Not legal advice. This article summarises a public regulatory decision and general GDPR principles. For your own situation, talk to your DPO or a lawyer.
On 21 September 2026, Ireland's Data Protection Commission (DPC) fined Google €403 million over how it processed location data. The decision concerns three Google account features (Web & App Activity, Location History and Location Accuracy) in the period from 25 May 2018 to 4 February 2020. The EDPB announced the decision on 23 September. Besides the fine, the DPC ordered Google to bring its processing into compliance within six months.
Why it matters beyond Google: the breaches the DPC found are about collecting by default, explaining purposes poorly and keeping data too long. Every website with analytics makes the same three choices, usually without thinking about them. This article covers what the DPC decided and turns it into a short check for your own setup.
The Google GDPR fine in brief
The DPC opened its own-volition inquiry into Google Ireland Limited in February 2020, acting as lead supervisory authority. It followed complaints from several European consumer organisations, including BEUC, about Google's processing of location data. The decision was taken by the three Commissioners for Data Protection, Des Hogan, Dale Sunderland and Niamh Sweeney, according to Irish Legal News.
According to the EDPB summary, the DPC found infringements of:
- Lawfulness and fairness of processing location data in Web & App Activity and Location History.
- Accountability for Location Accuracy: Google could not demonstrate compliance with the lawfulness, fairness and transparency principle.
- Transparency obligations for all three features.
- Retention: keeping location data in Web & App Activity and Location History longer than necessary.
The articles involved are Article 5 (principles, including storage limitation), Article 6 (lawful basis), Article 12 (transparent information) and Article 13 (information to give when data is collected). Deputy Commissioner Graham Doyle said that location data "can reveal a significant amount of information about an individual", as reported by the IAPP, and that keeping it longer than necessary deepened people's loss of control.
According to the IAPP, a Google spokesperson linked the penalty to "historical policies" for location data that Google says it has revised since 2019. The full text of the decision had not been published when this article was written, so some details, such as exactly how the fine is split across the infringements, are not yet public.
Why the dates matter
The decision covers conduct that ended more than six years ago. That says something about the pace of GDPR enforcement in big cross-border cases, but also that old settings can still be fined. If your analytics collected too much in 2022, the fact that you changed it in 2025 does not erase the earlier period. The EDPB's new fining guidelines, which we covered earlier this week, point the same way: a fine is meant to be the normal outcome of a serious breach, not the exception.
Three lessons for website owners
1. Default-on collection is a fairness problem
Two of the three features were found to breach lawfulness and fairness. The general lesson: if people cannot reasonably expect a type of collection, switching it on by default and burying the explanation is risky. For a website, the equivalent is an analytics tag that collects more than visitors would expect from "we count visits", such as precise location, cross-site identifiers or session recordings.
2. Vague purposes fail transparency
All three features breached transparency (Articles 12 and 13). Privacy notices that say data is used "to improve our services" do not tell people what happens with it. Doyle's remark that people may not have been aware how their location was used to target them with ads points at the same gap. For analytics, your privacy notice should name the tool, the data, the purpose and the retention period in plain words.
3. Keeping data too long is a breach on its own
The retention finding is the easiest one to learn from. Storage limitation (Article 5(1)(e)) means identifiable data may only be kept as long as the purpose requires. Many analytics accounts keep user-level data for the longest period available simply because nobody changed the default, or because more history "might be useful".
Check your own analytics: principle by principle
| GDPR principle | What Google got wrong (per the DPC) | What to check in your own analytics |
|---|---|---|
| Lawfulness and fairness (Art. 5(1)(a), Art. 6) | Processing of location data in Web & App Activity and Location History breached the lawfulness and fairness principles | What legal basis do you rely on? If your tool sets cookies or tracks individuals, do you have valid consent? |
| Transparency (Art. 12, 13) | Google breached its transparency obligations for all three location features | Does your privacy notice name your analytics tool, the data, the purpose and how long it is kept? |
| Accountability (Art. 5(2)) | Google could not show Location Accuracy complied with the core principle | Can you show your setup on paper: a record of processing, a DPA with the vendor, and where data is stored? |
| Storage limitation (Art. 5(1)(e)) | Location data was kept longer than necessary | What retention is set in your tool, and can you justify it? Is identifiable data kept longer than aggregated reports? |
| Data minimisation (Art. 5(1)(c)) | Not a separate finding in the EDPB summary, but the same question applies | Do you collect full IP addresses, precise location or user IDs that your reports do not need? |
A few concrete places to look:
- Retention settings. In GA4, for example, user-level and event data retention for standard properties can be set to 2 or 14 months; the setting affects Explorations and funnel reports, not standard aggregated reports. Pick the shortest period you actually use.
- Location granularity. Country or region is enough for most sites. City-level or precise location in analytics is hard to justify for a blog or shop.
- IP addresses. Check whether your tool stores IPs, truncates them or only uses them in transit. Ask your vendor in writing.
- Purpose limitation. If analytics data also flows to advertising (audiences, remarketing, data sharing settings), that is a second purpose with its own requirements. Turn off what you do not use.
- Where the data goes. Location and storage of the data matter too; see why your analytics data should stay in Europe.
For a fuller list, our GDPR analytics checklist has the twelve questions a DPO is likely to ask.
What this means for your analytics
The Google location data fine is not about website analytics, but its logic is: collect only what the purpose needs, say clearly what you do, and delete it when the purpose is served. ClearAnalytics is built along those lines. It sets no cookies, does not store IP addresses (unique visitors are counted with a hash of IP, user agent and a salt that rotates daily), keeps data in the EU and does not share visitor data with third parties or use it for advertising. If you want to see how that maps to your DPO's questions, start with the checklist.