> For the complete documentation index, see [llms.txt](https://www.headlesslaw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.headlesslaw.com/gdpr/articles/31.md).

# Article 31 — Cooperation with the supervisory authority

*In force · Consolidated version of 4 May 2016 · Checked against EUR-Lex on 30 Sep 2026 ·* [*Official source*](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504)

The [controller](https://www.headlesslaw.com/definitions/gdpr/controller) and the [processor](https://www.headlesslaw.com/definitions/gdpr/processor) and, where applicable, their representatives, shall cooperate, on request, with the [supervisory authority](https://www.headlesslaw.com/definitions/gdpr/supervisory-authority) in the performance of its tasks.

***

[Chapter IV — Controller and processor](/gdpr/chapters/iv.md) · [← Article 30](/gdpr/articles/30.md) · [Article 32 →](/gdpr/articles/32.md)


---

# 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.headlesslaw.com/gdpr/articles/31.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.