← Back to Insights
November 18, 2026 · 4 min read · GDPR

GDPR Breach Notification: The 72h Clock

Under GDPR, if personal data is breached, you have 72 hours to notify the supervisory authority. That's not 72 hours to fix it — 72 hours to notify. Here's what counts, who to tell, and what evidence to keep.

What counts as a personal data breach

A stolen laptop with customer data is a breach. An email with patient records sent to the wrong hospital is a breach. A misconfigured S3 bucket exposing CVs is a breach.

The 72h deadline

72 hours from when you become aware — not from when the breach technically occurred. If an attacker was in your system for months but you discovered it today, the clock starts today.

Notification to the supervisory authority must include:

When to notify affected individuals

When the breach is likely to result in high risk to individuals, you must notify them 'without undue delay.' Not when convenient — when the risk is high. If the data is encrypted and keys are safe, notification may not be required. If the data is in plaintext, it likely is.

GDPR's 72h and NIS2's 24h/72h are different deadlines for different regulations. If personal data is involved, both apply. GDPR notification to the DPA, NIS2 notification to the CSIRT. Both need evidence. Both have penalties for late reporting.

Questions about this?

Get in touch. 15-minute call, no obligation.

Get in touch

Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.