Data Protection Monitor
Global Privacy & Data Protection Intelligence

Netherlands Data Protection & Privacy Regulation

NL schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 126 claims · 111 sources in the cumulative register

The Autoriteit Persoonsgegevens (AP) published a vision document on generative artificial intelligence on 4 February 2026, naming artificial intelligence as a top enforcement priority for 2026 and beyond.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Sectoral Watch, AdTech & Commercial Privacy, Algorithmic, Biometric & Surveillance Governance, Children & Vulnerable Groups (5 open gaps).

Framework & posture10 of 10 modules active
10 active · 27 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix126 claims · 102 sources · machine-compiled
42 Confirmed76 Probable6 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Law made at European Economic Area (Bloc) level that applies in Netherlands is covered once, on the European Economic Area (Bloc) page. This page covers Netherlands’s own layer: implementation, national authorities, national options and local enforcement.

Jurisdiction brief

Latest update · 4 November 2026

Lead Signal

The Dutch Autoriteit Persoonsgegevens combined its largest-ever sanction with a structural transparency reform, materially raising the stakes of GDPR non-compliance in the Netherlands. The AP fined Uber EUR824,990,000 on 21 August 2026 for breaching Article 22 GDPR's prohibition on solely-automated decisions with significant effect, arising from automated driver-account deactivations between 2018 and 2022 conducted without meaningful human review, compounded by inadequate information given to affected drivers. The fine is the AP's fourth against Uber and the second-largest GDPR fine issued anywhere in the EU, after Meta's EUR1.2 billion penalty; Uber has announced it will appeal. The size and basis of the fine signal that automated decision-making without a genuine human-review layer remains a top-tier enforcement target for the AP, even where the underlying processing long preceded the enforcement action. Alongside this, a new procedural rule under Article 21b of the Uitvoeringswet AVG, introduced by the Verzamelwet gegevensbescherming and in force since 1 September 2026, establishes publication as the default position for AP enforcement decisions, including orders, fines and settlements, which must now be published no earlier than two weeks after the decision absent an exception applying. Together, the record fine and the new default-publication rule mean that both the financial and reputational consequences of an AP enforcement decision have increased in the same period.

Key regulatory facts for Netherlands
Key regulatory facts for Netherlands
Regulatory DimensionNetherlands Standing Position
JurisdictionNetherlands (NL)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 126 sourced findings)
Regulator & FrameworkComprehensive, mature omnibus regime fully aligned with GDPR; UAVG implementation is policy-neutral with narrow, well-documented derogations.
Lawful Processing & Special DataCore lawful-basis and special-category framework is GDPR-aligned with well-documented, narrowly tailored Dutch derogations.
Data Subject RightsDirectly-effective GDPR rights regime, actively enforced by the AP against obstructive controller practices.
Controller/Processor DutiesFull GDPR accountability regime in force, reinforced by an AP-published DPIA trigger list and active enforcement on security/health-data handling.
Primary Instruments CitedRecording Law, Law & More, European Data Protection Law Review (Lexxion), EUR-Lex, Tweede Kamer der Staten-Generaal
Last Confirmed / Updated (111 sources in cumulative register)

#

Comprehensive, mature omnibus regime fully aligned with GDPR; UAVG implementation is policy-neutral with narrow, well-documented derogations.

Primary frameworkGDPR (Regulation (EU) 2016/679) as implemented by the Uitvoeringswet Algemene verordening gegevensbescherming (UAVG)
Traffic-light rationale — GreenComprehensive, mature omnibus regime fully aligned with GDPR; UAVG implementation is policy-neutral with narrow, well-documented derogations.

Sub-modules (5)

Regulator and authorityGreen

The AP is the Article 51(1) GDPR supervisory authority, established under UAVG Chapter 2, headquartered in The Hague, currently chaired by Aleid Wolfsen.

Claims (3):

  • The Autoriteit Persoonsgegevens (AP), based in The Hague, is the Dutch national data protection supervisory authority designated under Article 51(1) GDPR.
  • Autoriteit Persoonsgegevens (AP) — The Netherlands' independent national data protection supervisory authority under Article 51 GDPR.
  • Uitvoeringswet Algemene verordening gegevensbescherming (UAVG) — AP is the national GDPR supervisory authority, designated under art. 51(1) GDPR via UAVG

Act and instrumentsGreen

GDPR applies directly; UAVG supplements it in a policy-neutral manner, continuing pre-GDPR Dutch law insofar as permitted.

