Blog

Is Google Analytics legal in the EU? Regulator decisions (2026)

Google Analytics is not subject to an unconditional EU-wide ban. European regulators found specific deployments unlawful because of transfers to the United States under the arrangements then in place. The 2023 EU–US Data Privacy Framework changed the available transfer mechanism; it did not approve every website's analytics configuration.

This article separates that history from the checks a website owner still needs to make. Sources and court status were checked on 16 November 2026. This is general information, not legal advice.

Why Schrems II led to analytics decisions

On 16 July 2020, the Court of Justice delivered Schrems II, case C-311/18. It invalidated the EU–US Privacy Shield adequacy decision. Concerns included US surveillance powers and insufficient judicial redress for people whose data was transferred.

The Court did not invalidate standard contractual clauses as a mechanism. It required protection that works in practice, with supplementary safeguards where necessary. A contract alone could not neutralize conflicting third-country law. Subsequent analytics investigations examined whether the actual transfers met that standard, including transfers of online identifiers and IP-related information.

What regulators decided in 2022 and 2023

The phrase “Google Analytics declared illegal in the EU” compresses several national actions into a misleading universal statement. Keep the regulator, deployment, date and legal issue attached to each finding.

Austria, DSB: The partial decision D155.027, 2021-0.586.257, dated 22 December 2021 and prominent in the 2022 debate, found an Article 44 infringement in the deployment examined. User identifiers, an IP address and browser parameters were personal data. The contractual clauses and supplementary measures did not provide adequate protection against US intelligence access. Calling this a January 2022 decision confuses the public discussion with its decision date.

France, CNIL: On 10 February 2022, CNIL informed noyb that it had ordered a website operator to bring its Google Analytics processing into compliance with Article 44 within one month, including stopping use if necessary. The original announcement is no longer available at its former URL; noyb's case record preserves that chronology. Its April 2022 update describes orders affecting three French websites.

Italy, Garante: In its 23 June 2022 announcement of a 9 June decision, the authority reprimanded Caffeina Media and allowed 90 days to bring processing into compliance. It found inadequate safeguards for US transfers. It also explained why truncating an IP address did not necessarily anonymize the data in Google's hands.

Denmark, Datatilsynet: Its 2022 annual report, page 35, records its review following the Austrian, French and Italian decisions. The conclusion was that lawful use required supplementary measures beyond Google's available settings. This was regulatory guidance; describing it as a judgment by an EU court would be inaccurate.

EU institutions, EDPS: In January 2022 the European Data Protection Supervisor reprimanded the European Parliament over its COVID-testing website, including inadequately safeguarded transfers involving Google Analytics. noyb's report and linked decision explain that this case applied Regulation (EU) 2018/1725, the separate data protection regime for EU institutions.

Sweden, IMY: On 3 July 2023, IMY announced findings involving Tele2, CDON, Coop and Dagens Industri. It imposed fines of SEK 12 million on Tele2 and SEK 300,000 on CDON. Tele2 had already stopped using the tool; IMY ordered the other three to stop. The audits concerned the version used on 14 August 2020, so these findings should not be presented as a test of every later GA4 configuration.

What changed on 10 July 2023

The Commission adopted Implementing Decision (EU) 2023/1795 on 10 July 2023. Its Article 1 recognizes adequate protection for transfers to US organizations included on the Data Privacy Framework list under the framework's conditions.

Google's transfer-framework page states that Google LLC and covered wholly owned US subsidiaries are certified. For a real deployment, check the receiving entity and certification coverage rather than assuming every Google service or processing purpose is covered.

This provided a new route for covered transfers. It did not retrospectively make every earlier transfer lawful or replace the separate duties governing collection and use.

Latombe v Commission: outcome and current status

Philippe Latombe challenged the adequacy decision in T-553/23. On 3 September 2025, the General Court dismissed the action. Its assessment concerned the protection ensured when the contested decision was adopted; the ruling was not a guarantee against all future legal or factual changes.

Latombe appealed on 31 October 2025. As checked on 16 November 2026, CURIA lists C-703/25 P as pending. The General Court's dismissal should therefore be reported alongside the continuing appeal. The challenge has not annulled the adequacy decision. Do not treat an appeal's existence as either automatic invalidation or a prediction of its outcome.

What any analytics deployment still needs

Review the actual data flow, not only the vendor's transfer statement. GDPR Articles 5, 6, 13 and 28 address minimization, lawful basis, transparency and processor arrangements. Document purposes and retention, identify who receives data, assess rights requests, and review the applicable DPA and subprocessors. Customer identifiers and purchase metadata deserve particular attention.

Cookie consent is separate from international transfers. ePrivacy Article 5(3) regulates storing or accessing information on a device, subject to limited exceptions and national implementation. First-party cookies are not automatically exempt. Cookieless techniques may also require assessment.

For example, a shop may configure GA4 to avoid analytics cookies after refusal while still sending cookieless pings in advanced consent mode. Google's basic/advanced distinction explains why “no cookies” does not mean “no requests.” Test what happens before acceptance, after rejection and after withdrawal. Review IP handling across the entire path: receiving, hashing or discarding an address is still processing it.

Datatilsynet made the broader point in its 31 July 2023 clarification: lawful transfers do not settle the remaining GDPR requirements.

Cookieless and privacy-first alternatives

Consider what measurement you need before choosing an alternative to Google Analytics. Fewer fields and shorter-lived identifiers can reduce exposure while limiting journey continuity. Cookieless tracking describes a technique, not a compliance guarantee.

AnalyticFast uses first-party cookies by default. Optional per-site cookieless mode, with the appropriate installed snippet, derives a daily salted pseudonymous identifier from the site, IP address and user agent. IP addresses are not stored with analytics; coordinates are rounded to two decimal places. Explicit identify calls and payment integrations can still introduce customer identity. Review the privacy configuration against your own purposes and obligations before deployment.

Questions, answered.

Was Google Analytics declared illegal throughout the EU?

Regulators found unlawful transfers in specific deployments under the arrangements they examined. Those decisions were not an unconditional EU-wide ban on every current use. The 2023 Data Privacy Framework introduced a transfer route for covered certified organizations, while consent and other GDPR duties remain.

Did Latombe v Commission invalidate the Data Privacy Framework?

No. The General Court dismissed the challenge in T-553/23 on 3 September 2025. As checked on 16 November 2026, CURIA lists the appeal, C-703/25 P, as pending. The challenge has not annulled the adequacy decision.

Keep exploring