Free tool · 3 minutes · no registration
Is it a GDPR data breach to notify?
Tell the tool what happened and when you became aware: it says whether the breach must be notified to the supervisory authority, whether the people concerned must be informed, and works out the 72-hour time limit. Nothing you enter leaves your browser.
When a personal data breach must be notified: the short answer
A controller notifies a personal data breach to the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after having become aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons (Art. 33(1) GDPR). If the breach is likely to result in a high risk, the controller also communicates it to the people concerned without undue delay (Art. 34(1)). A processor notifies its controller without undue delay (Art. 33(2)).
What counts as a personal data breach
A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data (Art. 4(12)). In practice three kinds:
- Confidentiality: unauthorised or accidental disclosure of, or access to, personal data.
- Integrity: unauthorised or accidental alteration of personal data.
- Availability: accidental or unlawful loss of access to, or destruction of, personal data.
Who to tell, depending on the risk
| Risk for the people concerned | Supervisory authority | People concerned | Internal record |
|---|---|---|---|
| Unlikely | No notification | No communication | Yes (Art. 33(5)) |
| Risk | Within 72 hours of becoming aware | Not required | Yes |
| High risk | Within 72 hours of becoming aware | Without undue delay, unless an Art. 34(3) exception applies | Yes |
What the notification contains
- The nature of the breach, with the categories and approximate number of people and of records concerned.
- The name and contact details of the data protection officer or other contact point.
- The likely consequences of the breach.
- The measures taken or proposed to address the breach and mitigate its effects.
Where the information is not all available at once, it can be provided in phases without undue further delay (Art. 33(4)). A notification made after 72 hours is accompanied by the reasons for the delay.
When the people concerned need not be informed
- The data affected was protected by measures that make it unintelligible to unauthorised persons, such as encryption (Art. 34(3)(a)).
- The controller has taken subsequent measures that make the high risk no longer likely to materialise (Art. 34(3)(b)).
- Individual communication would involve disproportionate effort: a public communication or similar measure is made instead (Art. 34(3)(c)).
The supervisory authority can still require the communication (Art. 34(4)). Every breach, notified or not, is documented with its facts, effects and remedial action (Art. 33(5)).
Checked against the official texts on 22/11/2026 · reviewed by GoToCertify's Subject Matter Expert. Sources: Regulation (EU) 2016/679, Articles 4(12), 33 and 34; EDPB Guidelines 9/2022 on personal data breach notification. Preliminary orientation, not legal advice.
Frequently asked questions
When does the 72-hour deadline start?
When the controller becomes aware of the breach, that is when it has a reasonable degree of certainty that a security incident has compromised personal data. The 72 hours are calendar hours, weekends and holidays included.
Do all data breaches have to be notified?
No. A breach that is unlikely to result in a risk to the rights and freedoms of natural persons does not have to be notified (Art. 33(1)). It must still be documented internally, with the reasons for the decision (Art. 33(5)).
What does a processor have to do?
A processor notifies the controller without undue delay after becoming aware of a breach (Art. 33(2)) and assists it. The decision to notify the authority and the people concerned belongs to the controller.