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

# Art. 36 — Prior consultation

1. The [controller](https://headlesslaw.com/definitions/gdpr/controller/) shall consult the [supervisory authority](https://headlesslaw.com/definitions/gdpr/supervisory-authority/) prior to [processing](https://headlesslaw.com/definitions/gdpr/processing/) where a data protection impact assessment under [Article 35](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/35.md) indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk.
2. Where the supervisory authority is of the opinion that the intended processing referred to in paragraph 1 would infringe this Regulation, in particular where the controller has insufficiently identified or mitigated the risk, the supervisory authority shall, within period of up to eight weeks of receipt of the request for consultation, provide written advice to the controller and, where applicable to the [processor](https://headlesslaw.com/definitions/gdpr/processor/), and may use any of its powers referred to in [Article 58](/mica.wtf/gdpr/chapter-vi-independent-supervisory-authorities-art.-51-59/58.md). That period may be extended by six weeks, taking into account the complexity of the intended processing. The supervisory authority shall inform the controller and, where applicable, the processor, of any such extension within one month of receipt of the request for consultation together with the reasons for the delay. Those periods may be suspended until the supervisory authority has obtained information it has requested for the purposes of the consultation.
3. When consulting the supervisory authority pursuant to paragraph 1, the controller shall provide the supervisory authority with:
   1. where applicable, the respective responsibilities of the controller, joint controllers and processors involved in the processing, in particular for processing within a [group of undertakings](https://headlesslaw.com/definitions/gdpr/group-of-undertakings/);
   2. the purposes and means of the intended processing;
   3. the measures and safeguards provided to protect the rights and freedoms of data subjects pursuant to this Regulation;
   4. where applicable, the contact details of the data protection officer;
   5. the data protection impact assessment provided for in [Article 35](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/35.md); and
   6. any other information requested by the supervisory authority.
4. Member States shall consult the supervisory authority during the preparation of a proposal for a legislative measure to be adopted by a national parliament, or of a regulatory measure based on such a legislative measure, which relates to processing.
5. Notwithstanding paragraph 1, Member State law may require controllers to consult with, and obtain prior authorisation from, the supervisory authority in relation to processing by a controller for the performance of a task carried out by the controller in the public interest, including processing in relation to social protection and public health.


---

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