Is Google Analytics GDPR compliant? It can be, but not out of the box and not by itself. The data-transfer problem that led European regulators to rule against Google Analytics in 2022 has largely been addressed by the EU-US Data Privacy Framework, which the EU General Court upheld in September 2025. What hasn't changed is that GA4 sets cookies, so in the EU you need opt-in consent before it runs. In the UK, a tightly restricted GA4 setup may arguably fit the new statistical-cookie exemption, but most configurations used by publishers still need consent.
So the honest answer is: GA4 is usable in Europe if you gate it behind proper consent, configure it carefully, sign Google's data processing terms and explain it in your privacy notice. This guide covers each step and the rulings behind it.
This is general information, not legal advice.
What European regulators ruled in 2022 and 2023
After the CJEU's Schrems II judgment in 2020 struck down the Privacy Shield, the campaign group noyb filed complaints against European websites using Google Analytics. Several authorities found that those sites' use of the then-current Universal Analytics transferred personal data to the US unlawfully:
- Austria: the data protection authority's decision, published in January 2022, was the first.
- France: the CNIL followed in February 2022 and issued formal notices to website operators.
- Italy: the Garante reached a similar conclusion in June 2022.
- Sweden: in July 2023 the IMY ordered companies to stop using the tool and fined two of them, including telecoms company Tele2.
These decisions turned on transfers and US surveillance law, not on whether analytics is allowed in principle. They also targeted the website operators, not Google, which is a reminder that you, as the controller, carry the responsibility.
GA4 data transfers and the Data Privacy Framework
On 10 July 2023 the European Commission adopted an adequacy decision for the EU-US Data Privacy Framework (DPF). US companies that self-certify under the DPF can receive EU personal data without extra transfer tools, and Google LLC participates. In September 2025 the General Court dismissed the Latombe challenge to the framework; an appeal has been lodged with the Court of Justice, so the position could still change.
The UK has its own "data bridge" extension to the DPF, in place since October 2023, which covers transfers from the UK to certified US companies.
What this means for you:
- Transfers to Google under GA4 now have a legal basis, provided Google remains certified.
- Keep an eye on the CJEU appeal. If the DPF falls, you'd need to rely on standard contractual clauses plus supplementary measures, or switch tools.
- Accept Google's data processing terms in your Analytics account settings, so the processor relationship is documented.
For the transfer mechanics in detail, read our guide to using US tools under the Data Privacy Framework.
Is consent required for Google Analytics?
Transfers are only half of it. GA4 stores identifiers in first-party cookies such as _ga, so the cookie rules apply regardless of where the data ends up.
| Market | Consent for GA4? | Why |
|---|---|---|
| EU / EEA | Yes, in practice | The ePrivacy Directive requires consent for non-essential cookies. National analytics exemptions (such as the CNIL's) have conditions that standard GA4 does not meet |
| UK | Usually yes; possibly not for a restricted setup | The statistical exemption from February 2026 requires a sole statistical purpose, sharing only to help improve your site, clear information and an opt-out |
| Switzerland | Check locally | Swiss law takes an information-and-opt-out approach to cookies, but many sites apply EU-style consent for consistency |
The UK statistical exemption and GA4
The ICO reads the statistical exemption as permitting a third-party analytics provider only where it acts as your processor and uses data only to help you improve your service. GA4 features such as Google signals, Google Ads linking, remarketing audiences, demographics and interests reporting and optional data-sharing settings take data beyond that purpose. A configuration with all of those turned off is arguably within the exemption, but this is contested, and you would need to document it, give clear information and provide a working opt-out. Many UK publishers are keeping GA4 consent-gated and using a self-hosted tool for consent-free statistics instead. See analytics without cookie consent for the alternatives.
GA4 IP anonymisation and other privacy settings
Universal Analytics needed an "anonymise IP" setting. GA4 doesn't, because, as Google's documentation states, "IP addresses are not logged or stored". That helps, but IP truncation alone doesn't make GA4 anonymous: the client ID in the cookie is still a unique identifier, so the GDPR still applies.
Settings worth reviewing in a GA4 property:
- Data retention: set event data retention to the shortest period that meets your needs.
- Google signals: leave off unless you have consent for advertising purposes.
- Granular location and device data: disable collection for regions where you don't need it.
- Data sharing settings: switch off sharing you don't need.
- Ads links: only link Google Ads where you have consent for advertising measurement.
- User-ID and enhanced measurement: never send emails, names or other direct identifiers in events or URLs.
- Consent Mode: implement it so that tags respect your banner choices. See Google Consent Mode v2 explained.
Watch your URLs. On adult and dating sites, page paths and search queries can reveal sensitive interests. Avoid passing detailed search terms or user-specific parameters into GA4, and consider grouping sensitive page paths into broad categories before they are sent.
Your responsibilities as the website operator
Google provides the tool, but under the GDPR you decide why and how analytics data is collected, which makes you the controller. In practice that leaves several jobs with you, not Google:
- Lawful basis: consent for the cookies in the EU, and a GDPR lawful basis for the processing itself (usually consent too, when it was collected through the banner).
- Transparency: your privacy notice must explain that you use Google Analytics, what it collects, why, how long data is kept and that data may go to the US under the DPF.
- Data minimisation: collect only what you need. An affiliate site rarely needs user-level analytics; aggregate traffic and conversion trends are usually enough.
- Rights requests: be ready to handle deletion requests. GA4 has a user deletion feature, but you'll need the visitor's client ID or user ID to use it.
- Risk assessment: on sites where browsing reveals sensitive interests, consider whether a data protection impact assessment is needed before deploying detailed tracking.
A hypothetical example: an adult review site runs GA4 with consent on EU traffic, keeps retention at two months, groups sensitive page paths into broad categories and never sends search queries. Its exposure is far lower than a site that loads GA4 on every visit with Google signals on and full URLs recorded, even though both "use Google Analytics".
Google Analytics 4 GDPR checklist
| Step | Done when |
|---|---|
| Consent before loading (EU) | No GA4 requests or cookies before the visitor accepts analytics |
| Consent Mode configured | analytics_storage and ad signals default to denied for EU visitors |
| UK approach decided | Either consent-gated, or documented exemption setup with an opt-out |
| Data processing terms accepted | Accepted in the Analytics admin settings |
| Privacy settings minimised | Retention, signals, sharing and location settings reviewed |
| No personal data in events | URLs, event parameters and User-ID checked |
| Privacy notice updated | Names Google as a recipient, explains purposes, US transfers and the DPF |
| Transfer status monitored | Someone owns checking the DPF appeal and Google's certification |
When an alternative makes more sense
GA4 is free and integrates with Google Ads, but for many affiliate publishers it is overkill. If you mainly need traffic, sources and top pages, and your revenue data lives in affiliate dashboards anyway, a privacy-focused or self-hosted tool can cover the basics with less legal exposure. On EU traffic you'll often see more of your visitors with an exempt-configured tool than with a consent-gated GA4, because rejection rates can be high.
Questions to ask any provider:
- Where is data stored and processed, and by whom?
- Does the provider use your data for its own purposes?
- Can it be configured to meet the CNIL's exemption or the UK statistical exemption?
- Does it offer a data processing agreement?
Compare options in our guide to Google Analytics alternatives for affiliate and adult sites and in our tracking platforms directory.
Frequently asked questions
Is Google Analytics illegal in the EU?
No. Earlier rulings found specific uses of Universal Analytics unlawful because of US transfers before the Data Privacy Framework existed. GA4 can be used lawfully today with consent, sensible configuration and a proper privacy notice, though the framework's appeal is still pending.
Does GA4 store IP addresses?
Google says GA4 does not log or store IP addresses. It does still use cookies and identifiers, so it processes personal data and needs consent for EU visitors.
Can I use GA4 without a cookie banner in the UK?
Only in a narrow case: if GA4 is configured purely for statistics about how your site is used, with advertising features and optional sharing turned off, and you give clear information and a simple opt-out. This is a contested reading, so take advice and document your decision.
Next steps
Check whether GA4 currently fires before consent on EU traffic, as that is the single biggest risk. Then work through the checklist. For more on consent, analytics and tracking, see our GDPR and cookies guides.