Privacy Policy

1. Who we are

The controller of your personal data is:

• Service: PartnerStandard Partner 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 / Partner 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.

4.3 Sign-in sessions

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

4.4 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 / Partner 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. 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.

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

4.7 Share links of business cases

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

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, 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. Deleting your account deletes your API keys, what you allowed apps, your webhooks, their deliveries and marks (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 hold IDs only (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).

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 spreadsheet 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 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 / Partner 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).

6.4 How we share it

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 Partner 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

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

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.

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

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;
• 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.

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.

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 partner and market content, we usually cannot provide it.

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