Data & Privacy
- Data Act
- Data Governance Act
- ePrivacy Directive
- GDPR
AI & Trust
- Artificial Intelligence Act
Cybersecurity
- Cybersecurity Act
- DORA
- NIS2
Digital Services & Media
- Digital Markets Act
- Digital Services Act
- European Media Freedom Act
General Data Protection Regulation
- Recitals
CHAPTER I
General provisionsArticles 1 — 4
CHAPTER II
PrinciplesArticles 5 — 11
CHAPTER III
Rights of the data subjectArticles 12 — 23
CHAPTER IV
Controller and processorArticles 24 — 43
CHAPTER V
Transfers of personal data to third countries or international organisationsArticles 44 — 50
CHAPTER VI
Independent supervisory authoritiesArticles 51 — 59
CHAPTER VII
Cooperation and consistencyArticles 60 — 76
CHAPTER VIII
Remedies, liability and penaltiesArticles 77 — 84
CHAPTER IX
Provisions relating to specific processing situationsArticles 85 — 91
CHAPTER X
Delegated acts and implementing actsArticles 92 — 93
CHAPTER XI
Final provisionsArticles 94 — 99
GDPR Article 41. Monitoring of approved codes of conduct
- 1.Without prejudice to the tasks and powers of the competent supervisory authority under Articles 57 and 58, the monitoring of compliance with a code of conduct pursuant to Article 40 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:
- (a)demonstrated its independence and expertise in relation to the subject-matter of the code to the satisfaction of the competent supervisory authority;
- (b)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;
- (c)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 or processor, and to make those procedures and structures transparent to data subjects and the public; and
- (d)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 criteria 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.
- 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 conditions 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 carried out by public authorities and bodies.
Relevant Recitals for this Article
Associations or other bodies representing categories of controllers or processors should be encouraged to draw up codes of conduct, within the limits of this Regulation, so as to facilitate the effective application of this Regulation, taking account of the specific characteristics of the processing carried out in certain sectors and the specific needs of micro, small and medium enterprises. In particular, such codes of conduct could calibrate the obligations of controllers and processors, taking into account the risk likely to result from the processing for the rights and freedoms of natural persons.
When drawing up a code of conduct, or when amending or extending such a code, associations and other bodies representing categories of controllers or processors should consult relevant stakeholders, including data subjects where feasible, and have regard to submissions received and views expressed in response to such consultations.