> 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/34.md).

# Art. 34 — Communication of a personal data breach to the data subject

1. When the [personal data breach](https://headlesslaw.com/definitions/gdpr/personal-data-breach/) is likely to result in a high risk to the rights and freedoms of natural persons, the [controller](https://headlesslaw.com/definitions/gdpr/controller/) shall communicate the personal data breach to the data subject without undue delay.
2. The communication to the data subject referred to in paragraph 1 of this Article shall describe in clear and plain language the nature of the [personal data](https://headlesslaw.com/definitions/gdpr/personal-data/) breach and contain at least the information and measures referred to in points (b), (c) and (d) of [Article 33(3)](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/33.md).
3. The communication to the data subject referred to in paragraph 1 shall not be required if any of the following conditions are met:
   1. the controller has implemented appropriate technical and organisational protection measures, and those measures were applied to the personal data affected by the personal data breach, in particular those that render the personal data unintelligible to any person who is not authorised to access it, such as encryption;
   2. the controller has taken subsequent measures which ensure that the high risk to the rights and freedoms of data subjects referred to in paragraph 1 is no longer likely to materialise;
   3. it would involve disproportionate effort. In such a case, there shall instead be a public communication or similar measure whereby the data subjects are informed in an equally effective manner.
4. If the controller has not already communicated the personal data breach to the data subject, the [supervisory authority](https://headlesslaw.com/definitions/gdpr/supervisory-authority/), having considered the likelihood of the personal data breach resulting in a high risk, may require it to do so or may decide that any of the conditions referred to in paragraph 3 are met.


---

# 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/34.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.