Privacy Policy

1. Who we are

The controller of your personal data is:

• Service: PartnerStandard MAP, a tool for creating and running Mutual Action Plans with partners
• Operator: Bernhard Friedrichs, sole proprietor (autónomo) registered in Spain, trading as PartnerStandard
• Address: Cowork Up! Puerta del Mar, C/ Cronista Carreres 10, Bajo, 46003 València, Spain
• VAT (NIF-IVA): ESX7526216H
• Email: hello@partnerstandard.com

We have not appointed a Data Protection Officer. Please send any privacy question to the email address above.

2. What this policy covers

This policy covers personal data we process through:

• the MAP web app at map.partnerstandard.com, including the public sample plan;
• signing in with Google, Microsoft or Notion;
• creating, connecting, reading and editing plans in your Google Sheets or Excel Online files or your Notion pages;
• magic links that let invited people open a plan without an account;
• reminder, digest, alert and other emails sent by the Service;
• emails you send us for support.

This policy does not cover how Google, Microsoft or Notion process your data in their own products. Their own privacy policies apply to that.

3. How MAP works, in brief

There are three kinds of users:

• Owners sign in with a Google account, a Microsoft work or school account or a Notion account. Each plan is a spreadsheet in the owner’s own Google Drive or OneDrive, or a page in the owner’s Notion workspace.
• Partner collaborators are contacts at the partner company. An owner invites them by magic link. They don’t create an account and can edit only the partner side of the plan.
• Internal collaborators are the owner’s colleagues. They are invited the same way and can edit only the owner’s side.

When you view or change a plan, our servers read or write the spreadsheet or Notion page on your behalf. The plan content passes through our servers but is not saved in our database.

4. Personal data we process

4.1 Owner account data

When you sign in, we receive and store:

• your name and email address;
• your Google, Microsoft or Notion account ID;
• the URL of your Google profile picture, if Google provides one (we do not store Microsoft or Notion profile photos);
• whether the provider says your email is verified;
• the permissions you granted (see sections 6, 7 and 8);
• the dates your account was created and last updated.

For Microsoft work or school accounts without an email claim, we store your sign-in name instead. This is usually your work email.

4.2 Connection data

To work with your spreadsheets and Notion pages, we store the access token and refresh token that Google, Microsoft or Notion issues to the Service. These tokens are encrypted at rest. The encryption key is kept separately from the database. Tokens are never sent to your browser, with one exception: when a Google user picks an existing file, the browser receives a short-lived access token for the Google Picker (see section 6.4).

4.3 Sign-in sessions

For each sign-in session we store a session token, its expiry date, and the IP address and browser user agent from which you signed in. We use these to keep you signed in and to protect your account.

4.4 Plan records

For each plan we store a small record so your dashboard loads quickly and notifications work:

• the plan ID, your user ID and the storage provider (Google, Microsoft or Notion);
• the file ID and file address of the spreadsheet or Notion page;
• the partner name (for example "Acme Ltd"), which is the only piece of plan content we store;
• creation, archive and pause dates, and the reason a plan is paused;
• your notification settings for the plan (reminder lead time, partner weekly copy on or off, partner alert frequency);
• the plan’s last notified health state and similar notification markers;
• the ID of your "PartnerStandard / MAPs" folder or, for Notion, the IDs of your PartnerStandard page and MAPs database and the ID and name of their workspace;
• for Notion plans, the IDs of the plan’s databases and of their columns, so that a column you rename keeps working.

4.5 Change records

When someone changes a plan through the Service, we record what kind of item changed (for example an activity), its ID, the type of change (created, updated, status changed or deleted), who made it (your user ID or a collaborator’s link ID) and when. We never record the values. We use these records for partner activity alerts and momentum warnings.

4.6 Profile settings

We store your timezone. Unless you choose one in Settings, it comes from your browser, which sends it when you open the dashboard or a plan. We use it to send emails at 08:00 your time. Where you provide them, we also store your company display name and a logo URL.

4.7 Collaborator data

When an owner shares a plan, we store for each magic link:

• the plan ID and the person’s row ID in the plan’s People tab;
• the email address the link was sent to;
• the side the person may edit (partner or owner side);
• a hash of the link token (never the token itself);
• when the link was created, last used and revoked.

When a collaborator opens a link, we create a session and store a hash of its token, the link it belongs to and its expiry date. Collaborator names are not stored in our database. They are in the plan spreadsheet, which the owner controls. When a collaborator edits a row, the Service writes their display name and the time into that row of the spreadsheet.

4.8 Email records

For each email we send, we keep a delivery record: the email type, the plan ID, the recipient’s email address, when it was prepared and sent, and the message ID from our email provider. This prevents duplicate emails.

When someone unsubscribes, we store only a one-way hash (SHA-256) of their email address, the email type and the date. We do not store the address itself for this purpose.

4.9 Security data

To limit abuse, we count requests to ask for a new magic link and to confirm actions from email buttons. The counters hold one-way hashes of the email address or IP address, never the raw values. Our hosting provider also keeps short-lived technical request logs (such as IP address, time and requested page) to run and secure the Service. We design our own server logs to hold only IDs and error codes, not plan content, names or email addresses.

We count page views with Vercel Web Analytics, to see how the Service is used and to improve it. It sets no cookies and stores nothing in your browser. For each page view it receives the page address, the site you came from, any campaign tags in the link, and your browser, operating system, device type and country. It tells visitors apart with a hash made from the request that changes every day, so it does not follow you from day to day or across sites, and we never see your IP address in it. Only public pages are counted by their address. Every page behind sign-in or a private link is counted as “/app”, so no ID, link or content reaches the page count.

4.10 Data we do not collect

• We do not store your plan content (objectives, activities, people, milestones, exit triggers, notes) in our database, except the partner name described in 4.4, and we design our logs to leave it out.
• We do not use advertising or tracking tools. The only analytics is the cookie-free page count described above.
• We do not use AI or machine-learning services to process your data.
• We do not process payment data. The Service is free.

5. Plan content

Your plan content lives in your spreadsheet or Notion page. When you or a collaborator use a plan, our servers read it, show it in the app and write changes back. While this happens, the content is held in server memory. To keep the app fast, a copy can stay in memory for up to about one minute. It is never written to our database, and we design our logs to leave it out.

Some emails contain plan content. For example, a reminder names the activity and its due date, and a digest lists what changed. These emails pass through our email provider (see section 13). They are sent only to the people described in section 10.

If you are an owner, you decide what goes into your plans, including the names, job titles and email addresses of people at your company and your partner’s. Please only add people’s details when you have a lawful reason to do so, and let them know you use MAP.

6. Google user data

This section applies if you sign in with Google.

6.1 What we access

When you sign in, Google asks you to grant these permissions:

• openid, email, profile: your name, email address, profile picture URL and Google account ID. We use these to create your account and sign you in.
• Google Drive, files used with this app (https://www.googleapis.com/auth/drive.file): access only to files that MAP created or that you chose to open with MAP through the Google Picker. MAP cannot see, list, open or change any other file in your Drive.

With that access, MAP uses the Google Sheets API and Google Drive API to:

• create a "PartnerStandard / MAPs" folder and a spreadsheet for each new plan;
• read and update the plans you open in the app, and the plans your collaborators and notifications need;
• check that a plan’s file still exists;
• move a half-created spreadsheet that MAP itself just made to your Drive trash, if creating it failed part-way.

6.2 How we use it

We use Google user data only to provide and improve the features you see in MAP: your dashboard, your plans, sharing with collaborators you invite, and the emails you set up. Our servers also read your plans on a schedule, using your access, to work out which reminders, digests, alerts and warnings are due.

6.3 How we store it

We store your name, email address, profile picture URL, Google account ID, the granted permissions and your encrypted access and refresh tokens (see sections 4.1 and 4.2). We store each plan’s file ID, file address and partner name (section 4.4). We do not store the content of your spreadsheets (section 5).

6.4 The Google Picker

When you choose "Connect existing file", your browser loads Google’s Picker from Google’s servers. Our server gives your browser a short-lived access token for this. The file you pick becomes available to MAP under the Drive permission above. Google processes this under its own privacy policy.

6.5 How we share it

We do not sell Google user data. We share it only:

• with the service providers in section 13, so they can host the Service, store our records and deliver emails;
• with the collaborators you invite, who see the plan you shared with them;
• with the recipients of emails you set up, which may contain plan content (section 10);
• when the law requires it (section 17).

6.6 Limited Use

PartnerStandard MAP’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In particular:

• We do not use Google user data for advertising, including retargeting or personalised ads.
• We do not use Google user data to train or improve artificial intelligence or machine-learning models, ours or anyone else’s.
• We do not sell Google user data or pass it to data brokers.
• No person at MAP reads your Google user data, unless you give us explicit consent for specific data (for example, when you ask for help with a plan), it is needed for security reasons (for example, to investigate abuse), it is needed to comply with the law, or the data has been aggregated and anonymised for internal operations.

6.7 How to revoke access

You can remove MAP’s access at any time at myaccount.google.com/connections. This also removes access for the other PartnerStandard tools, because they share one Google sign-in. After that, MAP cannot read or write your plans, and the plans are paused until you sign in again. Disconnecting your storage or deleting your account in MAP does not remove this access. To delete the data we store, see section 16.

7. Microsoft user data

This section applies if you sign in with a Microsoft work or school account. Personal Microsoft accounts are not supported.

7.1 What we access

When you sign in, Microsoft asks you, or your IT administrator, to grant these permissions:

• openid, email, profile, User.Read: your name, email address or sign-in name, and Microsoft account ID, to create your account and sign you in.
• offline_access: lets MAP keep working with your plans when you are not signed in, for example to send reminders.
• Files.ReadWrite: read and write access to the files in your own OneDrive.

7.2 Why MAP asks for Files.ReadWrite

Files.ReadWrite is broader than MAP needs. Technically, it would allow access to all files in your own OneDrive, not just MAP’s files. We ask for it because:

• Microsoft’s narrower "app folder" permission does not work reliably with Excel workbooks on OneDrive for work and school accounts;
• Files.ReadWrite is the narrowest permission that does work, and most organisations let users grant it without an administrator.

We do not ask for Files.ReadWrite.All or any SharePoint permission, so MAP has no access to files other people share with you or to your organisation’s sites.

7.3 What MAP actually does with it

MAP keeps its own files in the folder PartnerStandard / MAPs in your OneDrive. MAP only:

• creates that folder and an Excel workbook in it for each new plan;
• reads and updates the workbooks of plans you created or connected in MAP;
• looks up a workbook’s current web address when you click "Open in Excel";
• when you open "Connect existing file", searches your OneDrive for "PartnerStandard MAP" and lists the files in your MAPs folder, and shows you the names of the matching Excel files.

MAP does not open, read, copy or change any other file in your OneDrive. If you move a MAP workbook out of the folder, MAP keeps working with that file only.

7.4 Storage, sharing and revoking

We store and share Microsoft user data in the same way and under the same limits as Google user data (sections 6.3, 6.5 and 6.6). We do not use it for advertising or to train AI models, we do not sell it, and no person reads it except in the cases listed in section 6.6.

You can remove MAP’s access in your Microsoft account under myapps.microsoft.com, or ask your IT administrator to remove it for your organisation. After that, your plans are paused until you sign in again.

8. Notion user data

This section applies if you sign in with Notion.

8.1 What we access

When you sign in, Notion asks you to allow PartnerStandard Connector in one of your workspaces, with these capabilities:

• User information with email addresses: your name, email address and Notion user ID, to create your account and sign you in.
• Read, update and insert content: to create MAP’s own pages, and to read and update them.

Notion then offers a template provided by PartnerStandard, pre-selected, or lets you select pages. When you connect, Notion can copy a PartnerStandard page from our template into your workspace. MAP keeps its plans under a private PartnerStandard page (shared with other PartnerStandard tools) and only uses that. If a later sign-in makes a copy you never used, we move that copy to Notion’s trash.

8.2 What MAP actually does with it

MAP keeps its own pages under a private page PartnerStandard in your workspace, which it shares with other PartnerStandard tools. It holds a MAPs database with one row per plan, and each row’s page holds that plan’s five databases. MAP only:

• creates the PartnerStandard page and the MAPs database, and a row with its five databases for each new plan;
• when it has no PartnerStandard page on record for you, searches the pages the connection can reach for a PartnerStandard page the connection made (which another PartnerStandard tool may have made) or that Notion copied from our template and adds its MAPs database there;
• reads and updates the plans you created or connected in MAP;
• looks up a plan page’s current web address when you click "Open in Notion";
• when you open "Connect existing plan", lists the rows of your MAPs database.

Notion lets MAP reach the pages the PartnerStandard Connector created, the PartnerStandard page Notion copied from our template when you connected, and the pages you pick in Notion’s page picker. MAP reads and changes only its PartnerStandard page (the one the connection made, or the copy Notion made from the template) and the pages under it. After a sign-in it may move an unused extra copy of that template page to Notion’s trash. If you share a plan page with other people in Notion, that sharing is under your control.

8.3 What we store

We store your name, email address, Notion user ID and encrypted access and refresh tokens (sections 4.1 and 4.2). We also store the IDs of your PartnerStandard page and MAPs database, the ID and name of their workspace, and, for each plan, the IDs of its databases and their columns (section 4.4). We do not store the content of your pages (section 5).

8.4 Sharing and revoking

We share Notion user data in the same way and under the same limits as Google user data (sections 6.5 and 6.6). We do not use it for advertising or to train AI models, we do not sell it, and no person reads it except in the cases listed in section 6.6. Notion hosts your workspace under its own terms and privacy policy.

When you disconnect your storage or delete your account, MAP forgets its Notion tokens but does not revoke its access in Notion, because the same Notion connection is shared with other PartnerStandard tools. To remove PartnerStandard Connector’s access to Notion entirely, open Settings → Connections in Notion. This also removes access for the other PartnerStandard tools. After that, your plans are paused until you sign in again.

9. If you are a collaborator

If someone invited you to a plan, this section explains what we hold about you.

• Where your data comes from: the plan owner. They added your name, email address and, optionally, your job title and role to their plan, and chose to share it with you.
• What we store: your email address and the details of your magic link and session (section 4.7). Your name and other details stay in the owner’s spreadsheet. If an owner turns on emails for you, we keep delivery records (section 4.8).
• What you can do: use the link to view the plan and update your side. Ask the owner, who controls the spreadsheet, to correct or remove your details. Unsubscribe from any reminder or digest with one click. Contact us to exercise your rights (section 18).
• Link expiry: a link stops working after 90 days without use. You can then ask for a new one with the email address it was sent to. The owner can revoke your link at any time.

10. Emails we send

All emails come from notify@map.partnerstandard.com. Replies go to the plan owner.

Each person gets at most one reminder email a day, covering all their plans.

Every reminder, digest, alert and warning has a one-click unsubscribe link and the standard unsubscribe header, so your email app can show its own unsubscribe button. Magic links and Reconnect emails are needed to use the Service and have no unsubscribe link.

Buttons in reminder emails (such as "Mark done") open a confirmation page. Nothing changes until you press the button on that page. These buttons stop working after 14 days.

Our emails contain no tracking pixels. We do not send newsletters or marketing email from the Service.

11. Purposes and legal bases

Where we rely on legitimate interests, you can object at any time (section 18).

12. Cookies and browser storage

MAP uses only what is strictly necessary to run the Service. We do not use analytics, advertising or tracking cookies: our page count works without cookies and stores nothing on your device. So we do not show a cookie banner (Article 22.2 of Spanish Law 34/2002, LSSI-CE).

All cookies are HTTP-only, sent only over secure connections and limited to map.partnerstandard.com.

When you sign in, you are taken to Google’s, Microsoft’s or Notion’s sign-in page. When a Google user opens "Connect existing file", the browser loads the Google Picker from Google. Google, Microsoft and Notion may set their own cookies on those pages under their own policies.

If you set a company logo, the browsers of people who view your plans, including collaborators, load it from the web address you entered, so the host of that address receives their IP address. MAP sends no referrer with it.

13. Service providers

We use these providers to run the Service. They process personal data on our behalf, under data processing terms with appropriate safeguards.

Google, Microsoft and Notion are not our service providers. They are the sign-in and storage services you choose to connect, and they process your data under your own agreement with them.

14. International transfers

Our database and email sending are in the EU, and our server functions run in an EU region. Some providers are US companies and may access data from outside the European Economic Area, for example for support or security. Where this happens, we rely on the EU-U.S. Data Privacy Framework where the provider is certified, or on the European Commission’s Standard Contractual Clauses, together with additional safeguards where needed.

15. How long we keep data

Your spreadsheets and Notion pages are not ours to keep or delete. They stay in your Drive, OneDrive or Notion workspace until you delete them.

16. Deleting your account

You can delete your account in the app’s settings, or by emailing hello@partnerstandard.com. When you delete your account, we delete:

• your account, sign-in sessions and Google, Microsoft or Notion tokens;
• your profile settings and plan records, including partner names and the IDs of your Notion pages and databases;
• all magic links and collaborator sessions for your plans;
• the change records and email delivery records for your plans.

Your spreadsheets and Notion pages stay in your Google Drive, OneDrive or Notion workspace. They remain yours. Unsubscribe records stay, because they hold only a hash and protect people from unwanted email.

Deleting your account does not remove MAP’s access at Google, Microsoft or Notion. To remove it, see sections 6.7, 7.4 and 8.4.

17. Disclosure in response to legal process

We may disclose personal data if the law requires it or in response to valid legal process, including:

• court orders or judicial proceedings;
• subpoenas or regulatory investigations;
• requests from law-enforcement authorities;
• legal claims, where disclosure is needed to establish, exercise or defend legal rights.

We check each request for validity and scope. Where the law allows, we tell the affected users before we disclose their data. We disclose only the minimum needed. Because we do not store plan content, we usually cannot provide it.

18. Your rights

Under the GDPR you have the right to:

• Access: get a copy of your personal data.
• Rectification: correct inaccurate data.
• Erasure: ask us to delete your data.
• Restriction: limit how we use your data in certain cases.
• Portability: receive your data in a structured, machine-readable format. Your plans are already in your own spreadsheet.
• Object: object to processing based on legitimate interests, including the emails a collaborator receives.
• Withdraw consent: where we rely on consent, at any time.

Plan content is controlled by the plan owner. If you want details about you changed or removed from a plan, ask the owner. We can help you reach them.

19. How to exercise your rights

Email us at hello@partnerstandard.com. We may ask you to confirm your identity. We answer verified requests within 30 days.

You can also complain to the Spanish Data Protection Agency (Agencia Española de Protección de Datos, AEPD) at aepd.es, or to the data protection authority where you live or work.

20. Security

We protect your data with:

• encryption in transit (HTTPS) for all traffic;
• encryption at rest for Google, Microsoft and Notion tokens, with the key kept apart from the database;
• magic-link and session tokens stored only as one-way hashes;
• permission checks on our servers for every read and every change;
• rate limits on sensitive actions;
• logs designed to hold only IDs and error codes.

No system is perfectly secure. If a personal data breach affects you, we will tell you and the supervisory authority as the GDPR requires.

21. Children

The Service is a business tool. It is not meant for anyone under 18, and we do not knowingly collect children’s data.

22. Changes to this policy

We may update this policy. We will announce material changes in the Service and, where appropriate, by email to owners. The effective date at the top shows the latest version.

23. Contact

• Email: hello@partnerstandard.com
• Mail: Bernhard Friedrichs, Cowork Up! Puerta del Mar, C/ Cronista Carreres 10, Bajo, 46003 València, Spain