Privacy & GDPR

GDPR Fines in the Netherlands Will Now Always Be Made Public

From 1 September 2026 the Dutch DPA must publish its GDPR fines and other sanctions. What the new rule says and what it means for your website and analytics.

By Jasper Koers Published 6 min read

On this page
  1. What changes on 1 September 2026
  2. Why the Dutch DPA wants GDPR fines to be public
  3. The Uber GDPR fine as context
  4. What it means for websites, cookies and analytics
  5. What this means for your analytics

From 1 September 2026, a GDPR fine in the Netherlands also means being named in public. On 27 August 2026 the Dutch data protection authority, the Autoriteit Persoonsgegevens (AP), announced that it will be legally required to publish its GDPR sanctions: fines, orders under penalty and processing bans. Until now it did so under its own policy. A change to the Dutch GDPR Implementation Act (UAVG) turns that policy into a duty.

The timing is striking. Six days earlier, the AP fined Uber €824,990,000 for blocking drivers through fully automated decisions. Few organisations will ever face a fine of that size, but every organisation that does get a Dutch GDPR fine from September onwards will see its name and the decision published. This article explains what the new rule says, what it changes, and what it means for the most common thing every organisation has: a website with cookies and analytics.

Not legal advice. This article summarises the new Dutch rule and the AP's announcement. Ask your DPO or a lawyer how it applies to your organisation.

What changes on 1 September 2026

The legal basis is the Verzamelwet gegevensbescherming, a law of 10 June 2026 that updates the UAVG and several other Dutch laws. It was published in the Staatsblad on 26 June 2026 as Stb. 2026, 154. The publication duty was added to the bill by an amendment from the Dutch House of Representatives, something the AP says it had asked the legislator for over several years.

The new Article 21b UAVG says, in short:

  1. The AP publishes every decision in which it imposes an administrative sanction, unless the refusal grounds in Article 5.1(1), (2) and (5) of the Dutch Open Government Act (Woo) stand in the way.
  2. Publication happens no earlier than ten working days after the decision was made known to the organisation, unless the organisation published it itself, had it published, or said it has no objection to earlier publication.
  3. If the organisation asks a court for interim relief, publication is suspended until the judge has ruled or the request is withdrawn.
  4. The same applies to the AP's decision on an objection (bezwaar) that imposes a sanction.

The AP announced that the rule takes effect on 1 September 2026, and that it will adjust its own disclosure policy to match.

Which GDPR sanctions are published

Sanction Published from 1 September 2026?
Administrative fine (bestuurlijke boete) Yes, by law
Order under penalty (last onder dwangsom) Yes, by law
Processing ban (verwerkingsverbod) Yes, by law
Reprimand (berisping) Not named by the AP among the sanctions covered
Sanctions under the Police Data Act (Wpg) and Judicial Data Act (Wjsg) Yes, by AP policy choice, in the same way
Other AP documents Existing disclosure policy, unchanged

How the procedure works

The AP describes three steps. It first tells the organisation that it intends to publish the sanction and gives it the chance to respond. It then takes a final decision on publication. Only after that does it publish, with the ten-working-day waiting period described above.

An organisation can object to both the sanction and the publication, and can go to court to try to stop publication. But the starting point has flipped: publication is the rule, and the only legal grounds for keeping a decision private are those in the Woo.

Why the Dutch DPA wants GDPR fines to be public

The AP gives three reasons in its announcement:

  • Clarity about the norms. Published decisions show other organisations what went wrong and what they may need to fix themselves.
  • More effective enforcement. Publication adds weight to every sanction and should improve compliance with the GDPR.
  • Legal certainty. Because the duty is in the law rather than in AP policy, organisations know where they stand and what they can contest.

For businesses, the practical effect is that the reputational cost of a GDPR fine is now built in. A fine you consider unjustified, and plan to fight, will in most cases still be public while you fight it.

The Uber GDPR fine as context

