# Data breach response plan under GDPR

Guide, read 16 November 2026

**The short answer.** Under GDPR Article 33 a controller must notify the supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk. This page, read on 16 November 2026, lists what a plan must do to meet it.

## How does GDPR affect a data breach response plan?

GDPR sets a 72-hour clock, a content list, a phasing rule, a documentation rule and a separate duty to tell individuals. Article 33(1) requires the controller to notify the competent authority without undue delay and, where feasible, not later than 72 hours after becoming aware, with reasons if later.

Article 33(3) lists the minimum content, Article 33(4) allows phased information, and Article 33(5) requires documenting every breach.

| Article | Duty | Plan section |
| --- | --- | --- |
| 33(1) | Notify the authority within 72 hours where feasible, unless unlikely to risk rights and freedoms | Part 4 |
| 33(2) | Processor notifies controller without undue delay | Part 4; supplier contacts |
| 33(3) | Notice describes the breach, contact point, likely consequences, measures taken | Part 5 |
| 33(4) | Information may be provided in phases | Part 5 |
| 33(5) | Document every breach: facts, effects, remedial action | Part 7 |
| 34(1) | Tell individuals without undue delay when high risk | Parts 4 and 5 |
| 34(3) | No duty if data was protected, risk no longer likely, or disproportionate effort | Part 3 |

How does GDPR affect a data breach response plan?

## When must individuals be told under GDPR?

Article 34 requires the controller to communicate the breach to the data subject without undue delay when it is likely to result in a high risk to their rights and freedoms, in clear and plain language. It need not do so if the data was made unintelligible, for example by encryption, if later measures mean the high risk is no longer likely, or if it would involve disproportionate effort, in which case a public communication is used.

## What does the UK regulator add?

The ICO guide says the UK GDPR requires reporting within 72 hours of becoming aware where feasible and that prioritizing and expediting the investigation is expected. See the [UK template](/templates/incident-response-plan-template-uk/).

For NIS2 entities, Article 23 sets a 24-hour early warning, a 72-hour incident notification and a final report within one month for significant incidents. The [SaaS template](/templates/incident-response-plan-template-saas/) shows how provider duties fit.

## Related pages

- [Data breach response plan: what it is and how to write one](/data-breach/)
- [Free incident response plan template](/)
- [What should a data breach response plan include?](/data-breach/what-should-a-data-breach-response-plan-include/)
- [Data breach response plan template](/data-breach/data-breach-response-plan-template/)
- [Incident response plan templates: the full set](/templates/)
- [Incident response plan: what it contains and how to build one](/plans/)

## Sources

- Regulation (EU) 2016/679 (GDPR), EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679 (read 16 November 2026)
- ICO, Personal data breaches: a guide: https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/ (read 16 November 2026)
- Directive (EU) 2022/2555 (NIS2), EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555 (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/data-breach/data-breach-response-plan-gdpr/
