Privacy policies of the PartnerStandard tools

Each tool has its own Privacy Policy. All of them are on this page, in full and unchanged. Pick a tool to jump to its policy.

You sign in to these tools with Google through PartnerStandard Connector, the sign-in and storage connection they share. Google shows that name when it asks for your permission. What a tool does with your Google data is in that tool’s policy below, under “Google user data”. This website itself has its own Privacy Policy.

Mutual Action Plan

Privacy Policy

Effective date: 2026-11-12. The same text as on map.partnerstandard.com/privacy.

This Privacy Policy explains how PartnerStandard MAP ("MAP", "we", "us", "our") collects, uses, shares and protects personal data. It applies when you use the web app at map.partnerstandard.com (the "Service"), open a plan someone shared with you, or receive an email from the Service.

The short version: your plans live in your own Google Drive, OneDrive or Notion workspace. We do not store their content. We keep only what we need to sign you in, find your files, share plans with the people you invite and send the emails you set up.

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).

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.

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.

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).

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.

Email	Who receives it	When
Magic link	A collaborator	When the owner sends a link, or when you ask for a new one
Reminder	The person who owns an activity, on either side, if they have an email address	At 08:00 the plan owner’s time, 1, 3 or 7 days before a due date (the owner’s choice), then the day after it is overdue and weekly until done
Weekly digest	The plan owner, and partner contacts only if the owner turns on "Send partners a weekly copy"	Mondays at 08:00
Partner activity alert	The plan owner	Shortly after a collaborator makes changes, once a day, or never (the owner’s choice)
Momentum warning	The plan owner	When a plan has no progress for 14 days, and again at 30 days
Reconnect	The plan owner	When MAP loses access to the owner’s Google, Microsoft or Notion storage, at most once a day

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

Purpose	Legal basis (GDPR)
Create and run your owner account, sign you in, connect your storage, read and write your plans	Art. 6(1)(b), performance of a contract
Send owners the reminders, digests, alerts, warnings and Reconnect emails they set up	Art. 6(1)(b), performance of a contract
Store collaborators’ link and session data, and send them magic links, reminders and (if the owner turns it on) the weekly copy	Art. 6(1)(f), legitimate interests: the owner’s and our interest in running a shared plan the person was invited to
Keep sessions, IP addresses, user agents and hashed rate-limit counters to protect accounts and prevent abuse	Art. 6(1)(f), legitimate interests: security of the Service
Count page views without cookies, to see how the Service is used and improve it	Art. 6(1)(f), legitimate interests: understanding and improving the Service
Keep unsubscribe records after an account or plan is deleted, so we never email that address again for that type	Art. 6(1)(f), legitimate interests, and respecting your objection under Art. 21
Answer support requests	Art. 6(1)(b) for owners; Art. 6(1)(f) for others
Comply with legal obligations and valid legal requests	Art. 6(1)(c), legal obligation

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).

Name	Type	Purpose	Duration
`__Secure-better-auth.session_token`	Cookie	Keeps an owner signed in	30 days, extended when you use the app
`__Secure-better-auth.state`	Cookie	Protects the Google, Microsoft or Notion sign-in step against forgery	5 minutes
`map_c_` followed by a plan ID	Cookie	Keeps a collaborator signed in to one plan after opening a magic link	Up to 400 days in the browser; the session ends after 30 days without use
`map-theme`	Local storage	Remembers your light, dark or system theme choice. It never leaves your browser	Until you clear it
`map:timezone`	Session storage	Remembers that your timezone was already sent, so it is sent once per session	Until you close the tab
`map:guided-draft:v1:` followed by your user ID	Session storage	Keeps an unfinished new MAP if you reconnect part-way through. It never leaves your browser	Until you create the MAP or close the tab

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.

Provider	Purpose	Location of processing
Vercel Inc.	Hosting, server functions, scheduled jobs and the cookie-free page count (Vercel Web Analytics)	EU region for server functions; Vercel is a US company
Turso	Database for the records described in section 4	Ireland (EU)
Resend	Sending the Service’s emails	EU (Ireland) sending region; Resend is a US company

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

Data	How long
Owner account, connection data, profile settings and plan records	While your account exists. Deleted when you delete your account
Change records	While your account exists. Deleted when you delete your account
Owner sign-in sessions	30 days after your last use
Sign-in state	10 minutes
Magic links	Stop working after 90 days without use or when revoked. The records are deleted when the owner deletes their account
Collaborator sessions	Expire after 30 days without use and are then deleted
Email delivery records	90 days after sending
Email action buttons	Stop working after 14 days
Rate-limit counters	Reset every hour; old counters are deleted
Unsubscribe records (hash only)	Kept without a time limit, so your choice outlives a deleted account or plan
Hosting request logs	A short period set by our hosting provider
Page counts	Kept as totals with no names, email addresses or IP addresses, for as long as our hosting provider’s plan keeps them
Support emails	As long as needed to answer you, and no longer than 3 years

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

Partner Recruitment Tool

Privacy Policy

Effective date: 2026-11-12. The same text as on recruit.partnerstandard.com/privacy.

This Privacy Policy explains how PartnerStandard Recruitment ("we", "us", "our") collects, uses, shares and protects personal data. It applies when you use the web app at recruit.partnerstandard.com (the "Service").

The short version: your recruitment work lives in your own Google Sheets in your Google Drive, or in your own Notion workspace. We do not store its content. We keep only what we need to sign you in and find your files: your account, your company name, the names of your markets and a few technical records, in the EU.

1. Who we are

The controller of your personal data is:

Service: PartnerStandard Recruitment, a tool for finding, checking and signing partners, market by market
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 web app at recruit.partnerstandard.com, including the public sample market;
signing in with Google or Notion;
creating, reading and editing your markets in Google Sheets or in Notion;
emails you send us for support.

This policy does not cover how Google or Notion process your data in their own products, or how an AI assistant you choose processes what you give it. Their own privacy policies apply to that.

3. How the Service works, in brief

You sign in with a Google or a Notion account. Each market (one country or region and one partner type, for example "Austria · Reseller") is a spreadsheet, a "workbook", in your own Google Drive, in the folder PartnerStandard / Recruitment, or a page in your own Notion workspace, under a private page PartnerStandard with a Recruitment database. Only you work on your markets in the Service: it gives nobody else access to them.

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

4. Personal data in our database

Our database is hosted in the EU (section 13). It holds:

4.1 Account data

When you sign in, we receive and store:

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

4.2 Connection data

To work with your workbooks, we store the access token and refresh token that Google 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.

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 Your company name

If you enter it in Settings, we store your company name. The Service puts it into the search prompts it builds for you.

4.5 Market records

For each market we store a small record so your list of markets loads quickly:

the market ID, your user ID and the storage provider;
the file ID and file address of the workbook or Notion page;
the market’s display name (for example "Austria · Reseller"), which is the only piece of market content we store;
the dates the market was created and archived;
the ID of your "PartnerStandard / Recruitment" folder or, for Notion, the IDs of your PartnerStandard page and Recruitment database and the ID and name of their workspace;
for Notion markets, the IDs of the market’s databases and of their columns, so that a column you rename keeps working.

4.6 Technical records

To keep two changes to the same workbook or Notion page from clashing, we briefly store a lock with its file or page ID while a change is saved. To keep the app fast across our servers, we store the file or page ID and the time of the last change the Service made to each workbook or page. These records contain no content.

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 market content, names or email addresses.

