> 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-iii-rights-of-the-data-subject-art.-12-23/12.md).

# Art. 12 — Transparent information, communication and modalities for the exercise of the rights of the data subject

1. The [controller](https://headlesslaw.com/definitions/gdpr/controller/) shall take appropriate measures to provide any information referred to in [Articles 13](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/13.md) and [14](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/14.md) and any communication under [Articles 15](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/15.md) to 22 and 34 relating to [processing](https://headlesslaw.com/definitions/gdpr/processing/) to the data subject in a concise, transparent, intelligible and easily accessible form, using clear and plain language, in particular for any information addressed specifically to a child. The information shall be provided in writing, or by other means, including, where appropriate, by electronic means. When requested by the data subject, the information may be provided orally, provided that the identity of the data subject is proven by other means.
2. The controller shall facilitate the exercise of data subject rights under [Articles 15](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/15.md) to 22. In the cases referred to in [Article 11(2)](/mica.wtf/gdpr/chapter-ii-principles-art.-5-11/11.md), the controller shall not refuse to act on the request of the data subject for exercising his or her rights under [Articles 15](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/15.md) to 22, unless the controller demonstrates that it is not in a position to identify the data subject.
3. The controller shall provide information on action taken on a request under [Articles 15](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/15.md) to 22 to the data subject without undue delay and in any event within one month of receipt of the request. That period may be extended by two further months where necessary, taking into account the complexity and number of the requests. The controller shall inform the data subject of any such extension within one month of receipt of the request, together with the reasons for the delay. Where the data subject makes the request by electronic form means, the information shall be provided by electronic means where possible, unless otherwise requested by the data subject.
4. If the controller does not take action on the request of the data subject, the controller shall inform the data subject without delay and at the latest within one month of receipt of the request of the reasons for not taking action and on the possibility of lodging a complaint with a [supervisory authority](https://headlesslaw.com/definitions/gdpr/supervisory-authority/) and seeking a judicial remedy.
5. Information provided under [Articles 13](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/13.md) and [14](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/14.md) and any communication and any actions taken under [Articles 15](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/15.md) to 22 and 34 shall be provided free of charge. Where requests from a data subject are manifestly unfounded or excessive, in particular because of their repetitive character, the controller may either:

   1. charge a reasonable fee taking into account the administrative costs of providing the information or communication or taking the action requested; or
   2. refuse to act on the request.

   The controller shall bear the burden of demonstrating the manifestly unfounded or excessive character of the request.
6. Without prejudice to [Article 11](/mica.wtf/gdpr/chapter-ii-principles-art.-5-11/11.md), where the controller has reasonable doubts concerning the identity of the natural person making the request referred to in [Articles 15](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/15.md) to 21, the controller may request the provision of additional information necessary to confirm the identity of the data subject.
7. The information to be provided to data subjects pursuant to [Articles 13](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/13.md) and [14](/mica.wtf/gdpr/chapter-iii-rights-of-the-data-subject-art.-12-23/14.md) may be provided in combination with standardised icons in order to give in an easily visible, intelligible and clearly legible manner a meaningful overview of the intended processing. Where the icons are presented electronically they shall be machine-readable.
8. The Commission shall be empowered to adopt delegated acts in accordance with [Article 92](/mica.wtf/gdpr/chapter-x-delegated-acts-and-implementing-acts-art.-92-93/92.md) for the purpose of determining the information to be presented by the icons and the procedures for providing standardised icons.


---

# 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-iii-rights-of-the-data-subject-art.-12-23/12.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.
