Is Google Analytics GDPR compliant?

Published 12 min read

Regulators in Austria and Italy found sites in breach for sending Google Analytics data to the US; the 10 July 2023 adequacy decision gave that transfer a legal route, but asking before the cookie is still your job.

Photocopy-style paste-up of a printed browser window with a plain line chart and a blank banner strip
A printed browser page with its chart and an empty banner strip: the measuring and the asking are separate jobs.

Two questions hide inside the one you searched

“Is Google Analytics GDPR compliant?” has no yes or no, because a tool is not compliant on its own: the site that installs it is the controller and answers for how it runs. What regulators have actually ruled on splits into two questions. May the data travel to the US? And may the tag store its cookie on the visitor’s device before they agree? Follow one pageview and you can see where each question sits.

  1. Stop 01

    The visitor’s device

    The GA4 tag sets the _ga cookie to tell users apart. Its default expiration is 2 years.

    ePrivacy Art. 5(3): consent first, unless strictly necessary for a service the visitor asked for

    Untouched by the 2023 decision

  2. Stop 02

    Google’s collection servers in the EU, Switzerland or the UK

    For EU, Swiss and UK traffic, Google says it collects the data on servers there, uses the IP address only to derive a coarse location, and drops it without logging it.

    GDPR Art. 4(1): is what remains still personal data?

    Google’s own description, read today

  3. Stop 03

    Google Analytics servers, for processing

    The data is then forwarded to Analytics servers. Google says it relies on the EU-US Data Privacy Framework to transfer EEA personal information to the US.

    GDPR Arts. 44–46: a transfer needs a route under Chapter V

    The stop the 2023 decision covers

The 2021 and 2022 decisions below turned on stop 03, the transfer. The 10 July 2023 adequacy decision answered that stop for organisations on the US list. Stop 01 is a separate rule with its own answer, and it is where most of the day-to-day work still sits.

The decisions, in date order

The story did not stop in 2022. Here are 9 dated steps, from the court ruling that started it to the appeal lodged in 2025. Each row links to the deciding body’s own text, read 22 Oct 2026.

  1. Court of Justice of the EU

    Schrems II strikes down the Privacy Shield

    Case C-311/18 invalidates the earlier EU-US adequacy decision. From then on a US transfer needs another route under Chapter V of the GDPR.

    Commission, EU-US data transfers
  2. Austria (DSB)

    A website’s Google Analytics transfer breaks Art. 44

    On a visit of 14 August 2020 the site sent at least unique user ID numbers, the IP address and browser parameters to Google. The standard contractual clauses gave no adequate protection, because Google is subject to US surveillance under FISA 702; the extra measures did not remove that access; no other Chapter V tool applied. The complaint against Google itself was dismissed.

    BVwG W245 2252208-1, point I.17
  3. Austria (DSB)

    A second Google Analytics decision, now final

    The DSB later describes its decision D155.026 as final and cites it for the point that a visitor can enforce the transfer rules by complaint to a supervisory authority.

    DSB 2023-0.243.883 (2 Oct 2024)
  4. Italy (Garante)

    Reprimand and 90 days to fix the transfer

    The Garante reprimands a website operator, Caffeina Media S.r.l., and gives it ninety days to comply, or the Google Analytics data flows to the US will be suspended. An IP address stays personal data even when truncated, given what Google can add to it.

    Garante press release, 23 June 2022
  5. Austria (Federal Administrative Court)

    The DSB’s finding against the website stands

    The court rejects the appeal against the finding on the website operator and dismisses the appeal that tried to hold Google liable as the recipient. It allows a further appeal on points of law.

    BVwG W245 2252208-1, operative part
  6. European Commission

    Adequacy decision for the EU-US Data Privacy Framework

    Implementing Decision (EU) 2023/1795 finds that the US ensures an adequate level of protection for personal data sent to organisations on the Data Privacy Framework List kept by the US Department of Commerce.

    Commission press release IP/23/3721
  7. Google

    Google moves its ads and analytics transfers onto the framework

    Google says that from this date, when clients use its advertising and analytics products, it relies on the EU-US framework to transfer personal information from the EEA to the US.

    Google, international data transfers
  8. General Court of the EU

    Challenge to the framework dismissed

    In Latombe v Commission (T-553/23) the court dismisses an action to annul the 10 July 2023 decision.

    OJ C/2025/5446
  9. Court of Justice of the EU

    Appeal lodged

    The applicant appeals to the Court of Justice (C-703/25 P), asking it to set the judgment aside and annul the decision. The Court’s case list showed it pending when read on 22 Oct 2026.

    OJ C/2025/6610