4.7 Data we do not collect

We do not store your market content (hypotheses, candidate companies, people, calls, notes, scores, decisions) in our database, except the market display name described in 4.5, 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. Market content and people at potential partners

Your market content lives in your workbook or Notion page. When you use a market, 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.

5.1 Contact data of people at potential partners

You can record the names, job titles and email addresses of people at companies you consider as partners, and notes from your calls with them. This data is stored only in your own Google Sheet or Notion workspace. It is never stored in our database, and we design our logs to leave it out.

For this data, you are the controller: you decide whom you add, why and for how long, and you are responsible for having a lawful basis, for telling the people concerned where the law requires it, and for answering their requests. We process the data only to show and save your workbook for you.

If you are one of those people and want your details corrected or removed, please ask the user who added you. We cannot see or change their workbook outside their use of the Service, but we can help you reach them.

5.2 Text imported from AI assistants

The Service builds prompts you can copy into an AI assistant of your choice, for example to search for candidate companies. The Service itself sends nothing to any AI provider. What you paste into an AI assistant is processed by that provider under its own terms.

When you paste a result back, or paste notes from a call, the Service reads the text in your browser and shows you what it found. What you confirm is written to your workbook or Notion page as plain text, through our servers like any other change. We do not store the imported text in our database, and we design our logs to leave it out.

5.3 No emails

The Service sends no emails: not to you, and not to the people in your workbooks. Any contact with them happens outside the Service.

6. The sample market

The landing page shows a made-up sample market you can try without signing in. Your changes to it stay in your browser tab. Nothing is sent to our servers or stored.

7. Google user data

7.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 the Service created. The Service cannot see, list, open or change any other file in your Drive.

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

create a "PartnerStandard / Recruitment" folder and a workbook for each new market;
read and update the workbooks you open in the app;
check that a workbook still exists;
move a half-created workbook that the Service itself just made to your Drive trash, if creating it failed part-way.

7.2 How we use it

We use Google user data only to provide and improve the features you see in the Service: your list of markets and your workbooks.

7.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 (sections 4.1 and 4.2). We store each workbook’s file ID, file address and the market’s display name (section 4.5). We do not store the content of your workbooks (section 5).

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

with the service providers in section 12, so they can host the Service and store our records;
when the law requires it (section 16).

7.5 Limited Use

PartnerStandard Recruitment’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 PartnerStandard reads your Google user data, unless you give us explicit consent for specific data (for example, when you ask for help with a market), 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.

7.6 How to revoke access

You can remove PartnerStandard’s access at any time on Google’s Third-party connections page. After that, the Service cannot read or write your workbooks until you sign in again. Deleting your account in the Service does not remove this access, because the same Google sign-in is shared with other PartnerStandard tools. To delete the data we store, see section 15.

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 Recruitment’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. Recruitment keeps its markets 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 Recruitment actually does with it

Recruitment keeps its own pages under a private page PartnerStandard in your workspace, which it shares with other PartnerStandard tools. It holds a Recruitment database with one row per market, and each row’s page holds that market’s eight databases: value proposition, partner hypotheses, candidates, people, calls, qualification, exclusions and changes. Recruitment only:

creates the PartnerStandard page and the Recruitment database, and a row with its databases for each new market;
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 Recruitment database there. The search runs only when the connection’s Notion bot belongs to the person signed in;
reads and updates the markets you created in Recruitment;
looks up a market page’s current web address when you click "Open in Notion".

Notion lets Recruitment 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. Recruitment 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 market 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 Recruitment database, the ID and name of their workspace, and, for each market, the IDs of its databases and their columns (section 4.5). We do not store the content of your pages: your markets, candidate companies, the names, job titles and email addresses of people at them, and your calls and notes stay in your Notion workspace (section 5).

We share Notion user data in the same way and under the same limits as Google user data (sections 7.4 and 7.5). 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 7.5. Notion hosts your workspace under its own terms and privacy policy.

Recruitment never revokes its access in Notion, not when you sign out and not when you delete your account, because the same Notion connection is shared with other PartnerStandard tools. To remove PartnerStandard Connector’s access to Notion, open Settings → Connections in Notion. This also removes access for the other PartnerStandard tools. After that, your markets are paused until you sign in again.

9. Purposes and legal bases

Purpose	Legal basis (GDPR)
Create and run your account, sign you in, connect your Google Drive or Notion workspace, read and write your workbooks and Notion pages	Art. 6(1)(b), performance of a contract
Store your company name and put it into the prompts the Service builds for you	Art. 6(1)(b), performance of a contract
Process contact data of people at potential partners in your workbook, on your behalf	Your own legal basis as controller (section 5.1); for us, Art. 6(1)(b) towards you
Keep sessions, IP addresses and user agents to protect accounts and prevent abuse	Art. 6(1)(f), legitimate interests: security of the Service
Count page views without cookies, to see how the Service is used and improve it	Art. 6(1)(f), legitimate interests: understanding and improving the Service
Answer support requests	Art. 6(1)(b) for users; Art. 6(1)(f) for others
Comply with legal obligations and valid legal requests	Art. 6(1)(c), legal obligation

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

10. Cookies and browser storage

The Service uses only what is strictly necessary to run it. 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).

Name	Type	Purpose	Duration
`__Secure-better-auth.session_token`	Cookie	Keeps you signed in	30 days, extended when you use the app
`__Secure-better-auth.state`	Cookie	Protects the Google or Notion sign-in step against forgery	5 minutes
`map-theme`	Local storage	Remembers your light, dark or system theme choice. It never leaves your browser	Until you clear it
`recruit:new-market:` followed by your user ID	Session storage	Keeps an unfinished new market if you reconnect Google or Notion part-way through. It never leaves your browser	Until you create the market or close the tab

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

When you sign in, you are taken to Google’s or Notion’s sign-in page. Google and Notion may set their own cookies there under their own policies.

11. Links to AI assistants and other sites

If you open an AI assistant or another website from the Service, that site processes your data under its own terms and privacy policy. We send it nothing on your behalf.

12. Service providers

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

Provider	Purpose	Location of processing
Vercel Inc.	Hosting, server functions and the cookie-free page count (Vercel Web Analytics)	EU region for server functions; Vercel is a US company
Turso	Database for the records described in section 4	Ireland (EU)

Google 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.

13. International transfers

Our database is 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.

14. How long we keep data

Data	How long
Account, connection data, company name, market records and folder, page and database IDs	While your account exists. Deleted when you delete your account
Sign-in sessions	30 days after your last use
Sign-in state	10 minutes
Workbook and page locks	About 30 seconds while a change is saved
Last-change times of workbooks and pages	Deleted when you delete your account
Hosting request logs	A short period set by our hosting provider
Page counts	Kept as totals with no names, email addresses or IP addresses, for as long as our hosting provider’s plan keeps them
Support emails	As long as needed to answer you, and no longer than 3 years

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

15. 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 or Notion tokens;
your company name;
your market records, including their display names, and the IDs of your folder or of your Notion page and database and of the databases and columns of your Notion markets;
the locks and last-change times of your workbooks and pages.

Your workbooks and Notion pages stay in your Google Drive or Notion workspace. They remain yours, together with any contact data in them.

Deleting your account does not remove PartnerStandard’s access to your Google or Notion account. To remove it entirely, use Google’s Third-party connections page (section 7.6) or Notion’s Settings → Connections (section 8.4).

