Last updated: 4 November 2026
1. Who we are
Attributions is the data controller for personal data processed via this website and the SaaS service Server Side Support.
- Company name: Attributions
- Address: Tijmhof 36, 4907 BE Oosterhout, the Netherlands
- Chamber of Commerce (KvK): 73595039
- Email: support@ga4support.nl
2. What data we process
2.1 As a customer of the SaaS service
- Contact details: name, email address, phone number
- Company details: company name, address, Chamber of Commerce (KvK) number, VAT number (for Business and Agency plans)
- Payment details: handled directly by Mollie; we only see whether a payment succeeded
- Technical data: domain, linked Google account, GTM container IDs, the IP of your VPS
- Communication: messages you send via email, WhatsApp or chat
- GA4 data via the Google Analytics Data API: only aggregate event counts per event name, through our service account that is linked as a Viewer on your GA4 property (see 2.4 for the permissions this requires). We do not store any user IDs, transaction amounts or session details.
2.2 As a visitor to serverside-support.com
- IP address (temporarily, for security and logging)
- Data about your visit (pages, referrer, browser, language) — if you have given consent via the cookie banner
- See the cookie statement for the cookies we place
2.3 During migration to our infrastructure
During a migration we are temporarily granted user access to your Google Tag Manager containers (web and server) in order to host them on our infrastructure. We do not process event payloads persistently; see Security & Compliance for technical details.
2.4 Google permissions (OAuth): what we ask for and why
You sign in with your Google account and, at each step, grant only the permissions needed at that point. Google shows these permissions on its own consent screen, where you can untick individual permissions. What we ask for, per moment:
1. Signing in — identity only.
| Permission | Why | What we do with it — and what we don't |
|---|
openid
.../auth/userinfo.email
.../auth/userinfo.profile | To know who you are and recognise your account. | We read the name, email address and profile picture of your Google account. We ask for nothing more when you sign in. Signing up through the WordPress plugin asks for this only as well; customers without Google Tag Manager are not asked to link Tag Manager. |
2. Linking when you start your setup — Google Tag Manager and Google Analytics. We request these four together on the linking screen; what we do with each is listed below. For the cookie banner on its own we request only the two Tag Manager permissions (no Analytics).
| Permission | Why | What we do with it — and what we don't |
|---|
.../auth/tagmanager.readonly | To find your Tag Manager account and containers and read which measurement IDs they contain. | Read only. 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 the setup without your personal login. | We only add user permissions. You can always remove those permissions yourself in Tag Manager. |
.../auth/analytics.readonly | To see which GA4 property belongs to the measurement ID (G-…) in your container. | Only the list of accounts, properties and data streams. We do not read report data with this permission; we read event counts 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. | Only that one link. If you switch the event breakdown off in the dashboard, we remove the service account from your property. |
3. Connecting data sources — optional, only when you connect them yourself in the dashboard (for the AI add-ons for Google Ads, Search Console or BigQuery). Google then shows its own consent screen.
| Permission | Why | What we do with it — and what we don't |
|---|
.../auth/adwords | For the “what does a conversion cost?” insight. | Google offers only one permission for Google Ads and labels it “view and manage”. With your permission we run read queries only: cost, clicks, impressions and conversions per campaign or per day, for a period you choose (up to 90 days back), at the moment you ask in the dashboard or the AI chat. We change nothing in your Ads account. |
.../auth/bigquery.readonly | To measure how much of your tracking arrives without consent. | Read only. We search the names of your BigQuery projects and datasets for your GA4 export (analytics_…) and ask it one fixed question: the number of events with and without consent (7 days by default, 30 at most). No free-form queries and no other tables. |
.../auth/webmasters.readonly | For your top search queries on Google. | Read only: search queries and pages with clicks and impressions, for a period you choose (up to 90 days back), from your own Search Console sites. |
2.5 How long we keep your Google access and data
- No refresh token. We explicitly ask Google for short-lived access only (
access_type=online). 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 from that and stay in place until you or we remove them.
- The access token is held in your session cookie (sent over a secure connection only and not readable by scripts on the page), not in our database. A session lasts 24 hours at most; Google itself normally lets an access token expire after about an hour.
- Data from Google Ads, BigQuery and Search Console is fetched at the moment you ask and is not stored. If you use the AI chat, the results fetched (for example the counts from BigQuery) are sent to Anthropic to answer your question. We do not store your chat history; per month we keep only the number of questions and the number of tokens used, for the quota and billing.
2.6 Revoking permission
- In the dashboard (Settings → “What do we have access to?”) you can see what you have granted, including the data sources you connected for this session.
- You revoke at Google, via myaccount.google.com/permissions (the button in the dashboard takes you there). Google revokes per app, so everything at once: sign-in, Tag Manager, Analytics and data sources.
- On Google's consent screen itself you can untick individual permissions. Our data-source features then tell you which permission is missing.
- If you switch the event breakdown off in the dashboard, we remove our service account from your GA4 property. In Tag Manager you can remove our service account yourself.
2.7 Google API Services User Data Policy (Limited Use)
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In practice:
- We use that data only to provide the features described above, which you can see in the dashboard.
- We do not sell it and do not use it for advertising.
- We do not use it to train AI models.
- People at our company do not read that data, except with your consent for specific data, for security purposes (for example 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: Google Cloud (hosting) and, if you use the AI chat, Anthropic to answer your question (see section 4).
2.8 Advanced Data Keeper (add-on)
With the Advanced Data Keeper you store data yourself via your GTM server container, for example to match a purchase to a visitor after the fact.
- Where: on the server of your own setup (the VPS we manage for you, next to your server container). Not in our own database.
- How long: every collection has a mandatory retention period. 30 days by default, 400 days at most; “forever” does not exist. You adjust the period per collection in the dashboard.
- Deleting: you delete a collection, a document or a value (for example on a deletion request from your visitor) yourself in the dashboard; deleting by value works across all your websites at once.
- After cancelling: if you cancel the add-on, we delete the stored data on your server, the storage service itself and its access key after 30 days. If you turn the add-on back on within those 30 days, everything is still there. A deletion request (erasing the data of one person) remains possible during that period. We never delete your GTM container.
- What we see: for our overview we use only counts and storage size per collection. You view and manage the contents yourself in the dashboard.
- Our role: for what you store here you are the controller and we are the processor. We record this in the DPA (see section 4 and Security & Compliance).
2.9 Server Side Connect (add-on)
If you connect your CRM, your email tool or Google Ads with Server Side Connect, Privacy for Server Side Connect explains what we read and write per tool, what goes to Google Ads and how long we keep what.
2.10 AI assistants you connect to your account (Claude and others)
You can connect an AI assistant, such as Claude from Anthropic, to your Server Side Support account (see Claude connector). The assistant then reads data on your behalf, only after you have signed in with Google and chosen Allow. The connection is read only.
- What the assistant can receive: when you ask a question, the AI provider you use receives the answer from our service: your email address; the names, plans and roles of your accounts; domains and set-up status of your sites; event counts per day; consent percentages per Consent Mode signal; your plan, usage against your limit, add-ons and open notices; and your monthly amount. Never visitor IP addresses, visitor identifiers, payment details or invoices. The AI provider processes that data under its own terms and privacy policy, which you agreed with that provider; it is not our processor.
- What we store: we use Google sign-in only to confirm your email address (openid, email); we read or store no other Google data and no Google token. To keep you connected we store our own refresh token in our database, only as a SHA-256 hash, with a hash of the application's identifier, a keyed hash of your email address for lookup and an encrypted copy of your email address. Short-lived access tokens are not stored. Our logs contain per request only the tool name, an irreversible log identifier, the outcome and the duration; never your questions, the arguments or the answers.
- Disconnecting: at any time in the dashboard under Settings, “Connected AI assistants”. That revokes every connection for your email address. Afterwards the assistant can no longer renew its access; an access token that was already issued stays valid for at most 1 hour. Also remove the connector in your AI assistant’s settings.
- Legal basis: performance of the contract with you (Art. 6(1)(b) GDPR) and our legitimate interest in securing the connection (Art. 6(1)(f) GDPR).
3. Why we process this data
We process personal data solely on the basis of one of the following GDPR legal grounds:
- Performance of the contract (Art. 6(1)(b) GDPR): to provide the SaaS service, to invoice and to offer support.
- Legal obligation (Art. 6(1)(c) GDPR): statutory retention obligations, tax and financial administration.
- Legitimate interest (Art. 6(1)(f) GDPR): securing our systems, logging, fraud prevention, and the technical maintenance of the website.
- Consent (Art. 6(1)(a) GDPR): for non-essential cookies (analytics, marketing) on this website.
4. Who has access to your data
We only share personal data with subprocessors that are necessary for the provision of the service. The full list, including location and role, is available on the Security & Compliance page. In summary:
- UpCloud (Amsterdam, NL by default — or the data centre the customer selects: EU, UK, US, Singapore, Australia) — hosting of customer VPSes
- Google Cloud (europe-west1, BE) — dashboard infrastructure and database
- Mollie (Amsterdam, NL) — payment processing
- Rompslomp (NL) — invoicing and administration
- Anthropic (US) — AI chat support, active only per session, without persistent storage. If you use the AI chat, Anthropic receives your question and the data the chat fetches to answer it
- AI providers you connect yourself (for example Anthropic for Claude) — receive the data from the connector that you ask for, under your own agreement with that provider (see 2.10)
On request, we provide a DPA (Data Processing Agreement) that formalises the processing arrangements.
5. Retention periods
We do not retain personal data longer than necessary, and at most in accordance with statutory provisions:
| Data | Retention period |
|---|
| Invoices and administration | 7 years (statutory retention obligation, Art. 52 AWR) |
| Customer account after cancellation | As long as needed for remaining service delivery + 30 days |
| Technical logs (nginx, server) | 30 days |
| Support correspondence | 2 years after last contact |
| Google access token (session) | 24 hours at most, only in your session cookie; not in our database; no refresh token |
| Data from Google Ads, BigQuery and Search Console | Not stored; fetched at the moment you ask |
| AI chat | Conversation not stored by us; per month only the number of questions and tokens |
| Connected AI assistant (refresh token and identifiers, hashed) | 30 days after last use, at most 90 days per connection; removed when you disconnect. Authorization codes: valid 5 minutes, then deleted automatically |
| Request log of the AI assistant connection (tool, log id, outcome, duration) | 30 days |
| Advanced Data Keeper | Set by you per collection: 30 days by default, 400 days at most. After you cancel the add-on: 30 more days, after which we delete everything |
| Cookies on the website | See cookie statement |
6. Your rights
Under the GDPR you have the following rights regarding your personal data:
- Access (Art. 15) — request which data we process about you
- Rectification (Art. 16) — have inaccurate or incomplete data corrected
- Erasure (Art. 17) — have data deleted (subject to conditions)
- Restriction (Art. 18) — have processing restricted
- Portability (Art. 20) — receive your data in a machine-readable format
- Objection (Art. 21) — object to processing based on legitimate interest
- Withdraw consent — for processing based on consent
Send your request to support@ga4support.nl. We respond within 30 days.
7. Filing a complaint
If you believe that we do not handle your personal data carefully, you can file a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
8. Security
We take appropriate technical and organisational measures to protect personal data against loss or unlawful processing. Details are available on Security & Compliance.
9. Changes
We may amend this privacy statement when required by laws or regulations, or when our services change. The latest version can always be found on this page. In the event of significant changes, we inform existing customers by email.
10. Contact
For questions about privacy or this statement, please contact:
- Email: support@ga4support.nl
- Phone/WhatsApp: +31 6 25 11 82 13
- Post: Attributions, Tijmhof 36, 4907 BE Oosterhout, the Netherlands