The Dutch data protection authority, the Autoriteit Persoonsgegevens (AP), published its first full enforcement policy on 30 October 2026, after a public consultation. The part everyone is talking about is a settlement route that cuts a GDPR fine substantially. The price of that discount shows up later, and often somewhere else.
The Dutch DPA enforcement policy is the policy rule in which the Autoriteit Persoonsgegevens sets out how it chooses between a reprimand, an order subject to a penalty and a fine, how an enforcement procedure runs, and how a company can reduce a fine by up to 35% by admitting the violation and waiving objection and appeal. The policy was published in the Staatscourant 2026, 38702. If you run a company with 50 to 500 staff and the AP is your GDPR supervisor, the useful question isn't what the policy says. It's whether to take the discount. Sometimes yes. Often no.
What does the Dutch DPA enforcement policy change?
The Dutch DPA enforcement policy brings together in one document what used to be scattered or unwritten. The procedure itself still follows the Dutch General Administrative Law Act (Awb): investigation report, notice of intended enforcement, written views, decision. According to section 5.2 of the policy, that takes nine to eighteen months on average. Here's what's new or now written down:
| Element | What the policy says | Section |
|---|---|---|
| Acknowledgement and acquiescence procedure | Fine cut by up to 35% for admission, waiver of remedies, publication with press release | 5.6 |
| Remediation proposal | Allowed during the procedure, not an admission; the DPO's advice must be attached | 2.3 |
| Role of the DPO | Receives copies of report, notice, progress updates and decision | 2.5 |
| Late decisions | 5% off per full half-year past the 13-week decision period, capped at €5,000 per half-year | 3.1.6 |
| Preventive tools | Formal warning for planned processing, preventive order | 3.2 |
| DSA commitments | A commitment declared binding rules out a fine or penalty | 3.1.2 |
For companies, the AP calculates the fine itself under the EDPB Guidelines 04/2022, version 2.1 of 24 May 2023. The AP's own Boetebeleidsregels 2023 apply, under their article 2, only where those guidelines don't, such as to public bodies and to individuals not acting as a business. Anyone still modelling exposure with the 2019 fining rules is using rules that have been withdrawn.
How does the 35% settlement work?
The AP's settlement is formally called the erkennings- en berustingsprocedure (acknowledgement and acquiescence procedure), and it becomes available once the AP intends to impose a fine. The policy puts the trade this way: in return, the AP reduces the fine "met maximaal 35%", by at most 35%. That "at most" matters. It's a ceiling, not a fixed rate.
Three conditions apply together. You admit the established violation "clearly and unambiguously". You accept the fine, which means you file no objection, appeal or further appeal. And you agree to publication of the fining decision on the AP's website, with a press release that the AP also pushes through its social media channels. You get to see that press release in advance, but only to correct factual errors.
Section 5.6.2 adds the ground rules. The procedure starts only when both parties sign an agreement, either side can end it, and it's a one-time option. The policy is blunt: there is "uitdrukkelijk geen recht", expressly no right, to this way of closing a case. The AP only offers it where it expects efficiency gains.
One safeguard makes exploring it fairly low-risk. The exploration is confidential, and new information you share during it won't be used in the main case if the settlement fails, unless you consent. You can talk without weakening your position.
Worked example: a proposed €200,000 fine
A worked example makes the trade-off concrete. Every amount below is hypothetical and indicative; only the percentages and caps come from the policy.
Say the AP proposes a €200,000 fine for a data breach or an unlawful AI processing operation.
- Settlement, full discount: 35% × €200,000 = €70,000 off. You pay €130,000.
- Regular route, decision one full half-year late: 5% × €200,000 = €10,000, but the cap is €5,000. You're at €195,000 before objection or appeal achieves anything.
- Two full half-years late: 2 × €5,000 = €10,000 off, so €190,000.
For larger fines, the delay discount barely registers next to the settlement discount. The gap between €130,000 and €195,000 is €65,000; with a decision on time, it's the full €70,000. Add your own legal costs for objection, appeal and further appeal; call that L. The regular route only wins financially if you expect the objection stage or the courts to cut the fine by more than €65,000 + L. With an assumed L of €30,000, that's €95,000, close to half the fine.
There's a cash-flow effect on the other side. Under article 38 of the Dutch GDPR Implementation Act (UAVG), a fining decision is suspended while objection or appeal is pending, and section 5.2 of the policy confirms no interest accrues in that period. Litigate and you pay later. Settle and you pay now.
On the fine alone, settling often wins. What tips the balance is everything outside the fine.
When does settling with the Dutch DPA cost more than it saves?
Settling with the Dutch DPA costs more than it saves when the admission weighs more than €70,000 elsewhere. Three items decide that.
Damages claims from data subjects
Article 82 GDPR gives anyone who suffers material or non-material damage from a GDPR infringement the right to compensation from the controller. In the Netherlands, a foundation or association can bundle those claims under article 3:305a of the Dutch Civil Code, the basis of the WAMCA collective action regime. A public, final admission that you breached the GDPR is exactly the document a claimant starts with. Law firm Stibbe made the same point in its analysis of the policy on 3 November 2026.
The arithmetic is simple. If a breach affects 10,000 people, €70,000 divided by 10,000 is €7 per person. Every euro of compensation per data subject above that turns the discount negative. At 100,000 affected people, the line sits at 70 cents.
A prior violation on your record
Previous relevant infringements are a standing factor under article 83(2)(e) GDPR, and the policy applies those factors to the choice of every enforcement tool, not just fines. A settled case still counts as a prior violation later, Stibbe reported. That follows: with no objection or appeal, the decision becomes final as soon as the deadlines pass. A company running the same kind of processing in several places, say an AI tool using customer data in three business units, hands the AP an aggravating factor for the next case.
Your right to be proven right
Waiving remedies means a weak investigation report never gets tested. If the facts are disputable, or the case turns on an open legal question such as the lawful basis for training or fine-tuning a model on customer data, settling gives away the chance that a court reduces or annuls the fine.
Publication, on the other hand, is a smaller price than it looks. Since 1 September 2026, article 21b UAVG requires the AP to publish every fining decision, no earlier than ten working days after notifying you. Only a request for interim relief suspends that. What settlement adds is the press release, the social media push and, above all, the admission.
Settle or litigate: the call per situation
The choice between settling and litigating comes down to four questions: how solid are the facts, how clear is the rule, how many people were affected, and is the same processing still running elsewhere.
| Situation | Recommendation |
|---|---|
| Facts undisputed, rule clear (a breach notified late, for example), few people affected | Explore settlement; the discount is real money |
| Proposed fine small relative to expected legal costs | Settle |
| Facts or legal qualification disputable | Regular procedure |
| Thousands affected, or special categories of data | Regular procedure, unless claims are already resolved |
| A claims foundation has already come forward | Don't admit anything without litigation counsel in the room |
| Similar processing still running in other units | Stop that processing first, then decide |
Legal questions around AI end up in the third row more often than you'd expect. GDPR rules on profiling, automated decisions and reusing data for a new purpose are still being worked out for AI systems, and an admission locks in what a court might have seen differently. How the two regimes interact is covered in GDPR and AI: where the rules overlap.
What to set up now, before any investigation
The Dutch DPA enforcement policy rewards companies whose file is in order, and much of that runs through the data protection officer (DPO, or FG in Dutch).
- Register your DPO with the AP, if you have one. Under section 2.5, only a registered DPO automatically receives the investigation report, the notice, progress updates and the decision. The AP explicitly won't treat the DPO as your representative; the role stays independent.
- Get the DPO's advice in writing and record the follow-up. The policy weighs the extent to which the DPO flagged risks in data protection impact assessments, advice or other documents, and what you did with them. A DPIA where the DPO raised a warning that went nowhere works against you. Our step-by-step DPIA for an AI project shows where that advice belongs in the file.
- Attach the DPO's advice to any remediation proposal. If you want to discuss ending the violation with the AP during the procedure, the proposal has to be a concrete plan, and the DPO's advice on it must be attached. In practice: a dated, signed note from the DPO on that specific plan, submitted alongside your written views. Such a proposal doesn't count as an admission.
- End an ongoing violation immediately. For a continuing violation, the five-year limitation period under article 5:45 Awb only starts once it ends, and the policy weighs whether you stopped of your own accord, before or after learning of the investigation.
- Flag confidential business information early. If the investigation follows a complaint, the complainant receives a copy of the decision. Redaction only happens on a reasoned claim, assessed against the Dutch Open Government Act.
Make sure AI systems that process personal data keep logs that let you show afterwards what happened; see AI audit trails and logging for compliance. Who is liable when something does go wrong is covered in AI risks and liability.
What does the policy mean for AI supervision?
The Dutch DPA enforcement policy doesn't cover the AI Act yet. Annex I lists the rules the AP enforces today (the GDPR, the Data Act, the Digital Services Act, eIDAS, the political advertising regulation and a set of Dutch statutes) and says the list will be extended "in de toekomst", in future, with implementing legislation for the AI Act. Until that law exists, enforcement against AI applications runs through the GDPR, with exactly the tools and the settlement route above. Which regulator will be able to do what under the AI Act is set out in AI Act enforcement in the Netherlands; for the full regulatory picture, see our guide to AI legislation in the Netherlands and the EU AI Act.
If you build AI applications that process personal data, it helps when the file is right from the design stage: lawful basis, DPIA, DPO advice and logging. We set that up as part of AI consulting and custom software. Whether to settle a specific case is a question for a lawyer, not a software firm.