16. 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.

17. 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 markets are already in your own spreadsheets or Notion pages.
Object: object to processing based on legitimate interests.
Withdraw consent: where we rely on consent, at any time.

Workbook and page content, including contact data of people at potential partners, is controlled by the user who added it (section 5.1). If you want details about you changed or removed from a workbook or Notion page, ask that user. We can help you reach them.

18. 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.

19. Security

We protect your data with:

encryption in transit (HTTPS) for all traffic;
encryption at rest for Google and Notion tokens, with the key kept apart from the database;
permission checks on our servers for every read and every change;
imported and pasted text written to your workbook or Notion page as plain text, never as formulas;
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.

20. Children

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

21. Changes to this policy

We may update this policy. We will announce material changes in the Service. The effective date at the top shows the latest version.

22. Contact

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

Partner Business Case

Privacy Policy

Effective date: 2026-11-12. The same text as on pbs.partnerstandard.com/privacy.

This Privacy Policy explains how PartnerStandard Business Case ("we", "us", "our") collects, uses, shares and protects personal data. It applies when you use the web app at pbs.partnerstandard.com (the "Service").

The short version: your work lives in your own Google Drive or your own Notion workspace. We do not store its content. We keep only what we need to sign you in and find your files: your account, a few technical records and the records of your share links, in the EU.

1. Who we are

The controller of your personal data is:

Service: PartnerStandard Business Case
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 web app at pbs.partnerstandard.com;
signing in with Google or Notion;
opening a share link someone sent you;
creating, reading and editing your work in your Google Drive or in Notion;
emails you send us for support.

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

3. How the Service works, in brief

You sign in with a Google or a Notion account. Your work is kept in your own Google Drive, in the folder PartnerStandard / Business Cases, or in your own Notion workspace, under a private page PartnerStandard. Only you work on it in the Service. The only way anybody else sees a case is a share link that you create (section 5).

In Google Drive, the Service keeps one spreadsheet, Business Cases, with the tabs Offer, Products, Partner types, Cases, Costs, Our case and Strategic reasons. In Notion, it keeps a Business Cases database and a Business Case setup page. It holds a standard offer that new cases start from, and your cases. Each case holds its own offer (products, prices, partner types and their terms), its inputs, its cost lines and "our case": your own side of the case (figures such as your gross margin, your own cost lines, your reasons beyond revenue, your strategic reasons, the alternatives and a recommendation). A share link shows the case as it is now. Our case never reaches the person who opens a share link, neither on the page nor on the partner's PDF. It leaves the Service only as a PDF that you download.

When you view or change your work, our servers read or write your files or Notion pages on your behalf. The content passes through our servers but is not saved in our database.

4. Personal data in our database

Our database is hosted in the EU (section 11). It holds:

4.1 Account data

When you sign in, we receive and store:

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

4.2 Connection data

To work with your files, we store the access token and refresh token that Google 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.

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 Where your work is

We store the ID of your "PartnerStandard / Business Cases" folder and of its spreadsheet or, for Notion, the IDs of your PartnerStandard page, your Business Cases database and its data source, your setup page and its databases, and the ID and name of their workspace, so the Service finds them again without searching.

When you share a case, we store the ID of the case, a hash of the link, the date the link was created and, if you turn it off, the date it was turned off. In our database we never store the link itself, only a hash that cannot be turned back into it, so we cannot tell you your link again. Apart from our hosting provider’s short-lived request logs (section 4.6), which record each visit to a share link like any other page, we store nothing about the people who open it: no names, no email addresses and no record of who looked.

4.6 Technical records

Our hosting provider 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 your content, names or email addresses.

4.7 Data we do not collect

We do not store the content of your work in our database, 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. Your content

Your content lives in your Google Drive or Notion workspace. When you use the Service, our servers read it, show it in the app and write changes back. While this happens, the content is held in server memory. It is never written to our database, and we design our logs to leave it out.

You can share one case by link. Anyone who has the link can open that case’s one-page business case, without an account, until you turn the link off. They see the figures, the partner type, the costs and the offer of that case as it is now. They never see our case. They cannot change anything, and they see no other case and no other part of your files. When someone opens the link, our servers read the case from your Google Drive or Notion workspace with your connection and show it. Nothing is saved in our database.

Turning the link off ends it at once: the link no longer shows the case and says it does not work any more. Deleting your account ends all your links. If you share a link with someone, they can pass it on, so share it only with people you trust.

The Service sends no emails.

6. Google user data

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 the Service created. The Service cannot see, list, open or change any other file in your Drive.

With that access, the Service uses the Google Drive API to:

create a "PartnerStandard / Business Cases" folder and the spreadsheet for your work;
create, read and update the files the Service keeps there;
check that its folder and files still exist;
move a file that the Service itself made to your Drive trash, never deleting it for good.

6.2 How we use it

We use Google user data only to provide and improve the features you see in the Service.

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 (sections 4.1 and 4.2), the IDs of your folder and spreadsheet (section 4.4) and your share links (section 4.5). We do not store the content of your files (section 5).

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

with the service providers in section 10, so they can host the Service and store our records;
when the law requires it (section 14).

6.5 Limited Use

PartnerStandard Business Case’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 PartnerStandard reads your Google user data, unless you give us explicit consent for specific data (for example, when you ask for help), 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.6 How to revoke access

You can remove PartnerStandard’s access at any time on Google’s Third-party connections page. After that, the Service cannot read or write your files until you sign in again. Deleting your account in the Service does not remove this access, because the same Google sign-in is shared with other PartnerStandard tools. To delete the data we store, see section 13.

7. Notion user data

This section applies if you sign in with Notion.

7.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 PartnerStandard Business Case’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. The Service keeps your work under a private PartnerStandard page, which it shares 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.

7.2 What the Service does with it

The Service keeps its own pages under a private page PartnerStandard in your workspace: a Business Cases database with one row per case, and a Business Case setup page with the databases Offer settings, Products, Partner types, Costs, Our case and Strategic reasons. Each case's own offer, cost lines and our case are rows in those databases. The Service only:

creates the PartnerStandard page, the Business Cases database and the Business Case setup page, and the pages your work needs in them;
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 Business Cases database there. The search runs only when the connection’s Notion bot belongs to the person signed in;
reads and updates the pages it created, and moves rows it made to Notion’s trash when they are no longer needed (for example a row you removed).

Notion lets the Service 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. The Service 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 page with other people in Notion, that sharing is under your control.

7.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), and the IDs of your PartnerStandard page, Business Cases database and setup page with the ID and name of their workspace (section 4.4), and your share links (section 4.5). We do not store the content of your pages (section 5).

We share Notion user data in the same way and under the same limits as Google user data (sections 6.4 and 6.5). 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.5. Notion hosts your workspace under its own terms and privacy policy.

The Service never revokes its access in Notion, not when you sign out and not when you delete your account, because the same Notion connection is shared with other PartnerStandard tools. To remove PartnerStandard Connector’s access to Notion, open Settings → Connections in Notion. This also removes access for the other PartnerStandard tools. After that, the Service cannot reach your pages until you sign in again.

8. Purposes and legal bases

