Privacy Policy for GA4 Support API

Privacy Policy for GA4 Support API

Effective Date: October 9, 2026

Welcome to GA4 Support API (“we”, “us”, “our”), operated by Attributions / GA4 Support, the Netherlands. We are committed to protecting your personal information and your right to privacy. If you have any questions about this privacy policy or our practices, please contact us at [email protected].

This privacy policy describes how we use, process and store your information when you connect your Google account to our application (“GA4 Support API”). It was previously published under the application’s former name, Attributions Support API.

1. Information We Collect

Personal information provided by you: your name, email address and contact preferences, which we need in order to run your account and to email you about your own setup.

Information collected automatically: standard technical information such as IP address, browser and device characteristics and operating system. This does not identify you by name.

Google user data that you choose to make available by granting the permissions listed in section 3.

2. How We Use Your Information

We use this information to deliver the service you asked for, and for nothing else. Specifically:

  • To configure and verify your Google Tag Manager and Google Analytics 4 setup.
  • To grant our service account the access it needs to keep recurring checks working, on the property or container you point us at.
  • To answer your questions about your own measurement, advertising and search data. If you use the AI chat, the data needed to answer your question is sent to our AI provider (see section 4).
  • To comply with our legal obligations.

We do not use your data for advertising, we do not sell it, and we do not combine it with data from other customers.

3. Google User Data: Scopes, Retention, and Deletion

This section covers our use of Google user data accessed through Google APIs. We request permissions in three steps, and each step asks only for what it needs: (1) signing in: identity only; (2) linking Google Tag Manager and Google Analytics when you start your setup; (3) connecting Google Ads, Search Console and BigQuery, which is optional and happens only when you connect them yourself in the dashboard. For the cookie banner on its own we request only sign-in and the two Tag Manager permissions, no Analytics. On Google’s consent screen you can untick individual permissions.

Requested scopes:

  • openid, .../auth/userinfo.email, .../auth/userinfo.profile — to identify the signed-in user.
  • .../auth/analytics.readonly — to see which GA4 property belongs to the measurement ID in your container. We read only the list of accounts, properties and data streams with this permission; event counts are read with our service account.
  • .../auth/analytics.manage.users — only when you activate the event breakdown: to add our service account as a Viewer on your GA4 property, so recurring checks do not depend on your personal sign-in. If you switch the event breakdown off in the dashboard, we remove the service account again.
  • .../auth/tagmanager.readonly — to find your Tag Manager account and containers and read which measurement IDs they contain. Changes to your container are made by our service account, not with your account.
  • .../auth/tagmanager.manage.users — to add our service account and our support address as administrators to the Tag Manager account you choose, so we can carry out and maintain your setup without your personal login. You can remove them at any time in Tag Manager.
  • .../auth/adwords — to read campaign cost and conversion figures from Google Ads (cost, clicks, impressions and conversions per campaign or per day, for a period you choose of up to 90 days back, at the moment you ask in the dashboard or the AI chat). Google offers only one permission for Google Ads and labels it “view and manage”; we use it for read queries only and change nothing in your Ads account.
  • .../auth/webmasters.readonly — to read search queries and pages with clicks and impressions, for a period you choose of up to 90 days back, from your own Search Console sites.
  • .../auth/bigquery.readonly — to measure how much of your tracking arrives without consent, which only your GA4 export contains. We find your GA4 export dataset (analytics_…) and ask it one fixed question (number of events with and without consent, 7 days by default and 30 at most). No free-form queries, no other tables.

We deliberately do not request cloud-platform. Search Console and BigQuery are requested as read-only permissions. For Google Ads, Google offers only a combined permission that includes write access; we use it for read queries only.

Data retention (no storage of Google user data): we do not store your Google user data. The access token Google issues when you sign in is held in a secure session cookie in your own browser (not readable by scripts on the page) and is not stored in our database. A session lasts 24 hours at most; Google itself normally lets an access token expire after about an hour. We do not request or keep a refresh token, so we cannot reach your Google data with your account while you are not signed in yourself. Permissions you gave our service account (for example Viewer on a GA4 property) are separate and stay until you or we remove them. Campaign figures, search queries and BigQuery counts are fetched at the moment you ask and are not stored. We do not store your AI chat history; per month we keep only the number of questions and tokens used, for quota and billing.

What we do keep: your name and email address, for as long as you are a customer — and afterwards only in invoicing records, which Dutch tax law requires us to retain for seven years. We also keep aggregate counts about your own setup, such as the number of events measured, for as long as your subscription is active; you can ask us to delete these at any time.

Data deletion: because we do not store your Google user data, there is no archive of it to delete. You can see what you have granted in the dashboard (Settings, “What do we have access to?”) and revoke it at any time at https://myaccount.google.com/permissions; Google revokes per app, so everything at once, which takes effect immediately. You can separately remove our service account from your Analytics property or Tag Manager container; the checks that rely on it will then stop. If you ask us to delete your account, we remove your name, email address and aggregate counts, except where invoicing records must be retained by law.

Limited Use disclosure: our use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features described above. We do not sell it, we do not use it for advertising, and we do not use it to train AI models. People at our company do not read it, except with your consent for specific data, for security purposes such as investigating abuse, to comply with applicable law, or as aggregated and anonymised figures for internal operations. We transfer it to third parties only to provide the feature: our hosting provider and, if you use the AI chat, our AI provider (see section 4).

4. Will Your Information Be Shared With Anyone?

We do not share your personal information or Google user data with third parties, except in these limited situations:

  • Infrastructure and processors: our application runs on Google Cloud in the europe-west1 region (Belgium), and we send service email through our mail provider. If you use the AI chat, Anthropic (United States) receives your question and the data the chat fetches to answer it (for example campaign totals or BigQuery counts), and processes it only to answer you. These parties process data on our behalf and for no other purpose.
  • Legal obligations: we may disclose information where we are legally required to do so in order to comply with applicable law, a governmental request, a judicial proceeding, a court order or legal process.

5. How Do We Keep Your Information Safe?

We have implemented appropriate technical and organizational security measures designed to protect the information we process. Access to Google APIs runs over encrypted connections, and our credentials are held in a managed secret store rather than in code or configuration files. However, despite our safeguards, no electronic transmission over the Internet or information storage technology can be guaranteed to be 100% secure.

6. Changes to This Privacy Policy

We update this privacy policy whenever the permissions we request change, and the Effective Date above will tell you when that last happened. The updated version is effective as soon as it is accessible here.

7. Contact Us

If you have questions or comments about this policy, or if you want us to delete your data, you may contact us at [email protected].

Meer weten of hulp nodig?

We doen geen directe inschrijvingen of online-checkouts — alles gaat via een kort intake-gesprek. Stuur je vraag en we reageren binnen 1 werkdag.