Personal data breach
A personal data breach, in Dutch practice called a datalek, is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. The GDPR defines it in Article 4(12). A hack is not required: an email sent to the wrong recipient or a lost data carrier can also be a personal data breach.
Source: Regulation (EU) 2016/679 (GDPR) Article 4(12) and Articles 33, 34 and 83; Dutch GDPR Implementation Act (Uitvoeringswet AVG) Article 6; EDPB, Guidelines 9/2022 on personal data breach notification (version 2.0, 2023); Dutch Cybersecurity Act (Cyberbeveiligingswet) Articles 26 and 27; Delegated Regulation (EU) 2025/301 Article 5
The controller notifies a personal data breach without undue delay and, where feasible, not later than 72 hours after becoming aware of it to the supervisory authority, in the Netherlands the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP), unless the breach is unlikely to result in a risk to the rights and freedoms of individuals (Article 33(1)). If 72 hours is not met, the organisation gives reasons for the delay. A processor informs the controller without undue delay. Where a high risk is likely, the organisation also informs the data subjects, unless, for example, the data was encrypted (Article 34). Every breach is documented, even if it need not be notified (Article 33(5)).
For the management board and the audit committee, a personal data breach is often one of several reporting obligations triggered by the same incident. A cyber attack can at the same time be a significant incident under the Dutch Cybersecurity Act (Cyberbeveiligingswet), with an early warning within 24 hours, or a major ICT-related incident under DORA, with an initial notification within four hours of classification and no later than 24 hours after becoming aware, each with its own channel. The digital omnibus proposal of November 2025 would limit notification to the supervisory authority to breaches likely to result in a high risk, extend the deadline to 96 hours and introduce a single European reporting point; in October 2026 the proposal had not yet been adopted.
Failure to notify, or late notification, can lead to a fine of up to EUR 10 million or 2 per cent of worldwide annual turnover (Article 83(4) of Regulation (EU) 2016/679). A personal data breach always concerns personal data: a security incident involving only business data is not a breach within the meaning of the GDPR, although it may fall under other reporting obligations. Guidance and examples are set out in Guidelines 9/2022 of the European Data Protection Board (EDPB).
Last updated: · Editor: ONE Risk Advisory
Frequently asked questions
Must every personal data breach be notified to the Dutch Data Protection Authority?
No. Notification is mandatory unless the breach is unlikely to result in a risk to the rights and freedoms of individuals (Article 33(1) GDPR). The controller makes and records that judgement itself. Every breach must, however, be documented internally, with the facts, the effects and the remedial action taken, so that the supervisory authority can verify compliance (Article 33(5)).
When does the 72-hour period start?
When the controller becomes aware of the breach (Article 33(1) GDPR). A processor must inform the controller without undue delay (paragraph 2). If not all information is available at once, it may be provided in phases (paragraph 4); a notification made after 72 hours must be accompanied by reasons for the delay.
Who decides within the organisation on notifying a breach?
The controller, meaning the organisation; the management board determines who decides on its behalf. A playbook sets out who assesses the breach, when the data protection officer is involved, who notifies and who checks whether other reporting obligations apply, such as under the Dutch Cybersecurity Act or DORA. This keeps the different clocks aligned.