Purpose	Legal basis (GDPR)
Create and run your account, sign you in, connect your Google Drive or Notion workspace, read and write your files and Notion pages	Art. 6(1)(b), performance of a contract
Keep sessions, IP addresses and user agents to protect accounts and prevent abuse	Art. 6(1)(f), legitimate interests: security of the Service
Count page views without cookies, to see how the Service is used and improve it	Art. 6(1)(f), legitimate interests: understanding and improving the Service
Answer support requests	Art. 6(1)(b) for users; Art. 6(1)(f) for others
Comply with legal obligations and valid legal requests	Art. 6(1)(c), legal obligation

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

9. Cookies and browser storage

Name	Type	Purpose	Duration
`__Secure-better-auth.session_token`	Cookie	Keeps you signed in	30 days, extended when you use the app
`__Secure-better-auth.state`	Cookie	Protects the Google or Notion sign-in step against forgery	5 minutes
`ps-theme`	Local storage	Remembers your light, dark or system theme choice. It never leaves your browser	Until you clear it

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

When you sign in, you are taken to Google’s or Notion’s sign-in page. Google and Notion may set their own cookies there under their own policies.

10. Service providers

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

Provider	Purpose	Location of processing
Vercel Inc.	Hosting, server functions and the cookie-free page count (Vercel Web Analytics)	EU region for server functions; Vercel is a US company
Turso	Database for the records described in section 4	Ireland (EU)

Google 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.

11. International transfers

12. How long we keep data

Data	How long
Account, connection data and folder, spreadsheet, page and database IDs	While your account exists. Deleted when you delete your account
Share links (case ID, hash of the link, dates)	Until you delete your account. A link you turn off stops working at once, and its record stays until you delete your account
Sign-in sessions	30 days after your last use
Sign-in state	10 minutes
Hosting request logs	A short period set by our hosting provider
Page counts	Kept as totals with no names, email addresses or IP addresses, for as long as our hosting provider’s plan keeps them
Support emails	As long as needed to answer you, and no longer than 3 years

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

13. 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 or Notion tokens;
the IDs of your folder and spreadsheet, or of your Notion pages and database;
your share links, which ends them: nobody can open a case with them any more.

Your files and Notion pages stay in your Google Drive or Notion workspace. They remain yours, and we do not delete them. Delete them there if you want them gone. To end a single share link without deleting your account, turn it off in the app.

Deleting your account does not remove PartnerStandard’s access to your Google or Notion account. To remove it entirely, use Google’s Third-party connections page (section 6.6) or Notion’s Settings → Connections (section 7.4).

14. 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.

15. 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 work is already in your own files or Notion pages.
Object: object to processing based on legitimate interests.
Withdraw consent: where we rely on consent, at any time.

16. 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.

17. Security

We protect your data with:

encryption in transit (HTTPS) for all traffic;
encryption at rest for Google and Notion tokens, with the key kept apart from the database;
permission checks on our servers for every read and every change;
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.

18. Children

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

19. Changes to this policy

We may update this policy. We will announce material changes in the Service. The effective date at the top shows the latest version.

20. Contact

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

Partner Program Designer

Privacy Policy

Effective date: 2026-11-12. The same text as on program.partnerstandard.com/privacy.

This Privacy Policy explains how PartnerStandard Program Designer ("we", "us", "our") collects, uses, shares and protects personal data. It applies when you use the web app at program.partnerstandard.com (the "Service").

1. Who we are

The controller of your personal data is:

Service: PartnerStandard Program Designer
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 web app at program.partnerstandard.com;
signing in with Google or Notion;
creating, reading and editing your work in your Google Drive or in Notion;
emails you send us for support.

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

3. How the Service works, in brief

You sign in with a Google or a Notion account. Your work is kept in your own Google Drive, in the folder PartnerStandard / Programs, or in your own Notion workspace, under a private page PartnerStandard with a Programs database. Only you work on it in the Service. Nothing is shared with anyone. The Service has no share links.

In Google Drive, the Service keeps a folder for each company, with a spreadsheet Company facts and one spreadsheet for each programme. In Notion, it keeps a Programs database and a Program Designer setup page with the databases Companies, Reasons, Entry, Benefits, Requirements and Performance bar, and the Programs database has one row for each programme. They hold your companies (their facts, such as what a typical customer pays), your programmes (partner types, what each earns, reasons, benefits and requirements), the Program Sheet and the text of the public page. The Service does not publish the public page for you: you copy the text and use it where you choose.

When you view or change your work, our servers read or write your files or Notion pages on your behalf. The content passes through our servers but is not saved in our database.

4. Personal data in our database

Our database is hosted in the EU (section 11). It holds:

4.1 Account data

When you sign in, we receive and store:

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

4.2 Connection data

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 Where your work is

For Google Drive, we store the ID of your "PartnerStandard / Programs" folder and the ID of the folder of each company. For Notion, we store the IDs of your PartnerStandard page, your Programs database and its data source, your Program Designer setup page and its databases, and the ID and name of your workspace. The Service uses them to find your work again without searching. We store only these IDs, never the name or the content of a company or a programme.

4.5 Technical records

Our database also keeps short-lived locks (an ID and an expiry time, nothing else) so that renewing your Notion access runs once at a time, that your saves to Notion run one at a time, and that each Program Sheet rewrite in Notion runs once at a time (IDs only). A lock is removed when it expires.

4.6 Data we do not collect

We do not store the content of your work in our database, 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. Your content

When you delete a company or a programme in the Service, it moves to your Google Drive trash or to Notion’s trash. It is never deleted for good, and you can restore it there.

The Service sends no emails.

6. Google user data

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 the Service created. The Service cannot see, list, open or change any other file in your Drive.

With that access, the Service uses the Google Drive API to:

create a "PartnerStandard / Programs" folder for your work;
create, read and update the files the Service keeps there;
check that its folder and files still exist;
move a file or folder that the Service itself made to your Drive trash (when you delete a company or a programme), never deleting it for good.

6.2 How we use it

We use Google user data only to provide and improve the features you see in the Service.

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 (sections 4.1 and 4.2), and the IDs of your folders (section 4.4). We do not store the content of your files (section 5).

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

with the service providers in section 10, so they can host the Service and store our records;
when the law requires it (section 14).

6.5 Limited Use

PartnerStandard Program Designer’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 PartnerStandard reads your Google user data, unless you give us explicit consent for specific data (for example, when you ask for help), 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.6 How to revoke access

7. Notion user data

This section applies if you sign in with Notion.

7.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 PartnerStandard Program Designer’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. The Service keeps your work under a private PartnerStandard page, which it shares 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.

7.2 What the Service does with it

The Service keeps its own pages under a private page PartnerStandard in your workspace, in a Programs database. The Service only:

creates the PartnerStandard page, the Programs database and the Program Designer setup page, and the pages your work needs in them;
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 Programs database there. The search runs only when the connection’s Notion bot belongs to the person signed in;
reads and updates the pages it created, and moves rows it made to Notion’s trash when you delete a company or a programme.

7.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), and the IDs of your PartnerStandard page, Programs database and Program Designer setup page with the ID and name of your workspace (section 4.4). We do not store the content of your pages (section 5).

8. Purposes and legal bases

Purpose	Legal basis (GDPR)
Create and run your account, sign you in, connect your Google Drive or Notion workspace, read and write your files and Notion pages	Art. 6(1)(b), performance of a contract
Keep sessions, IP addresses and user agents to protect accounts and prevent abuse	Art. 6(1)(f), legitimate interests: security of the Service
Count page views without cookies, to see how the Service is used and improve it	Art. 6(1)(f), legitimate interests: understanding and improving the Service
Answer support requests	Art. 6(1)(b) for users; Art. 6(1)(f) for others
Comply with legal obligations and valid legal requests	Art. 6(1)(c), legal obligation

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

