Data Breach Notification Requirements
What you'll learn: How GDPR's 72-hour notification rule works and who must be informed when personal data is compromised.
The Clock Starts Ticking
Under GDPR, when a data breach occurs involving personal data, you're racing against a strict deadline. Organizations must notify their supervisory authority (like the ICO in the UK or CNIL in France) within 72 hours of becoming aware of the breach—not when you discovered it happened, but when you became aware it happened.
Think of it like a fire alarm: the moment you know there's smoke, you must pull the alarm. You can't wait until you've investigated every room to understand the full extent of the damage.
Two-Tier Notification System
To Supervisory Authorities (72 hours): The notification must describe:
- Nature of the breach and data categories affected
- Approximate number of affected individuals
- Likely consequences
- Measures taken or proposed to address the breach
If you can't provide all details within 72 hours, you can submit them in phases—but the initial notification cannot wait.
To Affected Individuals (Without Undue Delay): You must notify individuals directly when the breach is likely to result in a "high risk" to their rights and freedoms. This isn't required if:
- You implemented strong encryption or other safeguards rendering data unintelligible
- You took subsequent measures eliminating the high risk
- Individual notifications would involve disproportionate effort (then public communication suffices)
Communications to individuals must be in clear, plain language explaining what happened, potential consequences, and protective measures they should take.
Key Takeaway: GDPR requires breach notification to supervisory authorities within 72 hours of awareness, plus direct communication to affected individuals when high risk exists—failure to comply can result in fines up to 2% of global annual revenue or €10 million, whichever is higher.