Not in the file: France

The CNIL’s own page on its formal notice over Google Analytics and US transfers now reads that the article is no longer available. The CNIL explains that once the deadline in a published notice has passed, the organisations concerned are no longer named. Because we could not read the notice itself, we do not summarise it here. The CNIL’s current guidance on audience measurement is quoted further down.

What to do

In the Austrian and Italian decisions it was the website running the tag that was found in breach, not Google. If you run GA4, keep the paperwork that shows how your own set-up handles both questions: the DSB treats the transfer rules as something a single visitor can complain about.

What each finding means now

A decision is only as current as the facts it rested on. These are the findings the 2021 and 2022 decisions turned on, with what has moved since. 2 of the 5 still bind a GA4 site exactly as written.

Findings of the Austrian and Italian Google Analytics decisions and what has changed since
The findingWho, whenSince then
A unique ID in the cookie, with the IP address and browser data, is personal dataAustria (DSB), 22 Dec 2021; repeated in its 2025 decisionsUnchanged. GA4 still sets _ga to tell users apart, with a 2-year default expiration.
A truncated IP address is still not anonymousItaly (Garante), 9 Jun 2022Google now says GA4 does not log or store IP addresses from EU, Swiss or UK users and drops them after a coarse location lookup on servers there. No regulator page we read has ruled on that design.
Standard contractual clauses alone did not protect the data from US surveillanceAustria (DSB), 22 Dec 2021The Commission says the US safeguards adopted in 2022 apply to every GDPR transfer to US companies, whatever the tool, so they also support clauses. Google now names the framework first.
Google’s extra measures did not bring protection up to the EU levelItaly (Garante), 9 Jun 2022On the framework route the question changes: an adequacy decision covers the transfer to a listed organisation without a separate authorisation.
The site that runs the tag answers for the transfer; Google as recipient does notAustria (DSB), 22 Dec 2021; court, 12 May 2023Unchanged. The consent record, the privacy notice and the processing terms are yours to show.
Decisions read on the regulators’ and courts’ own pages, Google’s help pages read 22 Oct 2026. Open the Austrian ruling
Photocopy-style paste-up of a barred page sliding into an envelope on a paper outline of the EU
The transfer question is about the envelope: where the data goes once it leaves the EU.

What the Data Privacy Framework changed

“A transfer of personal data to a third country … may take place where the Commission has decided that the third country … ensures an adequate level of protection. Such a transfer shall not require any specific authorisation.”
GDPR Art. 45(1)

On 10 July 2023 the Commission took exactly that kind of decision for the United States, with one limit written into its first article: the adequate level of protection covers personal data sent to organisations that are on the “Data Privacy Framework List”, kept and published by the US Department of Commerce (Decision (EU) 2023/1795, Art. 1). A US company that is not on the list gets nothing from it. The decision answers where the data may go; it does not answer whether you may set the cookie.

Where Google stands on it

  • Google says Google LLC and its wholly-owned US subsidiaries, unless explicitly excluded, have certified that they adhere to the framework’s principles.
  • From 1 September 2023 it relies on the EU-US framework to transfer EEA personal information to the US when clients use its ads and analytics products. For UK and Swiss data it relies, in certain circumstances, on the UK Extension and the Swiss-US framework from 16 September 2024.
  • Its processing terms keep standard contractual clauses as the fallback where it has not adopted, or is no longer adopting, a framework like this one.

That fallback matters because the Commission says the US safeguards behind the decision apply to transfers made with clauses too. The comparison of PostHog and Google Analytics shows both vendors naming the same two routes.

What could still move it