Claims (8):

  • The Dutch GDPR Implementation Bill (UAVG) supplements the GDPR and is intended to implement it in a policy-neutral manner, continuing prior Dutch data protection law insofar as permitted by the GDPR.
  • Autoriteit Persoonsgegevens (AP) requires: New UAVG article 21b requires the AP to publish any decision imposing an administrative sanction (fine, penalty-payment order, processing ban), subject to Woo exceptions, converting prior discretionary policy into a statutory duty.
  • Autoriteit Persoonsgegevens (AP) subject to: Publication of an art. 21b sanction decision may not occur earlier than ten working days after notification to the offender, suspended pending a ruling if interim relief is sought under Awb art. 8:81.
  • Verzamelwet gegevensbescherming (UAVG amendment) — Amendments to UAVG (minors' rights, narrower criminal-data definition, stricter biometric conditions, mandatory publication of AP sanction decisions) commenced 2026-09-01 by royal decree of 2026-07-09, except one biometric-data provision (art. 29 UAVG) held back
  • Verzamelwet gegevensbescherming — Art. 21b UAVG establishes 'openbaar, tenzij' (public unless) as the default for AP enforcement decisions (orders, fines, settlements), to be published at the earliest two weeks after the decision.
  • UAVG (proposed amendment) — A proposal to amend the UAVG is in consultation as of 2026, including provisions to allow children aged 12 and above to make independent data-subject requests and to narrow the definition of criminal personal data.
  • GDPR + UAVG — Dutch data protection law rests on the directly-applicable GDPR and the national UAVG, both in force since 25 May 2018.
  • Verzamelwet gegevensbescherming — Art 41 UAVG tightened at consultation stage; AP raised compatibility doubt with Art 23 GDPR

Material scopeGreen

UAVG Article 2 applies to processing wholly or partly by automated means and to non-automated processing forming part of a filing system, mirroring GDPR Article 2/4.

Claims (1):

  • UAVG Article 2 provides that the Act and provisions based upon it apply to the processing of personal data wholly or partly by automated means and to processing that forms part of a filing system.

Territorial scopeGreen

The UAVG/GDPR regime extends to controllers/processors established in NL and to non-established controllers offering goods/services to, or monitoring the behaviour of, individuals in NL.

Claims (1):

  • The UAVG supplements GDPR with regard to personal data processed in the context of the activities of an establishment in the Netherlands, or related to offering goods/services to, or monitoring the behaviour of, individuals in the Netherlands.

Regulator registration and filingAmber

General notification duties were abolished under GDPR; a legacy Ministry-issued BCR permit regime was superseded by AP authorisation, with a risk of lapse absent timely AP action.

Claims (2):

  • Under the pre-GDPR Dutch Data Protection Act, binding corporate rules were authorised via a Ministry of Justice and Security permit; the GDPR Implementation Bill was silent on transitional treatment, creating a risk that such permits would lapse unless the AP issued its own authorisation.
  • Autoriteit Persoonsgegevens (AP) — Organisations to register a Data Protection Officer online with the AP, free of charge, whether the appointment is mandatory or voluntary.
Category narrative 103 words

The Netherlands is an EU Member State operating under the GDPR as the omnibus instrument, implemented and supplemented domestically by the Uitvoeringswet Algemene verordening gegevensbescherming (UAVG). The Autoriteit Persoonsgegevens (AP), seated in The Hague, is the designated national supervisory authority under Article 51(1) GDPR. Material and territorial scope follow the GDPR text as implemented policy-neutrally by the UAVG, including extraterritorial reach to non-established controllers targeting NL data subjects or monitoring behaviour occurring in NL. General notification/registration to the AP was abolished under GDPR in favour of accountability (ROPA, DPIA); a legacy BCR-permit regime under the Minister of Justice was replaced by AP authorisation.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (15)
  1. Confirmed EDPB — The Autoriteit Persoonsgegevens (AP), based in The Hague, is the Dutch national data protection supervisory authority designated under Article 51(1) GDPR. observed
  2. Confirmed IAPP — The Dutch GDPR Implementation Bill (UAVG) supplements the GDPR and is intended to implement it in a policy-neutral manner, continuing prior Dutch data protection law insofar as permitted by the GDPR. observed
  3. Confirmed DataGuidance — UAVG Article 2 provides that the Act and provisions based upon it apply to the processing of personal data wholly or partly by automated means and to processing that forms part of a filing system. observed
  4. Confirmed IAPP — The UAVG supplements GDPR with regard to personal data processed in the context of the activities of an establishment in the Netherlands, or related to offering goods/services to, or monitoring the behaviour of, individuals in the Netherlands. observed
  5. Probable IAPP — Under the pre-GDPR Dutch Data Protection Act, binding corporate rules were authorised via a Ministry of Justice and Security permit; the GDPR Implementation Bill was silent on transitional treatment, creating a risk that such permits would lapse unless the AP issued its own authorisation. observed
  6. Confirmed Overheid.nl (Ministerie van Justitie en Veiligheid) — Autoriteit Persoonsgegevens (AP) requires: New UAVG article 21b requires the AP to publish any decision imposing an administrative sanction (fine, penalty-payment order, processing ban), subject to Woo exceptions, converting prior discretionary policy into a statutory duty. observed
  7. Confirmed Overheid.nl (Ministerie van Justitie en Veiligheid) — Autoriteit Persoonsgegevens (AP) subject to: Publication of an art. 21b sanction decision may not occur earlier than ten working days after notification to the offender, suspended pending a ruling if interim relief is sought under Awb art. 8:81. observed
  8. Probable AVG Juristen — Verzamelwet gegevensbescherming (UAVG amendment) — Amendments to UAVG (minors' rights, narrower criminal-data definition, stricter biometric conditions, mandatory publication of AP sanction decisions) commenced 2026-09-01 by royal decree of 2026-07-09, except one biometric-data provision (art. 29 UAVG) held back observed
  9. Probable Lexology — Verzamelwet gegevensbescherming — Art. 21b UAVG establishes 'openbaar, tenzij' (public unless) as the default for AP enforcement decisions (orders, fines, settlements), to be published at the earliest two weeks after the decision. observed
  10. Uncertain Recording Law — UAVG (proposed amendment) — A proposal to amend the UAVG is in consultation as of 2026, including provisions to allow children aged 12 and above to make independent data-subject requests and to narrow the definition of criminal personal data. observed
  11. Confirmed Stibbe — Autoriteit Persoonsgegevens (AP) — The Netherlands' independent national data protection supervisory authority under Article 51 GDPR. observed
  12. Confirmed mijnevent.nl — GDPR + UAVG — Dutch data protection law rests on the directly-applicable GDPR and the national UAVG, both in force since 25 May 2018. observed
  13. Probable Officiële Bekendmakingen — Autoriteit Persoonsgegevens (AP) — Organisations to register a Data Protection Officer online with the AP, free of charge, whether the appointment is mandatory or voluntary. observed
  14. Confirmed Overheid.nl — Uitvoeringswet Algemene verordening gegevensbescherming (UAVG) — AP is the national GDPR supervisory authority, designated under art. 51(1) GDPR via UAVG observed
  15. Uncertain InView / Onderneming en Recht — Verzamelwet gegevensbescherming — Art 41 UAVG tightened at consultation stage; AP raised compatibility doubt with Art 23 GDPR observed

#

Core lawful-basis and special-category framework is GDPR-aligned with well-documented, narrowly tailored Dutch derogations.

Primary frameworkGDPR Articles 6, 7, 9 as supplemented by UAVG Chapter 3
Traffic-light rationale — GreenCore lawful-basis and special-category framework is GDPR-aligned with well-documented, narrowly tailored Dutch derogations.

Sub-modules (4)

Lawful basesGreen

The six GDPR Article 6 lawful bases (consent, contract, legal obligation, vital interests, public task, legitimate interests) apply directly and exhaustively in NL.

Claims (1):

  • Data controllers in the Netherlands may only process personal data where one of the GDPR Article 6 lawful bases applies, including consent, contractual necessity, legal obligation, vital interests, public-interest task, or legitimate interests.

Special categoriesAmber

UAVG Chapter 3 layers additional, sector-specific exceptions onto GDPR Article 9 for controllers such as hospitals, schools and insurers.

Claims (4):

  • UAVG Chapter 3 provides generic exceptions (e.g., explicit consent) alongside specific per-category exceptions allowing defined controllers such as hospitals, schools and insurance companies to process special categories of data for defined purposes (identification, sick-leave management, benefits, pre-employment screening, crime prevention).
  • Autoriteit Persoonsgegevens (AP) — Ten Dutch municipalities a combined €250,000 in February 2026 for commissioning or receiving 'quickscans' mapping local Islamic-community structures without a valid legal basis for processing special-category data.
  • UAVG Art 22 — Processing of special categories of personal data is prohibited unless a statutory exception under art. 9(2) GDPR (as implemented) applies
  • UAVG Art 23/23a — Art 23 UAVG sets further national exceptions to special-category prohibition (Ombudsman, AP, NIHR), and Art 23a allows accountants to process special-category data for statutory audits if pseudonymised

Pseudonymisation and anonymisationAmber

Biometric data processing is restricted under UAVG Article 29 to cases of strict necessity for authentication or security purposes, addressing a gap left by the GDPR's blanket Article 9 prohibition.

Claims (2):

  • UAVG Article 29 permits processing of biometric data for unique identification only where strictly necessary for authentication or security purposes, addressing a gap in GDPR Article 9 that otherwise lacked a workable workplace-biometrics exception.
  • CJEU, EDPS v SRB (C-413/23 P) — CJEU set aside the General Court's 2023 ruling, clarifying that whether pseudonymised data is personal data depends on a relative, case-specific identifiability assessment; whether this is anchored to discloser's or recipient's perspective remains contested
Category narrative 94 words

Lawful bases and consent standards follow GDPR Articles 6 and 7 directly. The Netherlands set the child consent age threshold for information-society-service consent at 16 (the GDPR default, not exercising the Member-State option to lower it to as little as 13). UAVG Chapter 3 supplies sector-specific exceptions permitting processing of special-category data (health, biometric, criminal) by defined controller categories (hospitals, schools, insurers) for defined purposes, and restricts biometric processing to strict necessity for authentication/security. A pending 'Data Protection Collective Act' bill would adjust several special-data and children's-consent provisions but is not yet in force.

Sources and claims (10)
  1. Confirmed EDPB — Data controllers in the Netherlands may only process personal data where one of the GDPR Article 6 lawful bases applies, including consent, contractual necessity, legal obligation, vital interests, public-interest task, or legitimate interests. observed
  2. Confirmed EUR-Lex — Under GDPR Article 8(1), processing of a child's data based on consent for direct offer of information-society services is lawful where the child is at least 16; below that age, parental/guardian consent is required, with Member States able to lower this to no less than 13. observed
  3. Confirmed IAPP — The Dutch GDPR Implementation Bill reiterates age 16 as the applicable threshold for Article 8 GDPR consent, matching the prior Dutch Data Protection Act age limit rather than exercising the option to lower it to 13. observed
  4. Confirmed IAPP — UAVG Chapter 3 provides generic exceptions (e.g., explicit consent) alongside specific per-category exceptions allowing defined controllers such as hospitals, schools and insurance companies to process special categories of data for defined purposes (identification, sick-leave management, benefits, pre-employment screening, crime prevention). observed
  5. Confirmed AP/EDPB — UAVG Article 29 permits processing of biometric data for unique identification only where strictly necessary for authentication or security purposes, addressing a gap in GDPR Article 9 that otherwise lacked a workable workplace-biometrics exception. observed
  6. Probable VNG — Autoriteit Persoonsgegevens (AP) — Ten Dutch municipalities a combined €250,000 in February 2026 for commissioning or receiving 'quickscans' mapping local Islamic-community structures without a valid legal basis for processing special-category data. observed
  7. Confirmed Overheid.nl (Ministerie van Justitie en Veiligheid) — UAVG Art 5 (as amended) — Where consent under art. 4(11) GDPR is relied on and the data subject is under 16, consent must be given or authorised by the legal representative (parallel rule for persons under guardianship) observed
  8. Confirmed Overheid.nl — UAVG Art 22 — Processing of special categories of personal data is prohibited unless a statutory exception under art. 9(2) GDPR (as implemented) applies observed
  9. Probable Tweede Kamer der Staten-Generaal — UAVG Art 23/23a — Art 23 UAVG sets further national exceptions to special-category prohibition (Ombudsman, AP, NIHR), and Art 23a allows accountants to process special-category data for statutory audits if pseudonymised observed
  10. Disputed Covington & Burling (Inside Privacy) — CJEU, EDPS v SRB (C-413/23 P) — CJEU set aside the General Court's 2023 ruling, clarifying that whether pseudonymised data is personal data depends on a relative, case-specific identifiability assessment; whether this is anchored to discloser's or recipient's perspective remains contested observed

#

Directly-effective GDPR rights regime, actively enforced by the AP against obstructive controller practices.

Primary frameworkGDPR Articles 12-22
Traffic-light rationale — GreenDirectly-effective GDPR rights regime, actively enforced by the AP against obstructive controller practices.

Sub-modules (5)

Access rightGreen

Access rights follow GDPR Article 15; AP enforcement confirms controllers may not impose disproportionate identity-verification barriers (e.g., mandatory ID-copy uploads) on access/erasure requests.

Claims (3):

  • The AP fined DPG Media Magazines €525,000 for infringing GDPR Article 12(2) by requiring individuals to upload a copy of their identity document before honouring access or erasure requests, without informing them they could redact data.
  • Autoriteit Persoonsgegevens (AP) — Data subjects in the Netherlands may exercise GDPR Chapter III rights via the controller, with AP enforcement backing.
  • UAVG Art 41(1) — Access right may be limited on a case-by-case basis to safeguard an Art 23(1) GDPR interest, including protection of the data subject or others' rights; no categorical restriction permitted

Rectification and erasureGreen

Controllers must notify recipients of any rectification, erasure, or restriction under Article 19 GDPR unless impossible or disproportionate.

Claims (1):

  • Under GDPR Article 19, controllers must communicate any rectification, erasure or restriction of processing to each recipient to whom the data were disclosed, unless this proves impossible or involves disproportionate effort, and must inform the data subject of those recipients on request.

Restriction and objectionGreen

Restriction and objection rights follow GDPR Articles 18 and 21 directly with no NL-specific derogation identified.

Data portabilityGreen

Portability follows GDPR Article 20, applying where processing is based on consent or contract and carried out by automated means.

Claims (1):

  • Under GDPR Article 20, the data subject has the right to receive personal data provided to a controller in a structured, commonly used, machine-readable format and to transmit it to another controller without hindrance where technically feasible.

Deadlines and response windowsGreen

Controllers must respond to data subject requests without undue delay and within one month, extendable by two further months for complex/numerous requests, per GDPR Article 12(3).

Claims (3):

  • GDPR Article 12(3) requires controllers to respond to data subject rights requests without undue delay and within one month of receipt, extendable by a further two months for complex or numerous requests, applying directly in the Netherlands.
  • Verzamelwet gegevensbescherming (UAVG Art 5 tiered minors regime) — Tiered regime for minors exercising Chapter III GDPR rights from 2026-09-01: under 12 only legal representative acts; 12-16 either data subject or representative; data subject alone may withdraw consent from age 12; guardians represent those under guardianship
  • GDPR Art 12(3)/Art 15 — Controller must respond to an access request within one month, extendable by two further months for complex/numerous requests
Category narrative 48 words

Data subject rights in NL derive directly from GDPR Chapter III (access, rectification, erasure, restriction, objection, portability) with no material Dutch derogation. AP enforcement practice (e.g., the DPG Media Magazines fine) illustrates active supervision of the access/erasure request process, specifically prohibiting disproportionate identity-verification demands that obstruct rights exercise.

Periodic update · new data 2026-09-28

A proposal to amend the UAVG is reported to be in consultation as of 2026, which would extend independent data-subject-request capacity to children aged 12 and above, and would narrow the definition of criminal personal data under Dutch law. This proposal has not been enacted, and its current legislative stage and expected effective date are not established to a primary source this cycle; reports suggest it remains at consultation stage without a confirmed timeline for enactment.

If enacted, this amendment would mark a structural change to who may exercise data-subject rights independently under Dutch law, lowering the effective age threshold for autonomous exercise of access, rectification, and erasure rights below the general default position that typically requires parental involvement for younger data subjects. The narrowing of the criminal-personal-data definition referenced in the same proposal is a related but distinct change affecting the special-category processing rules applicable to criminal-record information.

Outlook

The UAVG amendment's progression from consultation toward a confirmed legislative timetable is the clearest item to watch for the data-subject-rights dimension of the Dutch framework. Until a primary legislative source confirms the stage and expected effective date, this remains a reported but unconfirmed development.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (9)
  1. Confirmed AP/EDPB — The AP fined DPG Media Magazines €525,000 for infringing GDPR Article 12(2) by requiring individuals to upload a copy of their identity document before honouring access or erasure requests, without informing them they could redact data. observed
  2. Confirmed EUR-Lex — Under GDPR Article 19, controllers must communicate any rectification, erasure or restriction of processing to each recipient to whom the data were disclosed, unless this proves impossible or involves disproportionate effort, and must inform the data subject of those recipients on request. observed
  3. Confirmed EUR-Lex — Under GDPR Article 20, the data subject has the right to receive personal data provided to a controller in a structured, commonly used, machine-readable format and to transmit it to another controller without hindrance where technically feasible. observed
  4. Confirmed EUR-Lex — GDPR Article 12(3) requires controllers to respond to data subject rights requests without undue delay and within one month of receipt, extendable by a further two months for complex or numerous requests, applying directly in the Netherlands. observed
  5. Probable mijnevent.nl — Autoriteit Persoonsgegevens (AP) — Data subjects in the Netherlands may exercise GDPR Chapter III rights via the controller, with AP enforcement backing. observed
  6. Confirmed Overheid.nl (Ministerie van Justitie en Veiligheid) — UAVG Art 5(5) (as amended) — A minor data subject who has reached age 16 may bring proceedings for breach of GDPR rights without assistance of their legal representative observed
  7. Probable AVG Juristen — Verzamelwet gegevensbescherming (UAVG Art 5 tiered minors regime) — Tiered regime for minors exercising Chapter III GDPR rights from 2026-09-01: under 12 only legal representative acts; 12-16 either data subject or representative; data subject alone may withdraw consent from age 12; guardians represent those under guardianship observed
  8. Probable Belastingdienst Kennisgroepen — GDPR Art 12(3)/Art 15 — Controller must respond to an access request within one month, extendable by two further months for complex/numerous requests observed
  9. Probable Holla Advocaten — UAVG Art 41(1) — Access right may be limited on a case-by-case basis to safeguard an Art 23(1) GDPR interest, including protection of the data subject or others' rights; no categorical restriction permitted observed

#

Full GDPR accountability regime in force, reinforced by an AP-published DPIA trigger list and active enforcement on security/health-data handling.

Primary frameworkGDPR Articles 24-39, UAVG, Works Councils Act (WOR) Article 27
Traffic-light rationale — GreenFull GDPR accountability regime in force, reinforced by an AP-published DPIA trigger list and active enforcement on security/health-data handling.

Sub-modules (7)

Accountability & DPIAGreen

The AP has published a binding national list of processing operations requiring a DPIA, including large-scale/systematic employee monitoring, covert camera surveillance for fraud prevention, and large-scale biometric identification.

Claims (2):

  • The AP's published DPIA list requires a mandatory data protection impact assessment for, among other things, large-scale and/or systematic monitoring of employee activity, covert camera surveillance for theft/fraud prevention, and large-scale processing for unique identification.
  • AP Besluit lijst verwerkingen DPIA — Binding non-exhaustive list of 17 categories of processing for which DPIA is always mandatory before processing begins

DPO requirementsGreen

DPO appointment follows GDPR Article 37 thresholds (public authorities, large-scale monitoring, large-scale special-category processing); DPO positioning was the subject of a 2023 EDPB coordinated enforcement action in which the AP participated.

Claims (2):

  • The EDPB's 2023 Coordinated Enforcement Framework action, in which the AP participates as an EEA supervisory authority, focused specifically on the designation and positioning of Data Protection Officers.
  • controller/processor — DPO mandatory where public authority (except courts acting judicially), large-scale regular/systematic monitoring, or large-scale special-category/criminal-conviction processing

Ropa requirementsGreen

Controllers and processors must maintain records of processing activities under GDPR Article 30; no NL-specific derogation identified for the general regime (a separate, distinct ROPA duty exists under the Law Enforcement Directive regime for police data, outside this baseline's GDPR scope).

Claims (1):

  • Records of processing obligation — Enterprises with <250 employees exempt from records of processing unless risk, non-occasional, or special-category/criminal data

Joint controller arrangementsGreen

Joint-controller arrangements follow GDPR Article 26 directly; no NL-specific overlay identified.

Claims (1):

  • controller/processor — Processor contract in writing; sub-processor engagement requires prior written authorisation; processor remains liable

Security measuresAmber

Security-of-processing obligations under GDPR Article 32 are actively enforced; the AP fined an employer for maintaining an internet-accessible sick-leave register without multi-factor authentication.

Claims (1):

  • The AP fined employer CP&A for security failings after its online sick-leave register, containing health data, was accessible without multi-factor authentication, finding that internet-accessible sick-leave systems require MFA beyond a regular login.

Breach notificationGreen

Breach notification duties follow GDPR Articles 33-34: notify the AP within 72 hours of becoming aware unless unlikely to result in risk, and notify affected individuals without undue delay where high risk is likely.

Claims (3):

  • Under GDPR Article 33, controllers must notify the competent supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals' rights and freedoms.
  • Autoriteit Persoonsgegevens — Notification of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware, unless unlikely to result in risk to rights and freedoms
  • controller — Communication of high-risk breach to data subjects; internal breach register under Art 33(5)

Retention and disposalAmber

Retention limitation follows the GDPR storage-limitation principle (Article 5(1)(e)); no NL-specific statutory retention schedule identified at the omnibus level beyond sectoral rules.

Category narrative 75 words

Controllers and processors are subject to the full GDPR accountability toolkit. The AP has published a binding national DPIA 'blacklist' identifying processing types requiring a mandatory DPIA (large-scale employee monitoring, covert camera surveillance, large-scale biometric identification). Breach notification follows GDPR Articles 33-34 (72-hour regulator notification; subject notification where high risk). AP enforcement demonstrates active supervision of security-of-processing duties for sensitive employee health data, and Dutch Works Councils hold a statutory co-determination right over personnel-monitoring systems.

Sources and claims (10)
  1. Confirmed AP/EDPB — The AP's published DPIA list requires a mandatory data protection impact assessment for, among other things, large-scale and/or systematic monitoring of employee activity, covert camera surveillance for theft/fraud prevention, and large-scale processing for unique identification. observed
  2. Confirmed IAPP — The EDPB's 2023 Coordinated Enforcement Framework action, in which the AP participates as an EEA supervisory authority, focused specifically on the designation and positioning of Data Protection Officers. observed
  3. Confirmed AP/EDPB — The AP fined employer CP&A for security failings after its online sick-leave register, containing health data, was accessible without multi-factor authentication, finding that internet-accessible sick-leave systems require MFA beyond a regular login. observed
  4. Confirmed EDPB — Under GDPR Article 33, controllers must notify the competent supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals' rights and freedoms. observed
  5. Probable Nationaal Cyber Security Centrum (NCSC) — Autoriteit Persoonsgegevens — Notification of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware, unless unlikely to result in risk to rights and freedoms observed
  6. Probable MKB Juristen — controller — Communication of high-risk breach to data subjects; internal breach register under Art 33(5) observed
  7. Confirmed Autoriteit Persoonsgegevens / Overheid.nl — AP Besluit lijst verwerkingen DPIA — Binding non-exhaustive list of 17 categories of processing for which DPIA is always mandatory before processing begins observed
  8. Probable Law & More — controller/processor — DPO mandatory where public authority (except courts acting judicially), large-scale regular/systematic monitoring, or large-scale special-category/criminal-conviction processing observed
  9. Probable Daily Data Bytes — controller/processor — Processor contract in writing; sub-processor engagement requires prior written authorisation; processor remains liable observed
  10. Uncertain Virtio ICT — Records of processing obligation — Enterprises with <250 employees exempt from records of processing unless risk, non-occasional, or special-category/criminal data observed

#

Standard GDPR Chapter V transfer toolkit applies uniformly; no NL-specific localisation mandate identified.

Primary frameworkGDPR Articles 44-49
Traffic-light rationale — GreenStandard GDPR Chapter V transfer toolkit applies uniformly; no NL-specific localisation mandate identified.

Sub-modules (6)

Transfer mechanismsGreen

Transfers rely on Commission adequacy decisions, SCCs, BCRs, or Article 49 derogations, applying directly under GDPR Chapter V.

Claims (3):

  • Cross-border transfers of personal data from the Netherlands to third countries rely on the GDPR Chapter V toolkit: European Commission adequacy decisions, Standard Contractual Clauses, Binding Corporate Rules, or Article 49 derogations.
  • The AP fined MLU B.V. (Yango) EUR100 million for transferring personal data of Norwegian and Finnish taxi-app users and drivers to companies in Russia without ensuring adequate data protection.
  • EDPB Guidelines on Art 48 GDPR (third-country authority access) — Where an organisation responds to a third-country authority's request for personal data, that data flow constitutes a transfer and GDPR applies

Adequacy receivedGreen

As an EU Member State, NL does not receive bilateral adequacy from third countries; it operates within the EU's mutual-recognition (GDPR-internal) framework rather than a receiving-adequacy structure.

Claims (1):

  • EU-US Data Privacy Framework adequacy decision (2023/1795) — Remains fully operative; General Court dismissed annulment action (Case T-553/23) on 3 September 2025; appeal lodged to CJEU (Case C-703/25 P) on 31 October 2025

Adequacy grantedGreen

Adequacy decisions granted to third countries (e.g., the UK) are adopted at EU level by the European Commission and apply automatically in NL; the UK adequacy decisions are currently under an EDPB-reviewed extension process.

Claims (1):

  • The EDPB adopted opinions on the European Commission's draft decisions extending the validity of the UK adequacy decisions under the GDPR and the Law Enforcement Directive, an EU-wide determination that applies automatically in the Netherlands as an EU Member State.

SCCs and BCRsAmber

BCR authorisation in NL transitioned from a Ministry of Justice permit system to AP approval under GDPR; legacy permits faced a risk of lapse absent timely AP authorisation.

Claims (2):

  • Binding Corporate Rules previously authorised under a Ministry of Justice and Security permit faced a risk of becoming null and void from 25 May 2018 unless the AP issued its own GDPR-era authorisation, as the GDPR Implementation Bill did not expressly address transitional treatment.
  • Standard Contractual Clauses (2021/914) — 2021 modular SCCs are the standard clause set for transfers absent adequacy; old SCCs could not be relied on for new transfers after 27 December 2022

Transfer impact assessmentAmber

TIA obligations follow the EDPB's general post-Schrems II recommendations, applied by the AP as an EEA authority; no NL-specific TIA methodology beyond EDPB guidance was identified.

Claims (1):

  • Transfer impact assessment — Exporter must map transfer, verify tool, assess third-country law/practice against Schrems II 'essentially equivalent' standard, identify supplementary measures, implement, and periodically re-evaluate

Data localisationRed

No general data-localisation mandate exists in the Dutch omnibus DP regime.

Claims (2):

  • Kabinet antwoord Kamervragen Cloud Act — In October 2026 the government confirmed for the first time that the US CLOUD Act can conflict with GDPR and NEN 7510, with secret US government requests possible for Dutch-hosted healthcare data
  • Dutch government cloud and cybersecurity practice — No general statutory data-localisation duty under GDPR; Rijksbreed cloudbeleid is an administrative (non-statutory) constraint for central government cloud use
Category narrative 63 words

As an EU Member State, NL's cross-border transfer regime is governed directly by GDPR Chapter V: adequacy decisions issued by the European Commission apply uniformly across the EU including NL (e.g., ongoing extension of UK adequacy), alongside SCCs, BCRs and Article 49 derogations. The pre-GDPR Ministerial BCR-permit system was replaced by AP authorisation. No general data-localisation mandate exists in the Dutch omnibus regime.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (10)
  1. Confirmed EUR-Lex — Cross-border transfers of personal data from the Netherlands to third countries rely on the GDPR Chapter V toolkit: European Commission adequacy decisions, Standard Contractual Clauses, Binding Corporate Rules, or Article 49 derogations. observed
  2. Probable EDPB — The EDPB adopted opinions on the European Commission's draft decisions extending the validity of the UK adequacy decisions under the GDPR and the Law Enforcement Directive, an EU-wide determination that applies automatically in the Netherlands as an EU Member State. observed
  3. Probable IAPP — Binding Corporate Rules previously authorised under a Ministry of Justice and Security permit faced a risk of becoming null and void from 25 May 2018 unless the AP issued its own GDPR-era authorisation, as the GDPR Implementation Bill did not expressly address transitional treatment. observed
  4. Probable Computable — Kabinet antwoord Kamervragen Cloud Act — In October 2026 the government confirmed for the first time that the US CLOUD Act can conflict with GDPR and NEN 7510, with secret US government requests possible for Dutch-hosted healthcare data observed
  5. Confirmed Binnenlands Bestuur — The AP fined MLU B.V. (Yango) EUR100 million for transferring personal data of Norwegian and Finnish taxi-app users and drivers to companies in Russia without ensuring adequate data protection. observed
  6. Probable European Data Protection Board — EDPB Guidelines on Art 48 GDPR (third-country authority access) — Where an organisation responds to a third-country authority's request for personal data, that data flow constitutes a transfer and GDPR applies observed
  7. Probable European Data Protection Law Review (Lexxion) — EU-US Data Privacy Framework adequacy decision (2023/1795) — Remains fully operative; General Court dismissed annulment action (Case T-553/23) on 3 September 2025; appeal lodged to CJEU (Case C-703/25 P) on 31 October 2025 observed
  8. Probable Praxikon — Transfer impact assessment — Exporter must map transfer, verify tool, assess third-country law/practice against Schrems II 'essentially equivalent' standard, identify supplementary measures, implement, and periodically re-evaluate observed
  9. Probable Timelex — Standard Contractual Clauses (2021/914) — 2021 modular SCCs are the standard clause set for transfers absent adequacy; old SCCs could not be relied on for new transfers after 27 December 2022 observed
  10. Probable MailCamp — Dutch government cloud and cybersecurity practice — No general statutory data-localisation duty under GDPR; Rijksbreed cloudbeleid is an administrative (non-statutory) constraint for central government cloud use observed

#

Telecoms/ePrivacy and employment overlays are well documented; credit-scoring and education sub-modules lack NL-specific findings.

Primary frameworkTelecommunicatiewet (transposing ePrivacy Directive 2002/58/EC); UAVG Chapter 3; Works Councils Act (WOR)
Traffic-light rationale — AmberTelecoms/ePrivacy and employment overlays are well documented; credit-scoring and education sub-modules lack NL-specific findings.

Sub-modules (7)

Financial sector overlayAmber

No NL-specific financial-sector DP overlay beyond general GDPR/UAVG was surfaced in this run; AFM/DNB prudential rules interact with but do not supplant AP jurisdiction over personal data.

Claims (2):

  • DORA (Regulation (EU) 2022/2554) — DORA has applied directly in the Netherlands since 17 January 2025, with DNB as primary supervisor requiring ICT risk-management frameworks from in-scope financial entities.
  • PSD2 open-banking data sharing supervision — DNB/AFM for financial conduct/licensing, ACM for payment-system access, AP for GDPR compliance of account/payment-initiation data sharing

Health sector overlayGreen

UAVG Chapter 3 grants hospitals and other health controllers specific exceptions to process special-category health data for defined purposes.

Claims (1):

  • UAVG Chapter 3 provides sector-specific exceptions allowing hospitals, schools, and insurance companies to process special categories of personal data for defined purposes such as identification, sick-leave management, benefits/pensions, and pre-employment screening.

Telecoms and eprivacyGreen

The Telecommunicatiewet transposes the ePrivacy Directive, including cookie-consent and confidentiality-of-communications rules.

Claims (2):

  • The Telecommunications Act (Telecommunicatiewet) is the primary legislation governing telecommunications in the Netherlands and includes a chapter on privacy transposing the ePrivacy Directive (2002/58/EC as amended).
  • Wet bewaarplicht telecommunicatiegegevens — Disapplied by the Hague District Court on 11 March 2015 following CJEU invalidation of the Data Retention Directive

Employment dataAmber

Dutch Works Councils hold a statutory co-determination/consent right over the introduction of personnel-tracking and monitoring systems, and the AP publishes guidance to support Works Councils in assessing GDPR-compliance of such systems.

Claims (3):

  • The AP published a Works Council privacy booklet covering the right of consent and assessment questions for personnel-tracking systems, supporting Works Councils in evaluating whether employer monitoring plans are GDPR-compliant.
  • Employer personnel data-processing scheme — Works council consent required before adopting, amending or withdrawing a personnel data-processing scheme
  • Employer personnel-monitoring facility — Works council consent required before introducing personnel-monitoring facilities (attendance, behaviour, performance)

Credit and scoringRed

No NL-specific credit-scoring overlay was identified in this run beyond general GDPR Article 22 automated-decision-making protections.

educationRed

No NL-specific education-sector DP statute distinct from UAVG general exceptions was identified.

insuranceGreen

UAVG Chapter 3 grants insurance companies specific exceptions to process special-category data for underwriting and claims purposes.

Claims (1):

  • UAVG Chapter 3 provides sector-specific exceptions allowing hospitals, schools, and insurance companies to process special categories of personal data for defined purposes such as identification, sick-leave management, benefits/pensions, and pre-employment screening.
Category narrative 69 words

Telecommunications and electronic-communications processing is governed by the Telecommunicatiewet, transposing the ePrivacy Directive, including the cookie-consent rule and a July 2021 shift to opt-in consent for telemarketing to natural persons (abolishing the do-not-call register). Employment-sector processing is subject to Works Council co-determination rights over personnel-monitoring/tracking systems. Health and insurance sectors benefit from UAVG special-category exceptions. No NL-specific credit-scoring or education-sector DP overlay was identified beyond the general GDPR/UAVG regime.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (10)
  1. Confirmed IAPP — UAVG Chapter 3 provides sector-specific exceptions allowing hospitals, schools, and insurance companies to process special categories of personal data for defined purposes such as identification, sick-leave management, benefits/pensions, and pre-employment screening. observed
  2. Confirmed DataGuidance — The Telecommunications Act (Telecommunicatiewet) is the primary legislation governing telecommunications in the Netherlands and includes a chapter on privacy transposing the ePrivacy Directive (2002/58/EC as amended). observed
  3. Confirmed DataGuidance — The AP published a Works Council privacy booklet covering the right of consent and assessment questions for personnel-tracking systems, supporting Works Councils in evaluating whether employer monitoring plans are GDPR-compliant. observed
  4. Probable Autoriteit Consument en Markt — The Dutch Data Act implementing act came into effect on 21 November 2025, authorising ACM to enforce Regulation (EU) 2023/2854 against cloud providers and smart-device manufacturers headquartered in NL, covering data-sharing/access requests and cloud-switching/interoperability barriers. observed
  5. Probable financialregulations.eu — DORA (Regulation (EU) 2022/2554) — DORA has applied directly in the Netherlands since 17 January 2025, with DNB as primary supervisor requiring ICT risk-management frameworks from in-scope financial entities. observed
  6. Confirmed Autoriteit Persoonsgegevens — Data Act / Uitvoeringswet dataverordening — ACM designated for most of the Data Act (product data, B2B sharing, cloud switching); AP for GDPR-related provisions of Chapter II observed
  7. Confirmed De Nederlandsche Bank — PSD2 open-banking data sharing supervision — DNB/AFM for financial conduct/licensing, ACM for payment-system access, AP for GDPR compliance of account/payment-initiation data sharing observed
  8. Probable Inview (legal database reproducing WOR text) — Employer personnel data-processing scheme — Works council consent required before adopting, amending or withdrawing a personnel data-processing scheme observed
  9. Probable Inview (legal database reproducing WOR text) — Employer personnel-monitoring facility — Works council consent required before introducing personnel-monitoring facilities (attendance, behaviour, performance) observed
  10. Probable ECER (Ministerie van Buitenlandse Zaken) — Wet bewaarplicht telecommunicatiegegevens — Disapplied by the Hague District Court on 11 March 2015 following CJEU invalidation of the Data Retention Directive observed

#

Cookie and direct-marketing rules are well documented; dark-pattern, opt-out-signal, clean-room and cross-context-advertising sub-modules lack NL-specific findings.

Primary frameworkTelecommunicatiewet (ePrivacy transposition); GDPR
Traffic-light rationale — AmberCookie and direct-marketing rules are well documented; dark-pattern, opt-out-signal, clean-room and cross-context-advertising sub-modules lack NL-specific findings.

Sub-modules (6)

Cookies and trackersGreen

Prior informed consent is required before storing or accessing information on a user's device, applying technology-neutrally to any tracking technology, not solely cookies.

Claims (5):

  • The confidentiality-of-terminal-equipment rule transposed into Dutch law from the ePrivacy Directive is technology-neutral, meaning user consent (or an applicable exception) is required not only for cookies but for any tracking technology accessing or storing information on a device.
  • Autoriteit Persoonsgegevens (AP) — Pre-consent tracking and cookie compliance as 2026 enforcement priority
  • Autoriteit Persoonsgegevens (AP) — Transparency (GDPR Arts 12-14), pre-consent tracking and cookie compliance as its three enforcement priority pillars for 2026.
  • Telecommunicatiewet — Clear/full information and prior consent before placing or reading cookies/similar technologies
  • Telecommunicatiewet — Cookie walls prohibited for government websites; not automatically barred for commercial operators but consent must remain freely given

Dark patternsRed

No NL-specific dark-pattern prohibition distinct from EU-level DSA/GDPR interplay guidelines was surfaced.

Claims (1):

  • Dark patterns — No stand-alone statutory ban; ACM treats a subset as misleading commercial practices under Civil Code; some techniques on the blacklist are per se prohibited

Opt out signalsRed

No NL-specific recognition of browser-level opt-out signals (e.g., Global Privacy Control) was identified.

Clean rooms and dcrRed

No NL-specific data clean-room regulatory framework was identified.

Cross context advertisingAmber

No NL-specific 'sale'/'share' construct analogous to US state law exists; cross-context advertising is governed by GDPR consent/legitimate-interest analysis and the ePrivacy cookie rule.

Claims (1):

  • IAB Europe TCF — Belgian DPA found IAB Europe acts as (joint) data controller of the TC String and consent/objection signals; Dutch AP acknowledged this finding publicly

Direct marketingGreen

Telemarketing to natural persons requires opt-in consent since 1 July 2021; the do-not-call register was discontinued.

Claims (4):

  • Prior to a 1 July 2021 amendment to the Telecommunications Act, telemarketing calls to natural persons operated on an opt-out basis; this was replaced with an opt-in consent requirement and the do-not-call register is no longer used.
  • Telecommunicatiewet — As of 1 July 2026, businesses may no longer call consumers for telemarketing purposes without consent, even where the consumer is or has been a customer; limited to telephone calls, does not remove the separate email/SMS existing-customer soft opt-in under art. 11.7(4).
  • Telecommunicatiewet — Unsolicited automated calling/fax/electronic marketing messages without prior consent ('spam ban')
  • Bel-me-niet Register (BMNR) — Telemarketing to numbers registered in the national do-not-call register
Category narrative 64 words

The Telecommunicatiewet's cookie-consent rule requires prior, informed consent before storing or accessing information on a user's terminal equipment, applying technology-neutrally to all tracking technologies, not only cookies. Since 1 July 2021, telemarketing to natural persons requires opt-in consent, replacing the prior opt-out/do-not-call regime. NL-specific findings on dark patterns, opt-out signals, clean rooms, and cross-context advertising were not surfaced beyond general EU-level DSA/GDPR interplay guidance.

Periodic update · new data 2026-11-04

Since 1 July 2026, businesses may no longer call consumers for telemarketing purposes without consent under the amended Telecommunicatiewet, even where the consumer is, or has been, a customer of that business. This closes the telephone-channel soft opt-in that previously permitted calls to existing customers without separate consent. The amendment is limited in scope: it applies to telephone calls only and does not alter the separate existing-customer soft opt-in for email and SMS marketing preserved under article 11.7(4) of the Telecommunicatiewet. The amendment also carves out charities, lotteries that donate proceeds to charity, and periodical publishers from the tightened consent requirement.

This is the one confirmed in-force change to the Dutch direct-marketing framework; no cookie-consent-specific or broader adtech development was independently re-verified in this window.

Outlook

Businesses that previously relied on the existing-customer telephone soft opt-in will need to have obtained affirmative consent before any telemarketing call made since 1 July 2026; the practical enforcement pattern around this change, including whether the Autoriteit Persoonsgegevens or another body brings early test cases, is the item to watch.

1 earlier distinct update
Periodic update · new data 2026-10-11

Since 1 July 2026, businesses may no longer call consumers for telemarketing purposes without consent under the amended Telecommunicatiewet, even where the consumer is, or has been, a customer of that business. This closes the telephone-channel soft opt-in that previously permitted calls to existing customers without separate consent. The amendment is limited in scope: it applies to telephone calls only and does not alter the separate existing-customer soft opt-in for email and SMS marketing preserved under article 11.7(4) of the Telecommunicatiewet. The amendment also carves out charities, lotteries that donate proceeds to charity, and periodical publishers from the tightened consent requirement.

This is the one confirmed in-force change to the Dutch direct-marketing framework this cycle; no cookie-consent-specific or broader adtech development was independently re-verified in this window.

Outlook

Businesses that previously relied on the existing-customer telephone soft opt-in will need to have obtained affirmative consent before any telemarketing call made since 1 July 2026; the practical enforcement pattern around this change, including whether the Autoriteit Persoonsgegevens or another body brings early test cases, is the item to watch.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (11)
  1. Confirmed EDPB — The confidentiality-of-terminal-equipment rule transposed into Dutch law from the ePrivacy Directive is technology-neutral, meaning user consent (or an applicable exception) is required not only for cookies but for any tracking technology accessing or storing information on a device. observed
  2. Confirmed DataGuidance — Prior to a 1 July 2021 amendment to the Telecommunications Act, telemarketing calls to natural persons operated on an opt-out basis; this was replaced with an opt-in consent requirement and the do-not-call register is no longer used. observed
  3. Confirmed Business.gov.nl — Telecommunicatiewet — As of 1 July 2026, businesses may no longer call consumers for telemarketing purposes without consent, even where the consumer is or has been a customer; limited to telephone calls, does not remove the separate email/SMS existing-customer soft opt-in under art. 11.7(4). observed
  4. High Officiële Bekendmakingen — Autoriteit Persoonsgegevens (AP) — Pre-consent tracking and cookie compliance as 2026 enforcement priority observed
  5. Possible Recording Law — Autoriteit Persoonsgegevens (AP) — Transparency (GDPR Arts 12-14), pre-consent tracking and cookie compliance as its three enforcement priority pillars for 2026. observed
  6. Probable Tweede Kamer (Kamerstukken) — Telecommunicatiewet — Clear/full information and prior consent before placing or reading cookies/similar technologies observed
  7. Probable Kennisdomein — Telecommunicatiewet — Cookie walls prohibited for government websites; not automatically barred for commercial operators but consent must remain freely given observed
  8. Probable Autoriteit Consument & Markt (OPTA) — Telecommunicatiewet — Unsolicited automated calling/fax/electronic marketing messages without prior consent ('spam ban') observed
  9. Probable Rechtbank Rotterdam — Bel-me-niet Register (BMNR) — Telemarketing to numbers registered in the national do-not-call register observed
  10. Probable Thuiswinkel.org — Dark patterns — No stand-alone statutory ban; ACM treats a subset as misleading commercial practices under Civil Code; some techniques on the blacklist are per se prohibited observed
  11. Probable Lexology (law-firm commentary) — IAB Europe TCF — Belgian DPA found IAB Europe acts as (joint) data controller of the TC String and consent/objection signals; Dutch AP acknowledged this finding publicly observed

#

Biometric and profiling rules are well established under GDPR/UAVG; AI Act competent-authority designation and NL-specific AI risk-assessment interplay is still maturing as of the 2 August 2026 application date.

Primary frameworkGDPR Article 22; UAVG Article 29; EU AI Act (Regulation (EU) 2024/1689); Law Enforcement Directive (2016/680)
Traffic-light rationale — AmberBiometric and profiling rules are well established under GDPR/UAVG; AI Act competent-authority designation and NL-specific AI risk-assessment interplay is still maturing as of the 2 August 2026 application date.

Sub-modules (6)

Profiling restrictionsGreen

Profiling restrictions follow GDPR Article 22 directly; the EDPB has issued an opinion confirming GDPR principles govern personal data use in AI model development and deployment.

Claims (3):

  • The EDPB adopted an opinion on the use of personal data for the development and deployment of AI models, confirming that GDPR principles apply to and support responsible AI governance.
  • Dienst Uitvoering Onderwijs (DUO) — AP found DUO's self-devised risk-profile algorithm for flagging suspected 'uitwonendenbeurs' student-grant misuse indirectly discriminated against students with a migration background, lacking scientific justification
  • Artificial Intelligence Act (Regulation (EU) 2024/1689) — AI Act in force 2024-08-01; Art 5 prohibitions apply 2025-02-02; GPAI obligations apply 2025-08-02; general application 2026-08-02

Automated decision making transparencyGreen

ADM transparency follows GDPR Articles 13-15/22 directly; no NL-specific derogation identified.

Claims (4):

  • Autoriteit Persoonsgegevens (AP) — Uber €824,990,000 on 21 August 2026 for deactivating driver accounts via automated fraud/rating-scoring systems, between 2018 and 2022, with no human review before deactivation, applying GDPR Article 22's restriction on solely-automated decisions with significant effects.
  • The AP fined Uber EUR824,990,000 on 21 August 2026 for operating automated systems that deactivated driver accounts without human review, breaching the GDPR's prohibition on solely automated decisions with significant effects.
  • Autoriteit Persoonsgegevens consultation on automated-decision-making explanations — AP opened a consultation on explanations for automated decision-making, published 2026-04-21, input requested by 2026-05-26
  • UAVG — National exception to GDPR Art 22(1) prohibition permits automated decision-making where human intervention adds no value, subject to appropriate safeguards

AI risk assessmentsAmber

The EU AI Act applies from 2 August 2026, with governance, sanctions, and GPAI-provider obligations already in force since August 2025 and AI-literacy obligations since February 2025; national competent authority designation interacts with the AP's data-protection remit.

Claims (5):

  • The EU AI Act applies from 2 August 2026, with certain provisions (prohibitions, definitions, AI-literacy obligations) already effective since 2 February 2025 and governance-structure, sanctions, and GPAI-provider rules effective since 2 August 2025.
  • AP directie Toezicht en Coördinatie AI/Algoritmes (TCA) — New internal AP directorate TCA, succeeding DCA, began operation 8 October 2026 to prepare for prospective AI Act market-surveillance role
  • Uitvoeringswet AI-verordening (Uvai) — Draft Uvai, published for consultation 20 April 2026 (closed 1 June 2026), designates AP and RDI as joint coordinators of a decentralised, sector-based AI Act market-surveillance model; anticipated entry into force 2 August 2027.
  • AP advies geautomatiseerde besluitvorming — Automated risk-selection tools do not in themselves qualify as 'automated decision-making' under art 22 where used only to assess whether further action is needed; Art 22 compliance assessed within the DPIA
  • Autoriteit Persoonsgegevens — AP is the proposed (not yet formally designated) market-surveillance and coordinating authority for the EU AI Act, pending Dutch implementing act

Biometric regimeGreen

Biometric data processing for unique identification is prohibited absent strict necessity for authentication/security, per UAVG Article 29; the AP's DPIA list separately mandates DPIAs for large-scale biometric identification and flexible camera surveillance.

Claims (4):

  • UAVG Article 29 permits processing of biometric data for unique identification purposes only where strictly necessary for authentication or security, subject to additional conditions in Dutch implementing law.
  • The AP's DPIA list identifies large-scale and/or systematic use of flexible camera surveillance (e.g., body-worn cameras, dash cams) and large-scale processing enabling unique identification of individuals as mandatory-DPIA processing categories.
  • UAVG — GDPR Art 9 biometric prohibition does not apply where processing biometric data for unique identification is necessary for authentication or security purposes
  • AP Juridisch kader gezichtsherkenning — Facial recognition is prohibited in most cases, with narrow exceptions; special-category ban also applies to confirm-identity use

Genetic dataAmber

Genetic data is a GDPR Article 9 special category; no NL-specific overlay beyond UAVG's general special-category exceptions was surfaced.

State surveillance carveoutsAmber

Law-enforcement and state-security processing is carved out of GDPR and governed instead by the Law Enforcement Directive (2016/680), implemented in Dutch law via police-data legislation and royal decrees.

Claims (1):

  • Processing of personal data by competent authorities for the prevention, investigation, detection or prosecution of criminal offences is subject to the Law Enforcement Directive (2016/680) rather than the GDPR, and has been implemented in Dutch law and royal decrees governing investigation and prosecuting authorities.
Category narrative 101 words

Profiling and automated-decision-making are governed by GDPR Article 22, with EDPB opinion clarifying GDPR principles' application to AI model development/deployment. The EU AI Act (Regulation (EU) 2024/1689) applies from 2 August 2026 (with earlier partial application from February and August 2025), requiring Member State designation of competent authorities, some of which may coordinate with the AP on data-protection-adjacent obligations. Biometric data is restricted under UAVG Article 29 to strict-necessity authentication/security use, and the AP's DPIA list mandates impact assessments for large-scale biometric identification and flexible camera surveillance. Law-enforcement processing sits under the separate Law Enforcement Directive (2016/680) regime rather than GDPR/UAVG.

Periodic update · new data 2026-10-11

The Autoriteit Persoonsgegevens fined Uber EUR824,990,000 on 21 August 2026 for breaching Article 22 of the GDPR, which prohibits decisions based solely on automated processing that produce a significant effect on the data subject, absent a lawful basis and adequate safeguards. The breach arose from Uber's automated deactivation of driver accounts between 2018 and 2022 without what the AP found to be meaningful human review, compounded by inadequate information given to affected drivers about the basis for deactivation. This is the AP's fourth fine against Uber and the second-largest GDPR fine issued anywhere in the EU, behind only Meta's EUR1.2 billion penalty. Uber has announced it will appeal the decision.

Separately, and at an earlier stage of development, the Dutch government published a draft Uitvoeringswet AI-verordening (Uvai) for consultation on 20 April 2026, with the consultation period closing 1 June 2026. The draft designates the Autoriteit Persoonsgegevens and the Rijksinspectie Digitale Infrastructuur as joint coordinators of a decentralised, sector-based market-surveillance model for AI Act supervision in the Netherlands, with anticipated entry into force on 2 August 2027. The Netherlands had missed the EU's own August 2025 deadline for designating AI Act supervisory authorities, so this draft represents a belated structural response rather than an early-adopter position.

Outlook

Whether the Uber appeal proceeds, and on what grounds, will test the durability of the AP's Article 22 theory of automated decision-making without meaningful human review. Separately, whether the draft Uvai has progressed from the closed consultation toward formal introduction before the Tweede Kamer since 1 June 2026 has not been independently verified and remains open, as does the draft's anticipated 2 August 2027 entry-into-force date.

1 earlier distinct update
Periodic update · new data 2026-09-28

The AP is reported to have fined Uber EUR824,990,000 on 21 August 2026 for operating automated systems that deactivated driver accounts without human review, a decision reported to breach the GDPR's Article 22 prohibition on solely automated decision-making that produces significant effects on individuals. This fine is described as the second-largest GDPR fine on record, reflecting the scale of exposure the AP is prepared to impose for automated-decision-making violations affecting a large population of gig-economy workers.

The scale of this fine signals that the AP treats unlawful automated decision-making, specifically decisions taken without meaningful human review that carry significant consequences for affected individuals such as loss of livelihood through account deactivation, as among the most serious categories of GDPR violation it currently enforces. The AP has separately been reported to enforce EU AI Act prohibited-practices provisions since February 2025, indicating an emerging institutional focus on algorithmic-system oversight that extends beyond GDPR Article 22 into the newer AI-specific regulatory framework.

Outlook

Whether Uber challenges the AP's decision, and how any appeal addresses the automated-decision-making findings, is the clearest item to watch. More broadly, the AP's parallel enforcement role under both GDPR Article 22 and the AI Act's prohibited-practices provisions positions it as an increasingly significant algorithmic-governance enforcer, worth monitoring as its supervisory focus areas for 2026 become clearer.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (17)
  1. Confirmed EDPB — The EDPB adopted an opinion on the use of personal data for the development and deployment of AI models, confirming that GDPR principles apply to and support responsible AI governance. observed
  2. Confirmed EUR-Lex — The EU AI Act applies from 2 August 2026, with certain provisions (prohibitions, definitions, AI-literacy obligations) already effective since 2 February 2025 and governance-structure, sanctions, and GPAI-provider rules effective since 2 August 2025. observed
  3. Confirmed AP/EDPB — UAVG Article 29 permits processing of biometric data for unique identification purposes only where strictly necessary for authentication or security, subject to additional conditions in Dutch implementing law. observed
  4. Confirmed AP/EDPB — The AP's DPIA list identifies large-scale and/or systematic use of flexible camera surveillance (e.g., body-worn cameras, dash cams) and large-scale processing enabling unique identification of individuals as mandatory-DPIA processing categories. observed
  5. Confirmed IAPP — Processing of personal data by competent authorities for the prevention, investigation, detection or prosecution of criminal offences is subject to the Law Enforcement Directive (2016/680) rather than the GDPR, and has been implemented in Dutch law and royal decrees governing investigation and prosecuting authorities. observed
  6. Confirmed Autoriteit Persoonsgegevens — AP directie Toezicht en Coördinatie AI/Algoritmes (TCA) — New internal AP directorate TCA, succeeding DCA, began operation 8 October 2026 to prepare for prospective AI Act market-surveillance role observed
  7. Probable Loyens & Loeff — Uitvoeringswet AI-verordening (Uvai) — Draft Uvai, published for consultation 20 April 2026 (closed 1 June 2026), designates AP and RDI as joint coordinators of a decentralised, sector-based AI Act market-surveillance model; anticipated entry into force 2 August 2027. observed
  8. Confirmed https://www.gblock.app/articles/uber-825-million-dutch-dpa-gdpr-fine-2026 — Autoriteit Persoonsgegevens (AP) — Uber €824,990,000 on 21 August 2026 for deactivating driver accounts via automated fraud/rating-scoring systems, between 2018 and 2022, with no human review before deactivation, applying GDPR Article 22's restriction on solely-automated decisions with significant effects.
  9. Probable VNG — The AP fined Uber EUR824,990,000 on 21 August 2026 for operating automated systems that deactivated driver accounts without human review, breaching the GDPR's prohibition on solely automated decisions with significant effects. observed
  10. Probable Computable — Dienst Uitvoering Onderwijs (DUO) — AP found DUO's self-devised risk-profile algorithm for flagging suspected 'uitwonendenbeurs' student-grant misuse indirectly discriminated against students with a migration background, lacking scientific justification observed
  11. Confirmed Autoriteit Persoonsgegevens — Autoriteit Persoonsgegevens consultation on automated-decision-making explanations — AP opened a consultation on explanations for automated decision-making, published 2026-04-21, input requested by 2026-05-26 observed
  12. Probable Official Journal of the European Union / EUR-Lex — Artificial Intelligence Act (Regulation (EU) 2024/1689) — AI Act in force 2024-08-01; Art 5 prohibitions apply 2025-02-02; GPAI obligations apply 2025-08-02; general application 2026-08-02 observed
  13. Confirmed Rijksoverheid (Algoritmekader) — UAVG — National exception to GDPR Art 22(1) prohibition permits automated decision-making where human intervention adds no value, subject to appropriate safeguards observed
  14. Probable Autoriteit Persoonsgegevens — AP advies geautomatiseerde besluitvorming — Automated risk-selection tools do not in themselves qualify as 'automated decision-making' under art 22 where used only to assess whether further action is needed; Art 22 compliance assessed within the DPIA observed
  15. Probable Autoriteit Persoonsgegevens — Autoriteit Persoonsgegevens — AP is the proposed (not yet formally designated) market-surveillance and coordinating authority for the EU AI Act, pending Dutch implementing act observed
  16. Probable Salaris Vanmorgen — UAVG — GDPR Art 9 biometric prohibition does not apply where processing biometric data for unique identification is necessary for authentication or security purposes observed
  17. Confirmed Autoriteit Persoonsgegevens — AP Juridisch kader gezichtsherkenning — Facial recognition is prohibited in most cases, with narrow exceptions; special-category ban also applies to confirm-identity use observed

#

Age-of-consent and parental-consent framework is clear and GDPR-aligned; a minor pending legislative refinement does not affect current binding status.

Primary frameworkGDPR Article 8; UAVG Article 5
Traffic-light rationale — GreenAge-of-consent and parental-consent framework is clear and GDPR-aligned; a minor pending legislative refinement does not affect current binding status.

Sub-modules (5)

Age verificationGreen

Controllers must make reasonable efforts, given available technology, to verify that parental/guardian consent has been given for children under 16.

Claims (2):

  • Data controllers must take reasonable efforts, using available technology, to verify that a person consenting on behalf of a child under the applicable age threshold actually holds parental responsibility.
  • UAVG Art 5 — Age 16 retained as the consent age for information-society services offered directly to a child

Minor profiling bansAmber

No NL-specific blanket ban on profiling of minors distinct from GDPR Article 22/Recital 71 general caution was identified.

Claims (2):

  • GDPR Art 22(3) — Automated decision-making may never be applied to children under 16
  • Digital Services Act — Platform providers must not present profiling-based ads using personal data of a recipient known with reasonable certainty to be a minor

Education settingsAmber

UAVG special-category exceptions extend to schools processing pupil data for defined educational purposes; no separate education-specific DP statute was identified.

Claims (1):

  • UAVG Chapter 3 exceptions extending to schools permit processing of certain special-category pupil data for defined educational purposes, alongside similar exceptions for hospitals and insurers.

Dependent adultsGreen

UAVG Article 5 requires the consent of a legal representative instead of the data subject where the data subject is under guardianship or subject to an administration or protection order and lacks legal capacity to consent.

Claims (1):

  • Under UAVG Article 5(2), if a data subject is under guardianship or subject to an administration or protection order, the consent of the legal representative is required instead of the data subject's own consent, to the extent the data subject lacks legal capacity.
Category narrative 71 words

The Netherlands applies the GDPR default age of 16 for information-society-service consent (Article 8), requiring verifiable parental/guardian consent below that age, with controllers expected to make reasonable efforts to verify parental authority given available technology. UAVG Article 5 extends analogous legal-representative consent requirements to adults under guardianship or subject to an administration/protection order. A pending Dutch bill (Data Protection Collective Act) would adjust children's-data consent provisions but is not yet enacted.

Periodic update · new data 2026-09-28

A proposed amendment to the UAVG, reported to be in consultation as of 2026, would allow children aged 12 and above to make independent data-subject requests under Dutch data protection law. This proposal is not yet enacted, and reports suggest it remains at consultation stage without a confirmed timeline for entry into force.

If adopted, this would represent a structural shift in how Dutch law treats the data-protection agency of minors, granting a defined age cohort, 12 and above, the standing to exercise data-subject rights independently rather than through a parent or guardian. This is a notable departure from data-protection frameworks that set the age of independent digital consent higher, and its progress is worth tracking distinctly from the general data-subject-rights item given its specific focus on the vulnerable-groups dimension of Dutch law.

Outlook

The UAVG amendment's consultation status means no confirmed effective date exists yet for the children's independent-request provision. Its progression toward enactment is the key marker to watch for this module, alongside any further detail on how the narrowed criminal-personal-data definition referenced in the same proposal would apply to minors specifically.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (9)
  1. Confirmed EUR-Lex — Data controllers must take reasonable efforts, using available technology, to verify that a person consenting on behalf of a child under the applicable age threshold actually holds parental responsibility. observed
  2. Confirmed IAPP — Children aged 16 and above may give their own consent for information-society-service processing in the Netherlands; for children below 16, consent must be obtained from the child's legal guardian or parent, consistent with the GDPR Article 8 default and reiterated in the UAVG. observed
  3. Probable IAPP — UAVG Chapter 3 exceptions extending to schools permit processing of certain special-category pupil data for defined educational purposes, alongside similar exceptions for hospitals and insurers. observed
  4. Confirmed DataGuidance — Under UAVG Article 5(2), if a data subject is under guardianship or subject to an administration or protection order, the consent of the legal representative is required instead of the data subject's own consent, to the extent the data subject lacks legal capacity. observed
  5. Probable ICTRecht — Verzamelwet gegevensbescherming — UAVG Arts 5, 22, 23, 23a, 30a, 30b, 41 and ten other Dutch statutes observed
  6. Uncertain Recording Law — UAVG (proposed amendment) — A UAVG amendment proposal in consultation as of 2026 would allow children aged 12 and above to make independent data-subject requests. observed
  7. Probable Schenkeveld Advocaten — GDPR Art 22(3) — Automated decision-making may never be applied to children under 16 observed
  8. Probable Tweede Kamer (Kamerstukken) — UAVG Art 5 — Age 16 retained as the consent age for information-society services offered directly to a child observed
  9. Probable Streamlex — Digital Services Act — Platform providers must not present profiling-based ads using personal data of a recipient known with reasonable certainty to be a minor observed

#

Mature, actively used enforcement toolkit with a published fining structure and recent illustrative decisions; collective-redress mechanism is narrower than the GDPR default option.

Primary frameworkGDPR Articles 58, 77-84; UAVG
Traffic-light rationale — GreenMature, actively used enforcement toolkit with a published fining structure and recent illustrative decisions; collective-redress mechanism is narrower than the GDPR default option.

Sub-modules (6)

Regulator powers and penaltiesGreen

The AP published a four-category fining structure with monetary ranges from €0 up to €1,000,000 per infringement category, escalating for category-four offences deemed inadequate.

Claims (6):

  • The AP created a four-tiered penalty structure for GDPR infringements ranging from €0-200,000 (category one) up to €450,000-1,000,000 (category four), with higher fines available where a category-four penalty is deemed inappropriate.
  • AP fined Uber EUR824,990,000 on 21 August 2026 for breaching GDPR Art 22's prohibition on solely-automated decisions with significant effect, via automated driver-account deactivation (2018-2022) without meaningful human review, and for inadequate information to drivers.
  • Autoriteit Persoonsgegevens (AP) — The AP may impose fines of up to EUR20 million or 4% of global annual turnover, whichever is higher.
  • Autoriteit Persoonsgegevens (AP) — When calculating fines for companies, the AP took into account the turnover of the (Yandex) parent company, consistent with EDPB fine-calculation guidelines.
  • AVG / UAVG — Administrative fines up to EUR 10M or 2% worldwide turnover (admin. breaches) and up to EUR 20M or 4% (core principles, rights, transfers)
  • Boetebeleidsregels AP 2023 — AP sorts violations into fine categories I/II/III and moves base amount up or down within bandwidth depending on aggravating/mitigating factors

Enforcement activity indexGreen

Illustrative recent enforcement includes the €525,000 DPG Media Magazines fine and the CP&A employee-health-data security fine.

Claims (7):

  • The AP imposed a €525,000 fine on DPG Media Magazines B.V. for infringing GDPR Article 12(2) by unnecessarily requiring copies of identity documents from individuals exercising access and erasure rights.
  • The AP fined employer CP&A for GDPR violations relating to insecure online processing of employees' sick-leave (health) data lacking multi-factor authentication.
  • Belastingdienst (Dutch Tax Administration) — AP fined Belastingdienst EUR 3,700,000 for using a self-learning algorithm to build the FSV blacklist on over 270,000 people, often without a lawful basis or accuracy safeguards
  • Belastingdienst (Minister of Finance) — AP fined Belastingdienst EUR 2,750,000 for unlawfully and discriminatorily processing dual-nationality data of childcare-benefit applicants during the 'toeslagenaffaire', part of an algorithm-driven selection process
  • Uber B.V. / Uber Technologies Inc. — AP fined Uber EUR 290,000,000 for transferring European drivers' personal data to the US for over two years without an adequate transfer mechanism after Schrems II
  • AP fined HAN University of Applied Sciences EUR 175,000 for insufficient security of personal data processing
  • Autoriteit Persoonsgegevens — Fines for tracking cookies placed without valid consent, including via pre-ticked boxes; example fines against Coolblue and AS Watson/Kruidvat

Regulator funding and capacityAmber

No specific NL AP budget/headcount figures were surfaced in this run; the AP operates as an independent non-departmental public body under UAVG Article 11 budgeting provisions.

Claims (2):

  • UAVG Article 11 requires the AP, as an independent non-departmental public body, to draw up its own draft budget subject to the Dutch non-departmental public bodies framework act.
  • Autoriteit Persoonsgegevens — In 2025 the AP imposed only four fines (down from six in 2024), issued nine reprimands (up from seven) and used a new simplified settlement procedure three times, favouring warnings, research and advice over fines

Collective redress and class actionsAmber

The Netherlands declined to adopt the GDPR Article 80(2) opt-out mechanism, instead requiring all affected data subjects to individually opt in for their data to be submitted as evidence in a collective action.

Claims (3):

  • The Dutch GDPR Implementation Bill specifically prohibits collective actions proceeding against a data subject's will, requiring all data subjects whose data forms part of a contested processing operation to individually sign up for a collective action, meaning the Netherlands did not adopt the Article 80(2) GDPR opt-out mechanism.
  • Latombe v Commission (T-553/23) / EDPS v SRB (C-413/23 P) — Latombe appealed the DPF ruling to the CJEU on 2025-10-31 (Case C-703/25 P)
  • WAMCA / GDPR Art 82 — Collective damages claims for GDPR infringements permitted via WAMCA regime (art 3:305a BW)

Private right of actionGreen

Data subjects retain the GDPR Article 78/79 right to an effective judicial remedy against both supervisory-authority decisions and controllers/processors directly before Dutch courts.

Claims (4):

  • The CJEU's judgment in Case C-245/20 (Autoriteit Persoonsgegevens), arising from a Dutch court reference, addressed the scope of AP supervisory competence under Article 55(3) GDPR over data processing by courts acting in their judicial capacity.
  • Awb objection/appeal procedure — 6-week objection window against AP decisions, 6-week AP decision deadline (extendable by 6 weeks), 6-week appeal window to district court
  • CJEU C-300/21 follow-on practice — No formal 'threshold of seriousness' required to found a claim for non-material damage under GDPR art 82; seriousness may affect ease of proving damage occurred
  • UWV data breach case — Amsterdam kantonrechter ordered UWV to pay EUR 250 non-material damages after unlawfully disclosing an employee's prior sickness to new employer; understood to be the Netherlands' first AVG damages award

Recent developments 180dGreen

Within the relevant window, the CJEU's Grand Chamber ruling of 10 February 2026 in WhatsApp Ireland v EDPB (C-97/23 P) addressed judicial review of EDPB binding Article 65 decisions arising from one-stop-shop disputes, relevant to Dutch controllers subject to lead-authority decisions; the EDPB also adopted a statement on DPAs' role in the AI Act framework (17 July 2026).

Claims (3):

  • The CJEU Grand Chamber issued its ruling of 10 February 2026 in WhatsApp Ireland Ltd v European Data Protection Board (Case C-97/23 P), concerning the reviewability under Article 263 TFEU of binding EDPB Article 65 dispute-resolution decisions arising from the one-stop-shop mechanism used against the Irish lead authority's draft WhatsApp decision.
  • The EDPB, of which the AP is a member, adopted a statement on 17 July 2026 concerning data protection authorities' role in the EU AI Act framework, relevant to AP's interaction with AI Act competent authorities in the Netherlands.
  • Verzamelwet gegevensbescherming (new Art 21b) — From 1 September 2026, a new Article 21b obliges the AP to publish, by name, any sanction it imposes, converting prior discretionary practice into a statutory duty.
Category narrative 125 words

The AP exercises the full GDPR Article 58 investigative and corrective toolkit and has published a four-tier fining structure ranging up to €1,000,000 per category (with higher fines possible where deemed appropriate). Enforcement examples include the €525,000 DPG Media Magazines fine (Article 12(2) transparency) and the CP&A fine for insecure health-data processing. NL notably declined to adopt the GDPR Article 80(2) opt-out collective-action mechanism, requiring data subjects to individually opt in to collective privacy actions. The CJEU's 2022 ruling in Case C-245/20 clarified limits on AP jurisdiction over courts acting in their judicial capacity, and the Court's 2026 WhatsApp v EDPB ruling (C-97/23 P) addressed challengeability of EDPB binding decisions within the one-stop-shop mechanism, both bearing on Dutch enforcement practice as an EU Member State.

Periodic update · new data 2026-10-11

The Autoriteit Persoonsgegevens imposed a fine of EUR824,990,000 on Uber on 21 August 2026 for breaching Article 22 of the GDPR through automated, insufficiently human-reviewed driver-account deactivations between 2018 and 2022, combined with inadequate information provided to affected drivers. This is the AP's fourth fine against Uber and the second-largest GDPR fine issued anywhere in the EU to date, exceeded only by Meta's EUR1.2 billion penalty. Uber has publicly announced its intention to appeal.

This record-scale sanction arrives alongside a structural change to how AP enforcement outcomes reach the public. Article 21b of the Uitvoeringswet AVG, introduced by the Verzamelwet gegevensbescherming and in force since 1 September 2026, makes publication the default position for AP enforcement decisions, including orders, fines and settlements, publishable no earlier than two weeks after the decision absent an exception. Taken together, the Uber fine and the new publication default mean that both the scale and the visibility of AP enforcement action have increased within the same period, raising the practical consequence of any future AP sanction for a regulated entity.

Outlook

The Uber appeal is the primary near-term item to watch, both for its outcome and for what it may reveal about the durability of the AP's Article 22 automated-decision-making theory. The first enforcement decisions published under the new article 21b default-publication regime, expected from mid-September 2026 onward, will be the first real test of how the transparency reform operates in practice.

1 earlier distinct update
Periodic update · new data 2026-09-28

The Netherlands' enforcement and redress landscape shifted materially this cycle through two nine-figure AP fines and a new statutory transparency obligation. The AP fined MLU B.V. (Yango) EUR100 million on 8 May 2026 for unlawful cross-border data transfers to Russia, and is reported to have fined Uber EUR824,990,000 on 21 August 2026 for unlawful automated decision-making, together representing a marked escalation in enforcement intensity by the Dutch regulator. The AP's standing statutory fine ceiling remains EUR20 million or 4% of global annual turnover, whichever is higher; both fines this cycle were calculated with reference to parent-company turnover consistent with EDPB fine-calculation guidance, explaining how figures well above the nominal EUR20 million ceiling were reached.

Separately, from 1 September 2026, a new Article 21b under the Verzamelwet gegevensbescherming obliges the AP to publish, by name, any sanction it imposes. This converts what had previously been discretionary publication practice into a statutory duty, meaning the AP's enforcement record will become systematically more visible and consistently published going forward, rather than subject to case-by-case publication decisions.

Outlook

The combination of two nine-figure fines and a new mandatory publication duty marks the Netherlands as an increasingly assertive enforcement jurisdiction within the GDPR framework. Whether the Yango and Uber fines are appealed, and how the new Article 21b publication duty is applied in practice from 1 September 2026 onward, are the clearest markers to track for this module going forward.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (25)
  1. Confirmed IAPP — The AP created a four-tiered penalty structure for GDPR infringements ranging from €0-200,000 (category one) up to €450,000-1,000,000 (category four), with higher fines available where a category-four penalty is deemed inappropriate. observed
  2. Confirmed AP/EDPB — The AP imposed a €525,000 fine on DPG Media Magazines B.V. for infringing GDPR Article 12(2) by unnecessarily requiring copies of identity documents from individuals exercising access and erasure rights. observed
  3. Confirmed AP/EDPB — The AP fined employer CP&A for GDPR violations relating to insecure online processing of employees' sick-leave (health) data lacking multi-factor authentication. observed
  4. Probable DataGuidance — UAVG Article 11 requires the AP, as an independent non-departmental public body, to draw up its own draft budget subject to the Dutch non-departmental public bodies framework act. observed
  5. Confirmed IAPP — The Dutch GDPR Implementation Bill specifically prohibits collective actions proceeding against a data subject's will, requiring all data subjects whose data forms part of a contested processing operation to individually sign up for a collective action, meaning the Netherlands did not adopt the Article 80(2) GDPR opt-out mechanism. observed
  6. Confirmed EUR-Lex — The CJEU's judgment in Case C-245/20 (Autoriteit Persoonsgegevens), arising from a Dutch court reference, addressed the scope of AP supervisory competence under Article 55(3) GDPR over data processing by courts acting in their judicial capacity. observed
  7. Confirmed EUR-Lex — The CJEU Grand Chamber issued its ruling of 10 February 2026 in WhatsApp Ireland Ltd v European Data Protection Board (Case C-97/23 P), concerning the reviewability under Article 263 TFEU of binding EDPB Article 65 dispute-resolution decisions arising from the one-stop-shop mechanism used against the Irish lead authority's draft WhatsApp decision. observed
  8. Confirmed EDPB — The EDPB, of which the AP is a member, adopted a statement on 17 July 2026 concerning data protection authorities' role in the EU AI Act framework, relevant to AP's interaction with AI Act competent authorities in the Netherlands. observed
  9. Probable Computable.nl — AP fined Uber EUR824,990,000 on 21 August 2026 for breaching GDPR Art 22's prohibition on solely-automated decisions with significant effect, via automated driver-account deactivation (2018-2022) without meaningful human review, and for inadequate information to drivers. observed
  10. Probable VNG — Autoriteit Persoonsgegevens (AP) — The AP may impose fines of up to EUR20 million or 4% of global annual turnover, whichever is higher. observed
  11. Confirmed Binnenlands Bestuur — Autoriteit Persoonsgegevens (AP) — When calculating fines for companies, the AP took into account the turnover of the (Yandex) parent company, consistent with EDPB fine-calculation guidelines. observed
  12. Probable Stibbe — Verzamelwet gegevensbescherming (new Art 21b) — From 1 September 2026, a new Article 21b obliges the AP to publish, by name, any sanction it imposes, converting prior discretionary practice into a statutory duty. observed
  13. Probable Commercial Risk — Belastingdienst (Dutch Tax Administration) — AP fined Belastingdienst EUR 3,700,000 for using a self-learning algorithm to build the FSV blacklist on over 270,000 people, often without a lawful basis or accuracy safeguards observed
  14. Probable BNNVARA / Joop — Belastingdienst (Minister of Finance) — AP fined Belastingdienst EUR 2,750,000 for unlawfully and discriminatorily processing dual-nationality data of childcare-benefit applicants during the 'toeslagenaffaire', part of an algorithm-driven selection process observed
  15. Confirmed Autoriteit Persoonsgegevens — Uber B.V. / Uber Technologies Inc. — AP fined Uber EUR 290,000,000 for transferring European drivers' personal data to the US for over two years without an adequate transfer mechanism after Schrems II observed
  16. Confirmed Autoriteit Persoonsgegevens — AP fined HAN University of Applied Sciences EUR 175,000 for insufficient security of personal data processing observed
  17. Probable Binnenlands Bestuur — Autoriteit Persoonsgegevens — In 2025 the AP imposed only four fines (down from six in 2024), issued nine reprimands (up from seven) and used a new simplified settlement procedure three times, favouring warnings, research and advice over fines observed
  18. Probable European Data Protection Law Review (Lexxion) — Latombe v Commission (T-553/23) / EDPS v SRB (C-413/23 P) — Latombe appealed the DPF ruling to the CJEU on 2025-10-31 (Case C-703/25 P) observed
  19. Probable Cookieconfirm — Autoriteit Persoonsgegevens — Fines for tracking cookies placed without valid consent, including via pre-ticked boxes; example fines against Coolblue and AS Watson/Kruidvat observed
  20. Confirmed Autoriteit Persoonsgegevens — AVG / UAVG — Administrative fines up to EUR 10M or 2% worldwide turnover (admin. breaches) and up to EUR 20M or 4% (core principles, rights, transfers) observed
  21. Probable Staatscourant — Boetebeleidsregels AP 2023 — AP sorts violations into fine categories I/II/III and moves base amount up or down within bandwidth depending on aggravating/mitigating factors observed
  22. Probable Autoriteit Persoonsgegevens — Awb objection/appeal procedure — 6-week objection window against AP decisions, 6-week AP decision deadline (extendable by 6 weeks), 6-week appeal window to district court observed
  23. Probable Rechtspraak.nl (Parket bij de Hoge Raad) — WAMCA / GDPR Art 82 — Collective damages claims for GDPR infringements permitted via WAMCA regime (art 3:305a BW) observed
  24. Probable WatsonLaw — CJEU C-300/21 follow-on practice — No formal 'threshold of seriousness' required to found a claim for non-material damage under GDPR art 82; seriousness may affect ease of proving damage occurred observed
  25. Probable ICTRecht — UWV data breach case — Amsterdam kantonrechter ordered UWV to pay EUR 250 non-material damages after unlawfully disclosing an employee's prior sickness to new employer; understood to be the Netherlands' first AVG damages award observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 126 claim(s) (126 category placement(s)), 111 source(s) in the cumulative register.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (39 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 8Children & Vulnerable Groupsparental consent
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsdeadlines and response windows
Art. 14Data Subject Rightsdeadlines and response windows
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrectification and erasure
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy granted
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer mechanisms
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressregulator powers and penalties
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties