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

# Art. 39 — Tasks of the data protection officer

1. The data protection officer shall have at least the following tasks:
   1. to inform and advise the [controller](https://headlesslaw.com/definitions/gdpr/controller/) or the [processor](https://headlesslaw.com/definitions/gdpr/processor/) and the employees who carry out [processing](https://headlesslaw.com/definitions/gdpr/processing/) of their obligations pursuant to this Regulation and to other Union or Member State data protection provisions;
   2. to monitor compliance with this Regulation, with other Union or Member State data protection provisions and with the policies of the controller or processor in relation to the protection of [personal data](https://headlesslaw.com/definitions/gdpr/personal-data/), including the assignment of responsibilities, awareness-raising and training of staff involved in processing operations, and the related audits;
   3. to provide advice where requested as regards the data protection impact assessment and monitor its performance pursuant to [Article 35](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/35.md);
   4. to cooperate with the [supervisory authority](https://headlesslaw.com/definitions/gdpr/supervisory-authority/);
   5. to act as the contact point for the supervisory authority on issues relating to processing, including the prior consultation referred to in [Article 36](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/36.md), and to consult, where appropriate, with regard to any other matter.
2. The data protection officer shall in the performance of his or her tasks have due regard to the risk associated with processing operations, taking into account the nature, scope, context and purposes of processing.


---

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