9. Cookies and browser storage

Name	Type	Purpose	Duration
`__Secure-better-auth.session_token`	Cookie	Keeps you signed in	30 days, extended when you use the app
`__Secure-better-auth.state`	Cookie	Protects the Google or Notion sign-in step against forgery	5 minutes
`pd_company`	Cookie	Remembers which company you opened last (an ID only)	1 year
`ps-theme`	Local storage	Remembers your light, dark or system theme choice. It never leaves your browser	Until you clear it

The sign-in cookies are HTTP-only, sent only over secure connections and limited to program.partnerstandard.com.

When you sign in, you are taken to Google’s or Notion’s sign-in page. Google and Notion may set their own cookies there under their own policies.

10. Service providers

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

Provider	Purpose	Location of processing
Vercel Inc.	Hosting, server functions and the cookie-free page count (Vercel Web Analytics)	EU region for server functions; Vercel is a US company
Turso	Database for the records described in section 4	Ireland (EU)

Google 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.

11. International transfers

12. How long we keep data

Data	How long
Account, connection data and folder, page and database IDs	While your account exists. Deleted when you delete your account
Sign-in sessions	30 days after your last use
Sign-in state	10 minutes
Hosting request logs	A short period set by our hosting provider
Page counts	Kept as totals with no names, email addresses or IP addresses, for as long as our hosting provider’s plan keeps them
Support emails	As long as needed to answer you, and no longer than 3 years

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

13. 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 or Notion tokens;
the IDs of your folders, or of your Notion pages and databases.

Your files and Notion pages stay in your Google Drive or Notion workspace. They remain yours, and we do not delete them. Delete them there if you want them gone.

14. 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.

15. 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 work is already in your own files or Notion pages.
Object: object to processing based on legitimate interests.
Withdraw consent: where we rely on consent, at any time.

16. 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.

17. Security

We protect your data with:

encryption in transit (HTTPS) for all traffic;
encryption at rest for Google and Notion tokens, with the key kept apart from the database;
permission checks on our servers for every read and every change;
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.

18. Children

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

19. Changes to this policy

We may update this policy. We will announce material changes in the Service. The effective date at the top shows the latest version.

20. Contact

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

PartnerStandard Desk

Privacy Policy

Effective date: 2026-11-04. The same text as on desk.partnerstandard.com/privacy.

This Privacy Policy explains how PartnerStandard Desk ("we", "us", "our") collects, uses, shares and protects personal data. It applies when you use the web app at desk.partnerstandard.com (the "Service").

The short version: your partner work lives in your own Google Sheets in your own Google Drive. We do not store its content. We keep only what we need to sign you in and find your files: your account, your company name, the names of your markets, cases and MAPs, the ids of your files, the hashes of your share links and a few technical records, in the EU. When you share a MAP or turn on reminders, the Service also sends emails for you, and keeps a short log of them. If you connect an AI assistant or another app, or make an API key or a webhook, we keep a small record of that too: names, levels, web addresses, dates, IDs and hashes, never your partner work. What an agent proposes to you is saved in your Partners spreadsheet; we keep only its IDs, codes and times, and the app’s name.

1. Who we are

The controller of your personal data is:

Service: PartnerStandard Desk, a workspace for running each partner from the first idea to exit
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 web app at desk.partnerstandard.com;
signing in with Google;
creating, reading and editing your partners, markets, business cases and Mutual Action Plans (MAPs) in Google Sheets;
the links by which people at your partners and your colleagues open a MAP, and the emails the Service sends for you;
AI assistants and other apps you connect to the Service, the API keys you make and the webhooks you add (section 4.11);
emails you send us for support.

This policy does not cover how Google processes your data in its own products, or how an AI assistant or another app you choose processes what you give it or what it reads through the Service. Their own privacy policies apply to that.

3. How the Service works, in brief

You sign in with a Google account. Your partners are one spreadsheet, and each market (one country or region and one partner type, for example "Austria · Reseller") is another. They sit in your own Google Drive, in the folder PartnerStandard / PartnerStandard Desk. Only you work on them in the Service: it gives nobody else access to them.

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

A MAP is the plan you and a partner agree on, with people, objectives, activities and milestones on both sides, and the reviews you hold with the partner (prep, scorecard, commitments, blockers, notes and the names of the people each summary went to). It is another spreadsheet in the same folder. You can give people on either side a link to it (section 4.8) and the Service can email them reminders and summaries for you (section 5.3).

4. Personal data in our database

Our database is hosted in the EU (section 10). It holds:

4.1 Account data

When you sign in, we receive and store:

your name and email address;
your Google account ID;
the URL of your Google profile picture, if Google provides one;
whether Google says your email is verified;
the permissions you granted (see section 6);
the dates your account was created and last updated.

4.2 Connection data

To work with your spreadsheets, we store the access token and refresh token that Google 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.

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 Your company name

If you enter it in Settings, we store your company name. The Service shows it in the menu and puts it into the search prompts it builds for you.

4.5 File records

So your lists load quickly, we store a small record for your Partners spreadsheet and one for each market:

the ids of the company, the market and you;
the file ID of the spreadsheet;
the market’s display name (for example "Austria · Reseller"), which is the only piece of market content we store;
the dates the market was created and archived;
the ID of your "PartnerStandard / PartnerStandard Desk" folder in Google Drive.

We store the same kind of small record for each MAP: the ids of the MAP, the company, the partner and you, the file ID of its spreadsheet, the partner type, the MAP’s display name (for example "Acme as reseller", which holds the partner’s name), the date it was created, your email settings for it and a few markers the scheduled job needs, such as the health it last reported, the last change time and whether it is paused. The MAP itself, with its people, objectives and activities, is a spreadsheet in your Google Drive. We also keep your timezone (section 4.10).

We store the same kind of small record for each business case: the ids of the case, the company, the partner and you, the file ID of its spreadsheet, the partner type (for example "Reseller"), the case’s title, which is its display name (for example "Case of 30 Oct 2026"), and the date it was created. The case itself, with its numbers and your own figures, is a spreadsheet in your Google Drive.

4.6 Events and technical records

When something changes in your work, we record an event: who made the change (your user ID, and whether you or an assistant acting for you made it), what kind of change it was, when it happened and the IDs of the file and the rows it touched. When the change comes from an agent’s proposal you accepted, the event also holds the proposal’s ID. An event holds IDs only. It holds no partner, market, call or person content and no names. When someone changes a MAP through a link, we also keep a short record of it for the alerts you can turn on: the ids of the MAP, the row and the link, a code for what happened (created, changed, status changed or deleted) and the time. It holds no content and is deleted after 30 days.

To keep two changes to the same spreadsheet from clashing, we briefly store a lock with its file ID while a change is saved. To keep the app fast across our servers, we store the file ID and the time of the last change the Service made to each spreadsheet. These records contain no content.

You can share a business case with a partner by a link. For each link we store the link’s ID, the ID of the case, your user ID, a hash of the link’s secret (the secret itself is never stored), and the dates the link was made and turned off. Nothing of the case is stored with it. When someone opens the link, our servers read your case from your spreadsheet, show the partner’s side of it and keep nothing. Your own side of the case (your costs and what you earn) is never on the link.

