GDPR data breach notification: when are you required to report?
Under the GDPR, some data incidents must be reported to your data protection authority within 72 hours. This decision tree helps you work out quickly whether yours is one of them.

GDPR data breach notification: when are you required to report?
Under the GDPR, some data incidents must be reported to your data protection authority within 72 hours. This decision tree helps you work out quickly whether yours is one of them.
Who this guide is for. This guide is for freelancers, healthcare providers, small organisations, and anyone who may have to decide quickly whether a data incident triggers GDPR notification duties.
Which law this covers. This page describes EU law: the GDPR (Articles 33 and 34), as explained in the European Data Protection Board’s guidelines, with Dutch specifics from the Autoriteit Persoonsgegevens (AP) and the Dutch GDPR Implementation Act (UAVG). It applies to organisations covered by the GDPR in the EU/EEA. Outside the EU/EEA your rules differ (the UK, for example, has its own version of the GDPR); check your own regulator. Checked against the sources as of 8 November 2026. A European Commission proposal (the “Digital Omnibus”, November 2025) would require notifying the authority only for high-risk breaches, within 96 hours; it is not law yet (still in European Parliament committee on 8 November 2026), so the 72-hour rule below applies.
It fits especially:
- people handling personal data in a professional role
- readers who need a practical first decision path after an incident
- organisations without an in-house privacy or compliance team on standby
What you gain, and what it costs
If you use this guide properly, you gain:
- a quicker first assessment of whether an incident is likely reportable
- a better sense of when the 72-hour clock matters
- a more structured response before guesswork turns into delay
What it costs:
- time under pressure
- the discipline to document facts instead of reacting purely on instinct
- accepting that this guide helps you classify the incident, but does not replace legal advice in borderline or high-stakes cases
When this is overkill
If the incident clearly does not involve personal data, you do not need a full GDPR breach-notification analysis.
If the breach is large, regulated, cross-border, or likely to cause serious harm, this guide should be treated as a first pass, not the final word. Then you escalate to legal or specialist advice immediately.
An incident has occurred. Your laptop was stolen, an email was sent to the wrong person, or your system was compromised. Do you need to report it?
The GDPR requires the organisation responsible for the data to report a breach to its supervisory authority unless the breach is unlikely to result in a risk to people, and to tell the affected people as well when the risk is high. The deadline is 72 hours after you become aware of the breach. The question is: when does a breach trigger the notification obligation?
What is a data breach?
The GDPR (Article 4(12)) defines a personal data breach as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. The EDPB and the AP sort breaches into three types: confidentiality (disclosure or access), integrity (alteration) and availability (loss of access or destruction).
Examples that qualify as a data breach:
- Stolen or lost laptop or USB drive containing unencrypted personal data
- Email with medical information sent to the wrong recipient
- An employee without authorisation viewing a medical record
- Ransomware attack that encrypts files (even if no data was exfiltrated: that is still an availability breach)
- Intrusion into a system where customer data was accessed
- Employee accidentally sharing a file publicly
Not a data breach, or usually low risk:
- Incident involving no personal data: not a GDPR breach
- Planned system maintenance that makes data temporarily unavailable: not a breach of security (EDPB)
- File sent internally to the wrong colleague: still a breach, but the AP counts a colleague in your own organisation as a “trusted recipient”, which can lower the risk. Record it.
- Data that was already publicly available: still a breach if security failed; the risk may be lower, but the AP warns that combining leaked data with public data can increase the impact.
The decision tree
Step 1: Does it involve personal data?
No → Not a data breach under GDPR. No notification obligation.
Yes → Continue to step 2.
Step 2: What exactly happened?
| Situation | Classification |
|---|---|
| Data was lost or destroyed | Data breach (availability) |
| Data was altered without authorisation | Data breach (integrity) |
| Data was accessed by unauthorised parties | Data breach (confidentiality) |
| Data was shared with the wrong recipient | Data breach (confidentiality) |
| Data was temporarily unavailable because of an incident (outage, attack, ransomware), even if intact afterwards | Data breach (availability); may or may not need notifying |
| Data was unavailable because of planned maintenance | Not a data breach |
Every breach goes into your internal register (see below), whatever the outcome of the next steps.
Step 3: What is your role in this processing?
Data processor (you process data on behalf of another organisation, the controller):
- Tell the controller without undue delay about every breach involving their data. You do not first assess the risk; that is the controller’s job (EDPB).
- You do not report to the supervisory authority yourself, unless the controller has authorised you in writing to notify on its behalf. Even then the controller stays legally responsible.
- Your part of the tree ends here. Help the controller with the facts it needs.
Data controller (you decide why and how the data is used) → Continue to step 4.
Step 4: What is the risk to the people affected?
The GDPR sets three outcomes, depending on the risk to the rights and freedoms of the people affected. You assess this yourself, looking at both how severe the consequences could be and how likely they are.
1. Unlikely to result in a risk → No notification. Record the breach and your reasoning in the register.
Examples that often fall here, based on the EDPB and AP guidance:
- A lost device or backup that was securely encrypted, with the key not compromised and a recent backup of the data (the AP adds: data intact and still under your control)
- A brief outage after which the data was restored, with no other harm
- Data sent to a trusted recipient (a colleague, a regular business partner, someone bound by professional secrecy) who confirms deletion
2. Likely to result in a risk → Notify the supervisory authority within 72 hours. This is the default: you notify unless you can show that a risk is unlikely.
3. Likely to result in a high risk → Notify the supervisory authority and the affected people (see “Notifying affected individuals”).
Factors that point to a high risk, according to the AP and the EDPB:
- Special categories of data (GDPR Article 9: health, ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, sex life or sexual orientation) and criminal-offence data
- Data that enables identity fraud or financial harm: copies of ID documents, credit card data, national ID numbers combined with other data (in the Netherlands: the BSN with name and address)
- Vulnerable people: children, older people, people with a disability or illness
- Large numbers of people (though a breach can be serious for even one person)
- Unencrypted data in the hands of an unknown or malicious party, such as a thief or attacker
Rule of thumb: When in doubt, notify. Both the EDPB (“err on the side of caution”) and the AP give this advice. A breach is not automatically a GDPR infringement, but failing to notify a breach that should have been notified is one, and the AP can fine for it.
The 72-hour deadline
The clock starts when you become aware of the breach, not when the incident occurred. According to the EDPB and the AP, you are aware once you are reasonably certain that a security incident has compromised personal data. You may take a short time to investigate whether it is a breach, but you must start that investigation immediately. If a breach happened on Monday but you become aware of it on Friday, the 72 hours begin on Friday. A processor’s notice to you normally counts as the moment you become aware.
The notification does not need to be complete at the time of filing: the GDPR allows information in phases. File an initial report within 72 hours and send a follow-up when you know more. If you notify later than 72 hours, you must give reasons for the delay; the AP accepts late notifications only in exceptional cases (a weekend, holiday or illness is not a valid reason).
Where to report: the supervisory authority of the EU/EEA country where you are established. For a breach involving cross-border processing, that is the lead authority where your main establishment is. The EDPB lists every national authority on its members page.
Filing with the AP (the Netherlands)
How the AP describes the process on its own pages (as of 8 November 2026):
- Prepare: the AP publishes the form’s questions in advance as the “Vragenlijst meldformulier datalekken” (also available in English).
- File via the AP’s online Meldformulier datalekken (data breach notification form), linked from the AP’s “This is how you report a data breach” page. The form itself is in Dutch. The AP does not accept notifications by phone, post or email. Your data protection officer is not a reporting channel: involve them, but the organisation files.
- After sending, a receipt with a notification number appears on screen. Save or print it straight away: you cannot view the notification online later.
- Use that number to supplement, change or withdraw the notification through the same form.
- Usually you hear nothing back; if the AP has questions it contacts you within two weeks.
A processor authorised by its client files under the controller’s name and uploads the written authorisation with the notification. Providers of public electronic communications services (under the Dutch Telecommunications Act) also report to the AP, through the same form.
Notifying affected individuals
In addition to reporting to the supervisory authority, you may also be required to notify the individuals whose data was affected.
Mandatory if the breach is likely to result in a high risk to their rights and freedoms (step 4, outcome 3). Special category data or a foreseeable risk of identity fraud are strong signs of high risk, but the test is always the overall risk.
Not required if (GDPR Article 34(3)):
- the data was protected by measures that make it unintelligible to anyone unauthorised, such as encryption, and the key was not compromised
- you have taken measures afterwards that ensure the high risk is no longer likely to materialise
- contacting everyone individually would involve disproportionate effort; then you must instead make a public communication or similar measure that informs people equally effectively
The supervisory authority can also order you to inform the people affected. In the Netherlands, the UAVG adds two exceptions: where necessary for weighty interests such as national or public security (Article 41), and for financial firms under the Dutch Financial Supervision Act (Wft), which must still notify the AP (Article 42).
Notify affected individuals without undue delay. Where the threat is immediate, such as a risk of identity theft, the EDPB says this can even come before the report to the supervisory authority. Tell them in clear and plain language what happened, who they can contact for more information, the likely consequences, and what you are doing about it, including what they can do to protect themselves.
Specific considerations for healthcare providers
Healthcare providers process health data, a special category. That does not change the legal test, but it makes a risk, and often a high risk, more likely:
- Unauthorised access to patient data, including by an employee who is not authorised to see it, is a data breach
- A stolen laptop with patient records: if it cannot be confirmed that the encryption was strong and the key was safe, treat it as unencrypted (the EDPB says not notifying data that was not actually securely encrypted breaches Article 33)
- Email with medical information sent to the wrong address: the AP names leaked medical files as a clear case of risk; if the recipient has already seen the data, the AP says this can already be a high risk
Who files:
- If you work within an organisation: alert your data protection officer (DPO) or privacy contact internally at once. The organisation, as controller, files with the supervisory authority; the DPO cannot receive the notification on the authority’s behalf.
- If you are a sole trader / freelancer, you are usually the controller yourself: file directly with your supervisory authority.
- Consider also contacting your national health-sector CERT or cybersecurity agency for technical support (in the Netherlands: Z-CERT, for healthcare organisations). This does not replace the GDPR notification.
Maintaining an internal register
The GDPR (Article 33(5)) requires you to document every data breach, including breaches you are not required to report to the supervisory authority. The supervisory authority can ask to see this documentation to check that you comply.
What the law requires per incident:
- The facts: what happened, the cause and which personal data
- The effects of the breach
- The remedial action taken
The AP also recommends recording whether you notified the AP and the people affected, and why or why not. It is useful to note when you discovered the incident and when you became aware of the breach as well, since that moment starts the 72 hours.
Next step
Go further
- Data processing agreement explained — clarify controller vs. processor roles and what changes about your obligations
- Backup implementation guide — prevent breaches caused by data loss
- Spyware detection guide — if you suspect a compromised device
Profiles
- Threat profile: healthcare provider — GDPR obligations in healthcare
- Threat profile: small business owner — GDPR for freelancers and SMEs