EU regulatory register · GDPR
Article 33Notification of a personal data breach to the supervisory authority
CELEX 32016R0679 · Read on 2026-08-18 · Chapter IV
When must a personal data breach be notified under the GDPR?
Under Article 33 of the GDPR (EU) 2016/679 the controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach. Notification is not needed if the breach is unlikely to result in a risk to people's rights. Late notification must be justified, and every breach must be documented.
EUR-Lex · Source: NovaCopilot
Short answer
1. In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of …
Verbatim from the article. Source: NovaCopilot · https://legal.exploreworldai.com/eu/rattsakter/gdpr-2016-679/artikel-33 · Short answer as data · Official text
Official text
Read from the EU Publications Office for this CELEX number. The wording stands as published; nothing here is rewritten or summarised.
1. In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons. Where the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by reasons for the delay.
2. The processor shall notify the controller without undue delay after becoming aware of a personal data breach.
3. The notification referred to in paragraph 1 shall at least:
(a)
describe the nature of the personal data breach including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
(b)
communicate the name and contact details of the data protection officer or other contact point where more information can be obtained;
(c)
describe the likely consequences of the personal data breach;
(d)
describe the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
4. Where, and in so far as, it is not possible to provide the information at the same time, the information may be provided in phases without undue further delay.
5. The controller shall document any personal data breaches, comprising the facts relating to the personal data breach, its effects and the remedial action taken. That documentation shall enable the supervisory authority to verify compliance with this Article.
Follow-up questions
Other articles in this chapter
Related articles
Articles in other acts connected to this one, with the reason written against the text. The map is a route between acts, not an assessment.
- Intersects with · mutualDORA · 19
Reporting a major ICT-related incident and notifying a personal data breach can be triggered by the same event at a financial entity.
CELEX 32022R2554 · 2026-08-18
- Intersects with · mutualNIS2 · 23
One and the same incident can trigger notification to the data protection authority and to the CSIRT, on different deadlines and to different recipients.
CELEX 32022L2555 · 2026-08-18
Knowledge card
- Applies
- controller: Notify a personal data breach to the supervisory authority. · processor: Notify the controller without undue delay after becoming aware of a breach.
- Risk if ignored
- high
- What to do
- Notify a personal data breach to the supervisory authority. · Notify the controller without undue delay after becoming aware of a breach.
- Deadline
- Not later than 72 hours after becoming aware, where feasible.
card:eu:article:gdpr--art-33 · sha256 c54deb5c44e5 · Source: NovaCopilot
Risk, sanction and outcome
Art. 33 · controller
Risk: high · Sanction: administrative_fine, högst EUR 10 000 000 · Authority: Competent supervisory authority
Decisions applying the provision: none in the register
Full chain (JSON)Art. 33 · processor
Risk: high · Sanction: administrative_fine, högst EUR 10 000 000 · Authority: Competent supervisory authority
Decisions applying the provision: none in the register
Full chain (JSON)
Outcomes are counted from stored judgments that cite the provision verbatim. Source: NovaCopilot
Everyday agents built on this article
Judgments applying this article
7 judgments in the register cite the article in their text. EU 1 · DE 6
Source: NovaCopilot
Recitals that carry the interpretation
The recitals in the preamble have no legal force of their own but often decide how the article is read. The links are curated against the official text. Read 2026-08-31.
Skäl 85 · Article 33
What a personal data breach is and when it is likely to result in risk, the basis of the 72-hour duty.
The text is quoted from the official source and is not legal advice. A national court reads the language version that binds in its jurisdiction.
Verifiable trust signals
- Six fixed blocks, one source per line
- No sentence written by a language model
- Engine version and read date on every answer
- No customer data, no documents, no advice
- Model card and audit published under the EU AI Act