Anyone who has the link can see the partner’s side of the case, without signing in. Treat the link like the case itself. You can turn a link off, or make a new one, at any time. Deleting a case or your account turns its links off.

4.8 Links to MAPs and their sessions

You can give a person on either side of a MAP their own link, by email or by copying it. For each link we store the link’s ID, the ID of the MAP, your user ID, the ID of the person in the MAP, which side they are on, a hash of their email address, a hash of the link’s secret (the secret itself is never stored) and the dates the link was made, last used and turned off. When someone opens the link, we start a session for their browser: we store its ID, the link’s ID, a hash of the session token and its expiry date. We store no IP address or browser details for it. The session lasts 30 days and is extended when the person uses the MAP. A link stops working after 90 days without use, and its owner can ask for a new one by email.

Anyone who has a link can see the whole MAP, both sides, without signing in. They can change only their own side: the activities and objectives of their side, and the joint activities. A partner contact never sees your other MAPs, your partners, your business cases or your figures. Treat the link like the MAP. You can turn a link off at any time. Removing a person’s access, deleting the MAP or deleting your account turns the links off.

To limit abuse we keep short-lived counters. When someone asks for a new link, we count the requests for the email address they enter and for their IP address. When someone presses a button in one of our emails, we count the presses from their IP address and on that button. Each counter is stored under a hash of the email address, the IP address or the button’s link, never the address or link itself, with the start of its time window and a count. Counters are deleted after about a day.

You can also send the summary of a held review to the people on the partner’s side of a MAP. The summary has its own link for each review. For each one we store the link’s ID, the ID of the MAP, the ID of the review, your user ID, a hash of the link’s secret (the secret itself is never stored) and the dates the link was made and turned off. Sending a summary again turns the earlier link off, and if no email goes out, the new link is turned off at once. The review itself, with its prep, scorecard, commitments, blockers and notes, stays in the MAP’s spreadsheet in your Google Drive, and so do the names of the people the summary went to, on the review’s row. We do not store the summary, any of its content or whom it went to, and the events we keep about it hold only the ids of the MAP, the review and the link. Anyone who has the link can read the summary the review page shows for it, without signing in. They cannot change anything.

4.9 The email log and email preferences

When the Service sends an email for you (section 5.3), it first writes a row to an email log, so the same email is not sent twice. The row holds the type of email, the ID of the MAP, a key that says which email it was, the recipient’s email address, the times it was claimed and sent, and the ID Resend gives it. It holds no subject and no content. We keep a sent row for 90 days. A row that was claimed but not sent is deleted after a day.

When someone uses an unsubscribe link, we store a hash of their email address, the kind of email they turned off and the time. We keep this record after you delete your account, because it belongs to the address and not to you. It lets us honor the choice if the same person is added again.

4.10 Your timezone

If you choose a timezone in Settings, we store it. Until then the Service uses Europe/Berlin. Reminders and summaries go out at 8:00 in it.

4.11 Agents, API keys and webhooks

You can let an AI assistant or another app (an "agent") use the Service for you. You either connect it from the app and allow it on our allow page, or make an API key in Settings for a tool such as n8n, Zapier, Make or your own script. An agent acts in your name, with your access and nothing more: it reaches only your own work, through the same permission checks as the screens. With "Read only" it can only read. With "Read and change" it can also make small changes, such as logging a call, updating a MAP activity or filling in a review. With "Read, change and propose" it can also propose decisions to you: 4C scores, moving a stage, closing, signing, new partners and the status of a hypothesis or a market. It can never sign a partner, close one, move a stage or send anything to a partner: you decide those in the Service. A change an agent makes is labeled with its name and yours, for example "Claude for Bernhard", where the Service shows who made a change, such as the "Updated by" column of a MAP’s spreadsheet. What you accept from a proposal is labeled "Bernhard, proposed by Claude". We record an event for each change an agent makes (section 4.6), and none for what it reads.

For an app you connect, we store:

the app’s registration: its ID, the name it gives itself (for example "Claude"), the web addresses it uses to sign in and any other details it sends about itself, such as its website. An app registers itself before anyone signs in, so its registration is not tied to you and stays when you turn the app off. A registration made while you were signed in is deleted with your account;
what you allowed it: the app’s ID, your user ID, the level you chose and the dates you allowed it;
the refresh tokens that keep it connected, each stored only as a hash (the token itself is never stored), with your user ID, the ID of the sign-in session in which you allowed it, its level and its dates. A refresh token is replaced each time the app uses it and ends after 30 days without use. We show the newest one’s date as "last used". The access token the app sends with each request lasts one hour and is not stored;
the keys that sign those access tokens, with the private key encrypted.

For each API key, we store its ID, your user ID, the name you give it, its level, a hash of the key (the key itself is never stored and is shown to you only once), its first 8 characters so you can tell your keys apart, and the dates it was made, last used and turned off. A key you turn off stays stored, unused, until you delete your account.

Proposals an agent makes are saved in your Partners file; we keep only their ids, kind, status and dates, to count and expire them. Each proposal is a row in the Proposals tab of your Partners spreadsheet in your Google Drive, with what it proposes, the agent’s evidence and reason, and your answer. For each proposal we store its ID, your user ID, its kind (a code such as "fourC"), the IDs of what it is about (the company, the partner type, the market or the partner hypothesis), its status (such as "waiting" or "accepted"), the times it was made, answered and expires, which app or key made it (the app’s ID and the name it gives itself, or the key’s ID) and the file ID of your Partners spreadsheet. It holds no score, evidence, reason, company name or answer of yours.

A proposal you do not answer expires after 30 days. An agent never decides: a proposal changes nothing until you accept it. When you accept, the Service makes the change in your name, as if you made it on the screen. A webhook can tell another tool that a proposal was made or answered, with the proposal’s ID, its kind and the IDs it is about, like any other event.

To keep each app and each key to 60 requests a minute, we count its requests. The counter is stored under the key’s ID, or the app’s ID and your user ID, with the start of the minute and a count. Counters are deleted after about a day.

For each webhook, we store its ID, your user ID, the web address you gave, the events you picked, its signing secret (encrypted at rest, like the Google tokens), whether it is on, when it was last turned on, the date it was made and, while its deliveries fail, when they started failing. When an event happens, we queue a delivery for each of your webhooks that wants it: the event’s ID and type (for example "partner.signed"), the time it happened, the IDs it is about (such as the partner, the MAP or the review), the number of tries, the time of the next try and the last answer code from the address. A delivery holds IDs only, never names or other content. Deliveries that were sent or given up are deleted after 7 days. To send an event such as "a MAP activity is overdue" only once, we keep a mark with your user ID, a key made of IDs and a date, and the time, for 90 days. For each MAP, its record also holds the last health we told your webhooks about (a code such as "at_risk").

A webhook sends the event, as a signed request, to the web address you gave: its type, its ID, the time and the IDs above, and nothing else. To learn more, the receiver must read it through the API with a key or an app you allowed. You choose the address, so you decide who receives these requests. The Service stops sending when you turn the webhook off or delete it, and turns it off itself after 3 days of failed deliveries.

You can turn off an app or an API key at any time in Settings, under "Agents and API". It stops working at once: turning off an app deletes what you allowed it and its refresh tokens. Turning off never touches your Google sign-in. Turning off an app or a key keeps its proposals, and you can still answer them. Deleting your account deletes your API keys, what you allowed apps, your webhooks, their deliveries and marks, and your agents’ proposals in our database (section 13).