The Uber decision of 21 August 2026 shows what a published AP decision looks like. According to the AP:

  • Uber automatically deactivated drivers' accounts, temporarily on suspicion of fraud or low customer ratings and permanently for persistently low ratings, without human assessment, between 2018 and 2022.
  • The AP found that this breached the GDPR's prohibition of fully automated decision-making (Article 22 GDPR), and that Uber did not sufficiently inform drivers about it.
  • The investigation started after 171 French drivers went to the human rights organisation Ligue des droits de l'Homme (LDH), which complained to the French regulator CNIL. Because Uber's European headquarters are in the Netherlands, the AP led the case under the GDPR's one-stop-shop mechanism.
  • The fine is €824,990,000. It is the AP's fourth fine for Uber, after €600,000 in 2018, €10 million in 2023 and €290 million in 2024. Uber has appealed, and according to the AP the proceedings over the 2023 and 2024 fines are still ongoing.

Uber's case is about algorithms, not websites. But it is a reminder that the AP enforces across the whole GDPR, and that it names the organisations it fines.

What it means for websites, cookies and analytics

For most organisations, the most visible piece of personal data processing is their website. That is also where the AP has been active. In April 2025 the AP warned 50 organisations about misleading cookie banners, the first of 500 it said it wanted to warn every year. The AP says it constantly monitors 10,000 Dutch websites, and warned that organisations that did not fix their banner within three months faced an investigation and "a high risk of a fine".

The examples of misleading banners the AP gave were concrete:

  • cookies placed before the visitor gives consent;
  • consent for tracking cookies pre-ticked in the banner;
  • a reject button that only appears after clicking through to a second screen.

Until now, the outcome of such a case might have stayed out of the news. From September, any fine that follows will be published with the organisation's name.

A quick self-check for your website

Question Why it matters
Does anything set tracking cookies or load trackers before consent? The AP lists this as a typical misleading-banner issue
Is refusing as easy as accepting, on the first screen? A reject button hidden on a second screen is on the AP's list
Are any consent boxes pre-ticked? Pre-ticked consent is on the AP's list
Do you know every third party your analytics and ads scripts send data to? You need to know this to explain it, and to answer a regulator
Is your analytics data processed and stored in the EU? Transfers outside the EU add legal requirements; see why your analytics data should stay in Europe
Do you have a processing agreement with your analytics provider? A processor needs a contract under Article 28 GDPR
Could you explain your setup to your DPO in five minutes? Use the GDPR analytics checklist to find out

If you answer "not sure" to the first three, those are the issues the AP has said it looks for, and fixing them is usually a matter of configuration rather than a new project.

What this means for your analytics

Mandatory publication doesn't change what the GDPR requires, but it raises the cost of getting it wrong. The simplest way to keep analytics off that list is to collect less: no tracking cookies, no data on the visitor's device, no transfers outside the EU. ClearAnalytics is built that way, with a daily-rotating hash instead of cookies and all data processed and stored in the EU, so it is designed to fit the profile where a consent banner shouldn't be needed for your analytics. See how ClearAnalytics compares with other tools.

Frequently asked questions

Does the Dutch DPA publish GDPR fines?

Yes. It already did so under its own policy, and from 1 September 2026 Article 21b UAVG makes publication of its sanction decisions a legal obligation, including the name of the organisation.

Which GDPR sanctions does the Autoriteit Persoonsgegevens have to publish?

The AP names fines, orders under penalty (lasten onder dwangsom) and processing bans. Reprimands are not on that list.

Can a company stop the Dutch DPA from publishing its fine?

Only in limited cases. Publication can be withheld on the refusal grounds of Article 5.1 of the Dutch Open Government Act, and asking a court for interim relief suspends publication until the judge rules.

How much was the Uber GDPR fine in the Netherlands?

On 21 August 2026 the Dutch DPA fined Uber €824,990,000 for automatically deactivating drivers without human review between 2018 and 2022. Uber has appealed.

Do cookie banners lead to GDPR fines in the Netherlands?

The Dutch DPA monitors 10,000 Dutch websites for misleading cookie banners and has warned organisations that fail to fix them that they run a high risk of a fine. From September 2026 any such fine is published by law.

  • gdpr-fines
  • dutch-dpa
  • enforcement
  • cookies
  • gdpr

Back to blog Read as markdown

Enjoyed this article?

Try ClearAnalytics for free and get privacy-first analytics for your website.