PartnerAccess
Privacy policy
What this service does with your information, in plain terms. Last updated 17 November 2026.
What PartnerAccess is, and whom this page covers
PartnerAccess is a service used by marketing agencies. An agency uses it to ask its clients for access to their marketing platforms (Google Analytics, Search Console, Meta, Shopify and others) and to keep track of which access it holds. A client gets a private link from the agency, follows the steps for each platform, and adds the agency as a user or partner inside that platform. Nobody is asked for a password, and PartnerAccess never sees or stores one.
This page covers three groups of people: clients who open a request link an agency sent them; people at an agency who sign in to run its requests; and people who contact PartnerAccess directly.
Each agency decides what it asks its clients for and why, and enters its clients' details. The service holds those details for that agency and shows them only to that agency's own team.
[To be supplied: the legal roles of the agency and of the service's operator for clients' details (for example, who is the controller and who the processor), as the agreement with agencies will set them]
Who runs PartnerAccess
[To be supplied: the name of the business that runs this service, and how to reach it by post if the law requires an address]
What is stored about clients
The details the agency's team enters when it makes a request: the client's first name, business name, email address and website.
Progress through the request, the time the link was first opened, and anything typed into the page: a store address, an account ID, a collaborator request code, or a note asking for help.
A copy of each email sent about the request, and a log of what happened on it (for example "link opened" or "Google Analytics connected").
This is used only to get the access set up and to show the agency what has been done. It is not used for advertising and it is not sold.
Each agency's information is kept apart
Every record belongs to one agency. Besides the checks in the software, the database itself is set up so that work done for one agency cannot read or change another agency's records. One agency never sees another agency's clients, requests or team.
If you choose Continue with Google
Where an agency offers it, a client may sign in with Google instead of following the written steps for Google Analytics, Tag Manager, Merchant Center and Search Console. It is optional: every platform can also be completed by following the steps.
If you sign in, Google asks you to allow PartnerAccess to see the list of your Google Analytics, Tag Manager and Merchant Center accounts and to manage the users on them, and to see the list of your Search Console sites. Only the platforms on your request are asked for.
That permission is used for one purpose: to show you your accounts so you can choose which to share, and to add the agency's access email as a user on the accounts you tick, at the access level shown on the page.
Your analytics, product, tag or search data is not read, and nothing else in your accounts is changed.
Your Google sign-in is held only in an encrypted cookie in your own browser for up to 20 minutes. It is not saved in the database, and no ongoing (offline) access to your Google account is requested. As soon as access has been granted, or you cancel, the sign-in is revoked with Google and the cookie is deleted.
What is kept afterwards: a note in the request's log that you signed in with Google, which platforms were connected, and the ID numbers of the accounts you chose to share; and the addresses of up to 20 of your Search Console sites, so the page can link you to the right one.
An agency's own Google and Meta accounts
Separately from anything a client does, an agency's team can connect the agency's own shared Google accounts: the accounts its clients add as users. For these accounts only, the service keeps ongoing (offline) access so it can check, once a day and on request, which access the agency already holds. The sign-in is stored encrypted and can be disconnected at any time, which revokes it with Google and deletes it.
With it, the service reads only lists: the Search Console sites, Google Analytics properties, Tag Manager accounts and containers, and Merchant Center accounts that the agency's account can see, with their names, IDs, website addresses and, where Google reports it, the agency's permission level. It stores that list and matches each entry to a client by website address. It does not read analytics reports, search queries, product data or tag contents, and it does not change anything. Merchant Center offers only one permission, which also allows changes; the service uses it only to read the list of accounts and their website address.
Where an agency has connected its own Meta business portfolio, the service reads the list of ad accounts, Pages, Instagram accounts, datasets and catalogues that clients have shared with that portfolio, with their names and IDs. It only reads.
How information from Google is treated
PartnerAccess's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Information from Google is used only for the features described on this page: adding an agency as a user where its client asks for that, and showing the agency's team which access it holds. It is not sold, not used for advertising, not used to train AI or machine-learning models, and not shared with anyone but the agency's own team and the service providers listed below.
The agency's team sees the lists described above, because showing them is the purpose of the service. Nobody reads the contents of your Google accounts.
AI assistants used by an agency's team
A person at an agency can connect an AI assistant so they can ask it questions such as "which clients have we got Search Console access for". The assistant can look up the client records and access lists that person is allowed to see in their own agency, and what it looks up is sent to that assistant's provider in order to answer.
Nothing obtained from a client's own Google sign-in is made available to an assistant. An assistant cannot sign in to Google, and cannot delete anything.
What is stored about people at an agency
For each person: name, email address, the agency they belong to, their role, a one-way hash of their password, and when they last signed in. If they connect an AI assistant, a one-way hash of its access token. If they switch on two-step sign-in, the secret their authenticator app uses (encrypted) and one-way hashes of their backup codes.
To slow down password guessing, a short-lived record of sign-in attempts is kept, which includes the network address they came from. These records are cleared within a day.
An agency's name, its accent colour and its logo (a PNG, JPEG or WebP image of at most 512 KB) are shown on its client pages and in its emails to clients. The logo is served at a public address so that those pages can show it.
Cookies
The service uses only cookies it needs to work: one that keeps a person at an agency signed in, one that remembers a browser they have signed in from, and short-lived cookies used while signing in with Google, described above. There are no advertising or analytics cookies.
Where it is kept, and who helps run it
Connections are encrypted in transit, and Google sign-ins and two-step secrets are encrypted before they are stored.
These providers are used to run the service, and process information only to run it: Vercel (hosting, and the store that keeps backups), Neon (the database), Resend (sending email), and Sentry (reports of software errors, so they can be fixed). When a client signs in with Google, or an agency checks its own access, the service talks to Google or Meta directly. If an agency connects its own Slack, a short notice of what its client did (for example "Sam at Harbour & Pine connected Google Analytics") is posted to that agency's channel.
Error reports describe what went wrong in the software. Before one is sent, private links, email addresses, sign-in details, cookies and anything typed into a form are removed from it.
[To be supplied: the country or region where the database, the backups and the error reports are kept, and whether any of it is held or reached from outside that place]
How long it is kept
A client's request and its history are kept until the agency deletes them, so the agency has a record of what access was set up and when. When the agency deletes a client, everything held about that client is deleted in one step: every request, what was typed, the activity log and the copies of emails.
The lists read from an agency's own Google and Meta accounts are refreshed at every check: anything the agency can no longer see is removed.
The whole database is backed up every day. Backups are kept for 30 days, and the first backup of each month for a year, so something deleted can remain in a backup for up to a year before that backup is removed.
[To be supplied: what happens to an agency's information, and its clients', when the agency stops using the service, and how soon it is deleted]
Removing access, and your choices
Access you grant lives inside each platform, not in this service. You can remove the agency at any time in that platform's user or partner settings.
You can remove this service's connection to your Google account at any time at myaccount.google.com/permissions.
To see, correct or delete what is held about you, ask the agency that sent you the request: reply to its email. You can also contact us, below.
[To be supplied: your rights under the privacy law that applies, and where you can complain if you are not satisfied with the answer]
Contact, and reporting a problem
If you received an access request you do not recognise, or think something here has been misused, tell us. Say which agency the request came from and, if you can, forward the email.
[To be supplied: the email address for privacy questions and problem reports (set PRODUCT_SUPPORT_EMAIL to show it here)]
Changes to this page
If the service starts handling information in a new way, this page is updated before that change is used, and the date at the top changes.