What an agent reads through the Service goes to the app you connected, and that app’s provider processes it under its own terms (section 9).

4.12 Data we do not collect

We do not store your partner, market, business case and MAP content (companies, people, calls, notes, hypotheses, scores, decisions, case numbers, objectives, activities, reviews, scorecards, commitments) in our database, except the market, case and MAP display names described in 4.5, the recipient addresses in the email log (4.9) and the hashes in 4.8, and we design our logs to leave it out. Webhook deliveries in our database hold IDs, codes and times only, and agent proposals hold IDs, codes and times and the app’s name (4.11).
We do not use analytics, advertising or tracking tools.
We do not use AI or machine-learning services to process your data. An AI assistant you connect yourself is your choice and works under its provider’s terms (section 9).
We do not process payment data. The Service is free.

5. Your content and people at potential partners

Your partner and market content lives in your spreadsheets. When you use the Service, 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.

5.1 Contact data of people at partners

You can record the names, job titles and email addresses of people at companies you consider as partners or work with, and notes from your calls with them. This data is stored in your own Google Sheets. The Service copies it into our database only as described in sections 4.8 and 4.9: a hash of an email address on a link, and the recipient’s address in the email log for 90 days. It is never otherwise stored in our database, and we design our logs to leave it out. People you add to a MAP get its emails and links only if you share the MAP or turn on reminders (section 5.3).

If you are one of those people and want your details corrected or removed, please ask the user who added you. We cannot see or change their spreadsheets outside their use of the Service, but we can help you reach them.

5.2 Text imported from AI assistants

The Service builds prompts you can copy into an AI assistant of your choice, for example to search for companies. The Service itself sends nothing to any AI provider. What you paste into an AI assistant is processed by that provider under its own terms.

When you paste a result back, or paste notes from a call, the Service reads the text in your browser and shows you what it found. What you confirm is written to your spreadsheet as plain text, through our servers like any other change. We do not store the imported text in our database, and we design our logs to leave it out.

5.3 Emails the Service sends for you

The Service sends emails only about a MAP. It sends them for you, to people on both sides of the MAP who have an email address in it, and to you:

a link to the MAP, when you choose Send link, and a new link when a person asks for one;
reminders to the owner of an activity before it is due and while it is overdue, with buttons to update it;
a weekly summary of the MAP to you and, if you turn it on, to the partner’s contacts;
the summary of a review, when you choose Send summary: a link to a one-page summary, to the people on the partner’s side that you pick;
a note when nothing has moved for a while, and alerts when someone changes the MAP through their link;
a note to you if the Service loses access to your Google Drive.

Every email has an unsubscribe link, except the note about your Google Drive, the link you asked for and the summary of a review. The buttons and unsubscribe links in an email open a page first and change something only when the person presses its button. The Service sends no emails about partners, markets or business cases, and sends nothing to people who are not in a MAP.

You decide whom you add to a MAP and whether to share it, so you are responsible for having a lawful basis to email them (section 5.1). We send the emails on your behalf and our email provider, Resend, delivers them (section 10). The recipient’s address and the content of the email pass through Resend. We keep only the log in section 4.9. The emails with the summary of a review are not written to that log; our server logs record only the ids of the MAP and the review if one fails.

6. Google user data

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 the Service created. The Service cannot see, list, open or change any other file in your Drive.

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

create a "PartnerStandard / PartnerStandard Desk" folder, a Partners spreadsheet and a spreadsheet for each new market, program, business case and MAP;
read and update the spreadsheets you open in the app;
check that a spreadsheet still exists;
move a business case or a MAP you delete to your Drive trash, and, when you choose it, the business cases and MAPs of a partner type you remove or of a Partners spreadsheet you start again;
move a half-created spreadsheet that the Service 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 the Service: your partners, your list of markets and your spreadsheets, also when an agent you connected reads or changes them in your name (section 4.11).

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 (sections 4.1 and 4.2). We store each spreadsheet’s file ID and the market’s display name (section 4.5). We do not store the content of your spreadsheets (section 5).

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

with the service providers in section 10, so they can host the Service and store our records;
with an AI assistant or another app you connect yourself, when it reads your work in your name, within the access you allowed it (section 4.11);
when the law requires it (section 14).

6.5 Limited Use

PartnerStandard Desk’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 personalized 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 PartnerStandard reads your Google user data, unless you give us explicit consent for specific data (for example, when you ask for help), 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 anonymized for internal operations.

6.6 How to revoke access

You can remove PartnerStandard’s access at any time on Google’s Third-party connections page. After that, the Service cannot read or write your spreadsheets until you sign in again. Deleting your account in the Service does not remove this access, because the same Google sign-in is shared with other PartnerStandard tools, and removing it signs you out of all of them. To delete the data we store, see section 13.

7. Purposes and legal bases

Purpose	Legal basis (GDPR)
Create and run your account, sign you in, connect your Google Drive, read and write your spreadsheets	Art. 6(1)(b), performance of a contract
Store your company name and use it in the menu and in the prompts the Service builds for you	Art. 6(1)(b), performance of a contract
Record events with IDs only, so a change can be traced to who made it	Art. 6(1)(b), performance of a contract; Art. 6(1)(f), legitimate interests: a reliable record of changes
Process contact data of people at partners in your spreadsheets, on your behalf	Your own legal basis as controller (section 5.1); for us, Art. 6(1)(b) towards you
Keep sessions, IP addresses and user agents to protect accounts and prevent abuse	Art. 6(1)(f), legitimate interests: security of the Service
Give people on a MAP their link and session, and keep a hash of their email address for it	Art. 6(1)(b) towards you; Art. 6(1)(f), legitimate interests: letting the people you chose use the MAP
Send the emails in section 5.3 for you and log them, so none goes out twice	Art. 6(1)(b) towards you; for the people who receive them, Art. 6(1)(f), legitimate interests: the plan they take part in
Let the agents and API keys you connect act for you, and send your webhooks’ events to the addresses you gave	Art. 6(1)(b), performance of a contract
Count the requests of each app and key, to keep each to 60 a minute	Art. 6(1)(f), legitimate interests: security of the Service and a fair share of your Google limits
Keep a hash of an email address that unsubscribed	Art. 6(1)(c), legal obligation, and Art. 6(1)(f), legitimate interests: honoring the choice
Answer support requests	Art. 6(1)(b) for users; Art. 6(1)(f) for others
Comply with legal obligations and valid legal requests	Art. 6(1)(c), legal obligation

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

8. Cookies and browser storage

The Service uses only what is strictly necessary to run it. We do not use analytics, advertising or tracking cookies, so we do not show a cookie banner (Article 22.2 of Spanish Law 34/2002, LSSI-CE).

Name	Type	Purpose	Duration
`__Secure-better-auth.session_token`	Cookie	Keeps you signed in	30 days, extended when you use the app
`__Secure-better-auth.state`	Cookie	Protects the Google sign-in step against forgery	10 minutes
`pd_m_` followed by the MAP’s ID	Cookie	Keeps a person with a link signed in to that MAP. It holds a random token; we store only its hash	30 days, extended when they use the MAP; the cookie itself can stay in the browser longer, but stops working
`map-theme`	Local storage	Remembers your light, dark or system theme choice. It never leaves your browser	Until you clear it
`partner-desk:new-market:` followed by your user ID	Session storage	Keeps an unfinished new market if you reconnect Google part-way through. It never leaves your browser	Until you create the market or close the tab

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

