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

# Art. 41 — Monitoring of approved codes of conduct

1. Without prejudice to the tasks and powers of the competent [supervisory authority](https://headlesslaw.com/definitions/gdpr/supervisory-authority/) under [Articles 57](/mica.wtf/gdpr/chapter-vi-independent-supervisory-authorities-art.-51-59/57.md) and [58](/mica.wtf/gdpr/chapter-vi-independent-supervisory-authorities-art.-51-59/58.md), the monitoring of compliance with a code of conduct pursuant to [Article 40](/mica.wtf/gdpr/chapter-iv-controller-and-processor-art.-24-43/40.md) may be carried out by a body which has an appropriate level of expertise in relation to the subject-matter of the code and is accredited for that purpose by the competent supervisory authority.
2. A body as referred to in paragraph 1 may be accredited to monitor compliance with a code of conduct where that body has:
   1. demonstrated its independence and expertise in relation to the subject-matter of the code to the satisfaction of the competent supervisory authority;
   2. established procedures which allow it to assess the eligibility of controllers and processors concerned to apply the code, to monitor their compliance with its provisions and to periodically review its operation;
   3. established procedures and structures to handle complaints about infringements of the code or the manner in which the code has been, or is being, implemented by a [controller](https://headlesslaw.com/definitions/gdpr/controller/) or [processor](https://headlesslaw.com/definitions/gdpr/processor/), and to make those procedures and structures transparent to data subjects and the public; and
   4. demonstrated to the satisfaction of the competent supervisory authority that its tasks and duties do not result in a conflict of interests.
3. The competent supervisory authority shall submit the draft requirements for accreditation of a body as referred to in paragraph 1 of this Article to the Board pursuant to the consistency mechanism referred to in [Article 63](/mica.wtf/gdpr/chapter-vii-cooperation-and-consistency-art.-60-76/63.md).
4. Without prejudice to the tasks and powers of the competent supervisory authority and the provisions of Chapter VIII, a body as referred to in paragraph 1 of this Article shall, subject to appropriate safeguards, take appropriate action in cases of infringement of the code by a controller or processor, including suspension or exclusion of the controller or processor concerned from the code. It shall inform the competent supervisory authority of such actions and the reasons for taking them.
5. The competent supervisory authority shall revoke the accreditation of a body as referred to in paragraph 1 if the requirements for accreditation are not, or are no longer, met or where actions taken by the body infringe this Regulation.
6. This Article shall not apply to [processing](https://headlesslaw.com/definitions/gdpr/processing/) carried out by public authorities and bodies.


---

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