Privacy statement

You can connect your workspace to Google Analytics 4 and Google Search Console. A workspace owner or admin does this themselves, by signing in with Google and granting permission. Below is what Branddock does with the data we receive from Google this way ("Google user data").

What we access

• Google Analytics 4 (read-only, analytics.readonly): the names and IDs of the GA4 properties your Google account can access, so you can choose one. We store only the ID of the chosen property. For that property we fetch, per page (host name and path), the number of active users, sessions and conversions over the last seven days. These are totals per page, not data about individual visitors.
• Google Search Console (read-only, webmasters.readonly): the sites your account can access and, for the chosen site, per page and per search query the number of clicks and impressions, the click-through rate and the average position. We also request your email address, only to show in a message which Google account you connected with. We do not store that address.
• Access tokens: the keys (OAuth tokens) Google gives us. We store them encrypted (AES-256), with a key kept separate from the database.

How we use it

Only to provide the features you ask for in Branddock:

• showing the fetched figures to the members of your workspace;
• measuring how content you published through Branddock performs (the learning loop);
• analyses and reports by agents: only an agent that an owner or admin gave read access to the connector, and only in a task or conversation started by a member of the workspace;
• SEO features based on Search Console, such as flagging pages that are losing visibility in Google.

While the connector is active, we fetch the data once a day, and when someone clicks "Sync now". We never write anything to your Google account.

Who we share it with

We do not sell Google user data. We only pass it on to these service providers, who process it on our behalf:

These service providers do not use the data for their own purposes, and the AI providers do not use it to train their models. Where they process the data is listed in our sub-processor list on the Security & GDPR page.

Beyond that, Google user data only goes to others when you choose to (your own AI assistant through the Branddock MCP server, a share link to a report, or content you publish in which an agent mentions figures) or when the law requires us to.

What we don't do

• We do not sell Google user data.
• We do not use it for advertising: not to serve ads, not for retargeting and not for personalised or interest-based ads.
• We do not use it to develop, improve or train generalised AI or machine-learning models.
• We do not use it to determine creditworthiness or for lending purposes.
• Branddock staff do not view your Google user data, except with your explicit consent (for example when you ask us for help), when it is necessary for security purposes (such as investigating abuse), or when the law requires it.
• We do not use it for product analytics. Technical error messages from the Google API, without report figures, may end up in our error monitoring so we can fix problems.

Revoking access and deleting data

• Disconnect: an owner or admin selects the Google connector under Connectors and clicks Disconnect. We then immediately delete the access tokens, the chosen property or site and the fetched reports and measurements from our active database, and stop fetching data. Analyses an agent already wrote for you remain until you delete them or the workspace.
• Revoking permission at Google: when you disconnect, you can also have access at Google revoked, or you can do it yourself at https://myaccount.google.com/permissions.
• Backups: the data is automatically removed from backups within 7 days.

Limited Use

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