When you sign in, you are taken to Google’s sign-in page. Google may set its own cookies there under its own policies.

9. Links to AI assistants and other sites

If you open an AI assistant or another website from the Service, that site processes your data under its own terms and privacy policy. We send it nothing on your behalf.

If you connect an AI assistant or another app to the Service (section 4.11), the Service sends it what it asks for in your name, within the access you allowed it. That provider processes it under its own terms and privacy policy. You choose which apps you connect, and you can turn them off at any time.

10. Service providers

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

Provider	Purpose	Location of processing
Vercel Inc.	Hosting and server functions	Dublin, Ireland (EU) for server functions; Vercel is a US company
Turso	Database for the records described in section 4	Ireland (EU)
Resend, Inc.	Delivery of the emails in section 5.3 (the recipient’s address and the email’s content)	Resend is a US company; see section 11

Google is not our service provider. It is the sign-in and storage service you choose to connect, and it processes your data under your own agreement with it.

11. International transfers

Our database is in the EU, and our server functions run in the EU. 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.

12. How long we keep data

Data	How long
Account, connection data, company name, file records and folder IDs	While your account exists. Deleted when you delete your account
Events (IDs only)	While your account exists. Deleted when you delete your account
Sign-in sessions	30 days after your last use
MAP link sessions	30 days after the person’s last use
MAP links	Until you delete your account. A link stops working after 90 days without use, and at once when you turn it off or delete the MAP
Review summary links (IDs, hashes and dates)	Until you delete your account. A link stops working at once when you turn it off, send the summary again, or delete the MAP
Counters for new-link requests and email buttons (a hash of an email address, an IP address or a link)	About a day
Email log (including the recipient’s address)	90 days after sending, or one day if the email was never sent. Deleted with your account, except reminder rows that are still within the 90 days
Changes made through MAP links (IDs and codes only)	30 days
Email preferences (a hash of the address and the kind of email)	Kept after you delete your account, because they belong to the address
Your timezone	While your account exists
Agent apps you allowed: what you allowed them and their refresh tokens (hashes)	Until you turn the app off or delete your account. A refresh token ends after 30 days without use
Registrations of agent apps (ID, name, sign-in addresses)	Kept, as they are not tied to a person. One made while you were signed in is deleted with your account
API keys (name, level, hash, first characters, dates)	Until you delete your account. A key stops working at once when you turn it off
Request counters of apps and keys (IDs and a count)	About a day
Webhooks (address, events, encrypted signing secret, status, dates)	Until you delete the webhook or your account
Webhook deliveries (IDs, event type, times, tries, answer codes)	7 days after they were sent or given up, or 7 days after the event for a webhook that is turned off; deleted with the webhook or your account
Webhook marks (IDs and dates)	90 days; deleted with your account
Agent proposals (IDs, codes and times, and the app’s name)	While a proposal waits, at most 30 days, and then 90 days after it was answered or expired; deleted with your account
Sign-in state, and the one-time code that connects an app	10 minutes
File locks	About 30 seconds while a change is saved
Last-change times of spreadsheets	Deleted when you delete your account
Hosting request logs	A short period set by our hosting provider
Support emails	As long as needed to answer you, and no longer than 3 years

Share links: kept, with only the link’s ID, the case ID, your user ID, the hash and the dates, until you delete your account. A link stops working at once when you turn it off or delete the case.

Your spreadsheets are not ours to keep or delete. They stay in your Google Drive until you delete them.

13. 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 tokens;
your company name;
your file records, including the market display names, and the ID of your folder;
your share links, with the hashes and dates we keep for them;
your MAP records, your MAP links and their sessions, your review summary links, your timezone and your email settings;
the email log rows of your MAPs that we can match to your account, and the changes made through your MAP links;
your API keys, what you allowed agent apps, their refresh tokens and the app registrations made while you were signed in;
your webhooks, their signing secrets, their deliveries and marks;
your agents’ proposals in our database (their IDs, codes and times, and the app’s name);
the events, the locks and the last-change times of your spreadsheets.

Reminder rows in the email log may stay until their 90 days are over, and email preferences stay, as the table in section 12 says. Your spreadsheets stay in your Google Drive. They remain yours, together with any contact data in them. The proposals themselves stay in your Partners spreadsheet in your Google Drive.

Deleting your account does not remove PartnerStandard’s access to your Google account. To remove it entirely, use Google’s Third-party connections page (section 6.6).

14. 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.

15. 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 work is already in your own spreadsheets.
Object: object to processing based on legitimate interests.
Withdraw consent: where we rely on consent, at any time.

Spreadsheet content, including contact data of people at partners, is controlled by the user who added it (section 5.1). If you want details about you changed or removed from a spreadsheet, ask that user. We can help you reach them.

16. 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.

17. Security

We protect your data with:

encryption in transit (HTTPS) for all traffic;
encryption at rest for Google tokens, with the key kept apart from the database;
permission checks on our servers for every read and every change;
MAP links kept only as hashes, and email buttons and unsubscribe links signed, each tied to one person and one purpose, so none can be used for anything else;
API keys and the refresh tokens of connected apps kept only as hashes, webhook signing secrets encrypted at rest, and every agent request checked against what you allowed;
imported and pasted text written to your spreadsheet as plain text, never as formulas;
logs and events 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.

18. Children

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

19. Changes to this policy

We may update this policy. We will announce material changes in the Service. The effective date at the top shows the latest version.

20. Contact

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

Privacy Policy

1. Who we are

2. What this policy covers

3. How MAP works, in brief

4. Personal data we process

4.1 Owner account data

4.2 Connection data

4.3 Sign-in sessions

4.4 Plan records

4.5 Change records

4.6 Profile settings

4.7 Collaborator data

4.8 Email records

4.9 Security data

4.10 Data we do not collect

5. Plan content

6. Google user data

6.1 What we access

6.2 How we use it

6.3 How we store it

6.4 The Google Picker

6.5 How we share it

6.6 Limited Use

6.7 How to revoke access

7. Microsoft user data

7.1 What we access

7.2 Why MAP asks for Files.ReadWrite

7.3 What MAP actually does with it

7.4 Storage, sharing and revoking

8. Notion user data

8.1 What we access

8.2 What MAP actually does with it

8.3 What we store

8.4 Sharing and revoking

9. If you are a collaborator

10. Emails we send

11. Purposes and legal bases

12. Cookies and browser storage

13. Service providers

14. International transfers

15. How long we keep data

16. Deleting your account

17. Disclosure in response to legal process

18. Your rights

19. How to exercise your rights

20. Security

21. Children

22. Changes to this policy

23. Contact

Privacy Policy

1. Who we are

2. What this policy covers

3. How the Service works, in brief

4. Personal data in our database

4.1 Account data

4.2 Connection data

4.3 Sign-in sessions

4.4 Your company name

4.5 Market records

4.6 Technical records

4.7 Data we do not collect

5. Market content and people at potential partners

5.1 Contact data of people at potential partners

5.2 Text imported from AI assistants

5.3 No emails

6. The sample market

7. Google user data

7.1 What we access

7.2 How we use it

7.3 How we store it

7.4 How we share it

7.5 Limited Use

7.6 How to revoke access

8. Notion user data

8.1 What we access

8.2 What Recruitment actually does with it

8.3 What we store

8.4 Sharing and revoking

9. Purposes and legal bases

10. Cookies and browser storage