> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/33.md).

# Art. 33 — Notification of a personal data breach to the supervisory authority

1. In the case of a [personal data breach](https://headlesslaw.com/definitions/gdpr/personal-data-breach/), the [controller](https://headlesslaw.com/definitions/gdpr/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](https://headlesslaw.com/definitions/gdpr/supervisory-authority/) competent in accordance with [Article 55](/mica.wtf/gdpr/chapter-vi-independent-supervisory-authorities-art.-51-59/55.md), 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](https://headlesslaw.com/definitions/gdpr/processor/) shall notify the controller without undue delay after becoming aware of a [personal data](https://headlesslaw.com/definitions/gdpr/personal-data/) breach.
3. The notification referred to in paragraph 1 shall at least:
   1. 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;
   2. communicate the name and contact details of the data protection officer or other contact point where more information can be obtained;
   3. describe the likely consequences of the personal data breach;
   4. 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/33.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.