The decision is reviewed: first after one year, then at intervals set with the member states’ committee and the EDPB, and the Commission can suspend, amend or repeal it if protection slips (Art. 3(4)–(5)). In court, the General Court dismissed an action to annul it on 3 September 2025, and an appeal to the Court of Justice was lodged on 31 October 2025. The Privacy Shield before it was struck down by that same court, so the appeal is worth a calendar reminder.

Check this

The framework only helps if the recipient is on the list on the day you rely on it. Look up Google LLC on the Data Privacy Framework List yourself, note its status and the date you checked, and keep that note with your records. We could not read the list’s entries with our tools.

What to do

Name the US transfer and the safeguard it rests on in your privacy notice, which must cover third-country transfers and their safeguards (Art. 13; the privacy policy checklist has the line), and in your record of processing where you keep one (Art. 30). Businesses established outside the EEA, the UK or Switzerland must accept Google’s data processing terms in Account Settings; our data processing agreement template lists what Art. 28(3) asks such terms to contain. The same transfer question comes up with AI tools; the GDPR and AI tools guide follows the chain to the model host.

The set-up sheet: what to be able to show

Regulators ask the site, so the useful question is not whether Google Analytics is compliant but whether you can show how your install handles each stop. This sheet puts the lines from the sections above in one place. If the GDPR reaches you at all, tracking people in the EU is one of the ways in; our guide on whether the GDPR applies to US companies covers that test, and the data map template has a column for each transfer.

Tick what your GA4 install already does. Nothing leaves your browser, and nothing is saved.

Where is your business established?
The transfer
The consent
The GA4 settings

Your sheet

0 of 12 in place

12 still open. Start with the transfer lines: those are what the Austrian and Italian cases turned on.

A working list, not legal advice and not a finding that a set-up is lawful.

The file in one box

Decisions against GA set-ups
Austria DSB 22 Dec 2021; Italy Garante 9 Jun 2022
What they turned on
The transfer to the US (GDPR Art. 44)
The route since
EU-US Data Privacy Framework, Decision (EU) 2023/1795 of 10 Jul 2023
Google on the framework
Relies on it for EEA data from 1 Sep 2023
In court
Annulment dismissed 3 Sep 2025 (T-553/23); appeal C-703/25 P lodged 31 Oct 2025
Still needed
Consent before _ga is stored (ePrivacy Art. 5(3)); default expiration 2 years
Processing terms
Built in for EEA, UK, CH businesses; accept in Account Settings elsewhere

Questions

Were the 2022 decisions about GA4 or the older version?

They looked at sites as they ran at the time: the Austrian complaint concerned a visit on 14 August 2020, and the Italian decision of 9 June 2022 a site as the Garante found it then. Both came before the 10 July 2023 adequacy decision. Some facts have moved since, such as how Google now says it handles EU IP addresses. The cookie and the site’s own responsibility have not.

Does the Data Privacy Framework mean I can drop the cookie banner?

No. The framework is about where personal data may go after collection. The banner answers a different rule, Art. 5(3) of the ePrivacy Directive, which asks for consent before the _ga cookie is stored, unless it is strictly necessary for a service the visitor asked for. Regulators differ on whether counting visits can be; the CNIL’s conditions above are one regulator’s answer.

What happens to my GA4 set-up if the Court of Justice annuls the framework?

We cannot say how the court will rule; the Court of Justice’s case list showed the appeal (C-703/25 P) still pending on 22 Oct 2026. What is on record: Google’s terms keep standard contractual clauses as the fallback where it no longer relies on a framework, and the Commission says the US safeguards behind the decision apply to transfers under clauses too. If the decision falls, read Google’s transfer page again and update your notice.

We are a US company. Do the EU decisions reach our GA4?

If the GDPR applies to you, yes: the transfer rules then cover your GA4 data like any other. Monitoring the behaviour of people in the EU is one of the ways the GDPR reaches a business outside it (Art. 3(2)(b)), and whether your analytics amounts to that depends on how you use it. Our guide on whether the GDPR applies to US companies walks through the test.

What does a transfer breach cost?

Transfers sit in the GDPR’s upper fine tier: up to EUR 20 000 000 or up to 4 % of total worldwide annual turnover of the preceding financial year, whichever is higher (Art. 83(5)). The cases on this page ended in findings, a reprimand and a deadline to fix the transfer, not in fines.

Related