Article 40 GDPR

← Article 40 - Codes of conduct →
Chapter 1: General provisions Article 1: Subject-matter and objectives Article 2: Material scope Article 3: Territorial scope Article 4: Definitions Chapter 2: Principles Article 5: Principles relating to processing of personal data Article 6: Lawfulness of processing Article 7: Conditions for consent Article 8: Conditions applicable to child’s consent in relation to information society services Article 9: Processing of special categories of personal data Article 10: Processing of personal data relating to criminal convictions and offences Article 11: Processing which does not require identification Chapter 3: Rights of the data subject Article 12: Transparent information, communication and modalities for the exercise of the rights of the data subject Article 13: Information to be provided where personal data are collected from the data subject Article 14: Information to be provided where personal data have not been obtained from the data subject Article 15: Right of access by the data subject Article 16: Right to rectification Article 17: Right to erasure (‘right to be forgotten’) Article 18: Right to restriction of processing Article 19: Notification obligation regarding rectification or erasure of personal data or restriction of processing Article 20: Right to data portability Article 21: Right to object Article 22: Automated individual decision-making, including profiling Article 23: Restrictions Chapter 4: Controller and processor Article 24: Responsibility of the controller Article 25: Data protection by design and by default Article 26: Joint controllers Article 27: Representatives of controllers or processors not established in the Union Article 28: Processor Article 29: Processing under the authority of the controller or processor Article 30: Records of processing activities Article 31: Cooperation with the supervisory authority Article 32: Security of processing Article 33: Notification of a personal data breach to the supervisory authority Article 34: Communication of a personal data breach to the data subject Article 35: Data protection impact assessment Article 36: Prior consultation Article 37: Designation of the data protection officer Article 38: Position of the data protection officer Article 39: Tasks of the data protection officer Article 40: Codes of conduct Article 41: Monitoring of approved codes of conduct Article 42: Certification Article 43: Certification bodies Chapter 5: Transfers of personal data Article 44: General principle for transfers Article 45: Transfers on the basis of an adequacy decision Article 46: Transfers subject to appropriate safeguards Article 47: Binding corporate rules Article 48: Transfers or disclosures not authorised by Union law Article 49: Derogations for specific situations Article 50: International cooperation for the protection of personal data Chapter 6: Supervisory authorities Article 51: Supervisory authority Article 52: Independence Article 53: General conditions for the members of the supervisory authority Article 54: Rules on the establishment of the supervisory authority Article 55: Competence Article 56: Competence of the lead supervisory authority Article 57: Tasks Article 58: Powers Article 59: Activity reports Chapter 7: Cooperation and consistency Article 60: Cooperation between the lead supervisory authority and the other supervisory authorities concerned Article 61: Mutual assistance Article 62: Joint operations of supervisory authorities Article 63: Consistency mechanism Article 64: Opinion of the Board Article 65: Dispute resolution by the Board Article 66: Urgency procedure Article 67: Exchange of information Article 68: European Data Protection Board Article 69: Independence Article 70: Tasks of the Board Article 71: Reports Article 72: Procedure Article 73: Chair Article 74: Tasks of the Chair Article 75: Secretariat Article 76: Confidentiality Chapter 8: Remedies, liability and penalties Article 77: Right to lodge a complaint with a supervisory authority Article 78: Right to an effective judicial remedy against a supervisory authority Article 79: Right to an effective judicial remedy against a controller or processor Article 80: Representation of data subjects Article 81: Suspension of proceedings Article 82: Right to compensation and liability Article 83: General conditions for imposing administrative fines Article 84: Penalties Chapter 9: Specific processing situations Article 85: Processing and freedom of expression and information Article 86: Processing and public access to official documents Article 87: Processing of the national identification number Article 88: Processing in the context of employment Article 89: Safeguards and derogations relating to processing for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes Article 90: Obligations of secrecy Article 91: Existing data protection rules of churches and religious associations Chapter 10: Delegated and implementing acts Article 92: Exercise of the delegation Article 93: Committee procedure Chapter 11: Final provisions Article 94: Repeal of Directive 95: /46: /EC Article 95: Relationship with Directive 20: 02: /58: /EC Article 96: Relationship with previously concluded Agreements Article 97: Commission reports Article 98: Review of other Union legal acts on data protection Article 99: Entry into force and application

Legal Text

Article 40 - Codes of conduct

1. The Member States, the supervisory authorities, the Board and the Commission shall encourage the drawing up of codes of conduct intended to contribute to the proper application of this Regulation, taking account of the specific features of the various processing sectors and the specific needs of micro, small and medium-sized enterprises.

2. Associations and other bodies representing categories of controllers or processors may prepare codes of conduct, or amend or extend such codes, for the purpose of specifying the application of this Regulation, such as with regard to:

(a) fair and transparent processing;

(b) the legitimate interests pursued by controllers in specific contexts;

(c) the collection of personal data;

(d) the pseudonymisation of personal data;

(e) the information provided to the public and to data subjects;

(f) the exercise of the rights of data subjects;

(g) the information provided to, and the protection of, children, and the manner in which the consent of the holders of parental responsibility over children is to be obtained;

(h) the measures and procedures referred to in Articles 24 and 25 and the measures to ensure security of processing referred to in Article 32;

(i) the notification of personal data breaches to supervisory authorities and the communication of such personal data breaches to data subjects;

(j) the transfer of personal data to third countries or international organisations; or

(k) out-of-court proceedings and other dispute resolution procedures for resolving disputes between controllers and data subjects with regard to processing, without prejudice to the rights of data subjects pursuant to Articles 77 and 79.

3. In addition to adherence by controllers or processors subject to this Regulation, codes of conduct approved pursuant to paragraph 5 of this Article and having general validity pursuant to paragraph 9 of this Article may also be adhered to by controllers or processors that are not subject to this Regulation pursuant to Article 3 in order to provide appropriate safeguards within the framework of personal data transfers to third countries or international organisations under the terms referred to in point (e) of Article 46(2). Such controllers or processors shall make binding and enforceable commitments, via contractual or other legally binding instruments, to apply those appropriate safeguards including with regard to the rights of data subjects.

4. A code of conduct referred to in paragraph 2 of this Article shall contain mechanisms which enable the body referred to in Article 41(1) to carry out the mandatory monitoring of compliance with its provisions by the controllers or processors which undertake to apply it, without prejudice to the tasks and powers of supervisory authorities competent pursuant to Article 55 or 56.

5. Associations and other bodies referred to in paragraph 2 of this Article which intend to prepare a code of conduct or to amend or extend an existing code shall submit the draft code, amendment or extension to the supervisory authority which is competent pursuant to Article 55. The supervisory authority shall provide an opinion on whether the draft code, amendment or extension complies with this Regulation and shall approve that draft code, amendment or extension if it finds that it provides sufficient appropriate safeguards.

6. Where the draft code, or amendment or extension is approved in accordance with paragraph 5, and where the code of conduct concerned does not relate to processing activities in several Member States, the supervisory authority shall register and publish the code.

7. Where a draft code of conduct relates to processing activities in several Member States, the supervisory authority which is competent pursuant to Article 55 shall, before approving the draft code, amendment or extension, submit it in the procedure referred to in Article 63 to the Board which shall provide an opinion on whether the draft code, amendment or extension complies with this Regulation or, in the situation referred to in paragraph 3 of this Article, provides appropriate safeguards.

8. Where the opinion referred to in paragraph 7 confirms that the draft code, amendment or extension complies with this Regulation, or, in the situation referred to in paragraph 3, provides appropriate safeguards, the Board shall submit its opinion to the Commission.

9. The Commission may, by way of implementing acts, decide that the approved code of conduct, amendment or extension submitted to it pursuant to paragraph 8 of this Article have general validity within the Union. Those implementing acts shall be adopted in accordance with the examination procedure set out in Article 93(2).

10. The Commission shall ensure appropriate publicity for the approved codes which have been decided as having general validity in accordance with paragraph 9.

11. The Board shall collate all approved codes of conduct, amendments and extensions in a register and shall make them publicly available by way of appropriate means.

Relevant Recitals

Recital 98: Codes of Conduct

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.

Recital 99: Consultation of Stakeholders for Codes of Conduct

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.

Commentary

Article 40 GDPR outlines a possibility for actors to elaborate codes of conducts for the effective implementation of the GDPR in specific sectors or for specific processing activities.

(1) Drawing up codes of conduct

In the first place, it is important to clarify what is meant by a code of conduct. According to Article 40 GDPR, the purpose of a code of conducts is to “[contribute] to the proper application”, as well as “[specify] the application” of the GDPR. Additionally, they may be developed to “calibrate the obligations of controllers and processors” according to Recital 98 GDPR. As such, codes are intended to be an additional accountability tool which acts as a “rulebook for controllers and processors” that fall within the scope of the GDPR (and in certain cases, see below, those who fall outside of it). The codes provide measures which data controllers and processors in a specific sector can implement in addition to, or to comply with, their existing legal obligations under the GDPR.

Codes of conduct are not obligatory but rather potential tools that can be used to promote compliance. Article 40 GDPR elaborates upon a pre-existing provision under the Directive 95/46/EC (Data Protection Directive – DPD), specifically Article 27(1). Accordingly, certain codes of conduct have already been elaborated under Article 27 DPD. These include a code of conduct on use of personal data in direct marketing practices, which was developed by the Federation of European Direct and Interactive Marketing (FEDMA), and a code of conduct on Cloud service providers developed by Cloud Select Industry Group (C-SIG). Both were approved by the Article 29 Working Party (WP29). According to the EDPB Guidelines 1/2019 on Codes of Conduct and Monitoring Bodies under Regulation 2016/679, Article 40 GDPR provides more “specific and detailed provisions” concerning the requirements and procedural aspects for drafting codes than the DPD. The aim of Articles 40 and 41 GDPR is to ensure a “practical, potentially cost effective and meaningful method to achieve greater levels of consistency” in data protection law. This is particularly relevant given the fact that Member States may give effect to EU data protection law in ways which differ from their counterparts (e.g. where processing targeted by a code of conduct relates to a particular Member State).

Interestingly, the EDPB also suggests that codes can generate a degree of co-regulation amongst controllers and processors within the same processing sector. This in turn, can help alleviate burdens placed on DPAs by controllers and processors seeking advice about the legality of their processing activities under the GDPR. This is, in theory, a strong argument in favour of developing codes of conduct and their corresponding monitoring bodies (as discussed in this commentary on Article 41 GDPR). However, not many associations or other bodies have made use of this possibility under the GDPR. As such, controllers and processors remain reliant on DPAs for guidance on compliance, which unfortunately will generally lack the sector-specificity that makes codes of conduct attractive in terms of effective application of the GDPR.

Shall encourage

Codes of conduct themselves are not obligatory. Article 40(1) GDPR provides that Member States, DPAs, the EDPB and the European Commission (EC) shall “encourage” actors to develop codes of conduct. This terminology, emphasised by the fact that Article 40(2) GDPR provides that relevant actors “may” draw up such codes, highlights that the codes are developed on a voluntary basis. The EDPB Guidelines also support this reading. However, through a detailed reading of Article 40(1) GDPR, there is a clear obligation imposed on Member States, DPAs, the EDBP and the EC to encourage their draw up. Indeed, the wording of Article 40(1) establishes that they “shall encourage” this (emphasis added).

Specific features of a processing sector, specific needs

Article 40(1) GDPR clarifies that codes of conduct must be tailored to “specific features” of a sector, as well as the “specific needs of micro, small and medium-sized enterprises”. Recital 98 and 99 GDPR provide additional information as to how the content of these codes of conduct may be developed. The former highlights that the codes should take into account “risk likely to result from the [relevant] processing for the rights and freedoms of natural persons”. According to the latter recital, the drafter “should consult relevant stakeholders, including data subjects” in order to develop these codes. They should also duly consider the “submissions received and views expressed in response to such consultations”.

This specificity is strictly connected with Article 40(2) GDPR, which provides a list of potential topics which the codes may address. It is important to note that the wording of the Article suggests that the list is non-exhaustive and that these elements are not necessarily cumulative. The Article provides the following examples of topics for the codes: fairness and transparency in processing; controllers’ legitimate interests in particular contexts; collection of personal data; pseudonymisation; information to be provided to the public and to data subjects; data subjects’ rights and their exercise; processing children’s personal data (including information to be provided, protection and mechanisms for obtaining parental consent); technical and organisational measures and the obligations to guarantee privacy by design and by default; notification and communication of data breaches to the competent supervisory authority and to affected data subjects; data transfers to third countries or international organisations; or dispute resolution procedures.

(2) Associations and other bodies

According to Article 40(2) GDPR, codes of conduct are to be drafted by trade associations and other bodies “representing categories of controllers or processors”. Therefore, these drafters act as representatives of specific sectors. The EDPB also refers to them as “code owners”. There is some ambiguity in the wording of this GDPR provision. Article 40(1) GDPR outlines that the drawing up of codes must be encouraged without specifying what entities may actually draw the codes. Only Article 40(2) GDPR makes direct reference to “associations and other bodies”, without excluding the possibility that other actors may draft the codes of conduct as well. Therefore, at least in principle, it could be interpreted that a controller or processor can take up the task of drafting a code. However, Recital 98 GDPR makes direct reference to associations and other bodies when addressing the obligation to encourage drawing up of codes of conduct (Article 40(1) GDPR). Similarly, Article 40(5) GDPR only refers to associations and other bodies when specifying the steps to get a code approved. It may therefore be assumed that only such entities may develop these codes. The EDPB supports the suggestion that only associations and other bodies may draft codes.

(3) Controllers and processors that are not subject to the GDPR

Generally speaking, codes of conduct developed in accordance with Article 40 GDPR are aimed at categories of controllers and processors within the scope of application of the GDPR. These categories are determined by their varying processing sectors. For example, a code of conduct for processing of personal data by banks would differ from one for the education sector. This is clear from the wording of Article 40(1) GDPR, which specifies that the codes should take into account “the specific features of the various processing sectors”.  However, Article 40(3) GDPR provides that certain codes of conduct can be followed by controllers and processors of personal data that are not subject to the GDPR. Such codes must not only be approved by the competent DPAas per Article 40(5) GDPR,  but must also have gained general validity from the EC pursuant to Article 40(9) GDPR. The third country controllers and processors should also make “binding and enforceable commitments” (i.e. contractual or other legally binding instruments). Should entities not subject to the GDPR adhere to them, these codes of conduct will act as appropriate safeguards in the context of transfers of personal data to third countries or international organisations. The hope is that international codes will lead to the “promotion and cultivation of the level of protection which the GDPR provides to the wider international community”.

For this paragraph and its interaction with paragraph 40(2)(j), please see in particular Guidelines 04/2021 on Codes of Conduct as tools for transfers.

(4) Mandatory monitoring of compliance

Article 40(4) GDPR outlines that a code of conduct must necessarily contain information on how a monitoring body (provided for in Article 41 GDPR) can ensure compliance with it. It is important to note that such monitoring by these bodies should be carried out “without prejudice to the tasks and powers of supervisory authorities”, which means that the powers of such a monitoring body do not prevent the DPAs from using their own.

(5) Approval of codes of conduct

Article 40(5) GDPR outlines that associations and other bodies which “intend to prepare a code of conduct or to amend or extend an existing [one]” must submit their draft to the competent DPA. Once the code owner has submitted the draft, amendment or extension, in either an electronic or written format, the competent DPA should review the code of conduct against the admissibility criteria and the conditions for approval which will be discussed in the following subsections. The DPA will then approve the code, amendment or extension when it “provides sufficient appropriate safeguards”. Not much detail is provided by the provisions in the GDPR with regards to the admissibility criteria and conditions for approval. Therefore, much of the following discussion is derived from the EDPB Guidelines, which elaborate on these requirements.

Competent authority

Although Article 40(5) GDPR mentions that the competent DPA will be determined through the application of Article 55 GDPR, the GDPR does not provide concrete rules on this. However, the EDPB Guidelines explain how code owners may identify the competent DPA in its Annex 2. This document provides factors that can be considered such as: the Member State where most of the processing activity takes place, or where the processing sector is predominant; the Member State where data subjects are most affected; the Member State where the drafting association or other body has its headquarters; the Member State where the monitoring body will have its headquarters; or the Member State where a DPA has developed initiatives in the code of conduct’s specific field.

The code complies with the Regulation

Admissibility criteria

The EDPB Guidelines provide a series of conditions that code drafters should fulfil before considering submitting their code, amendment or extension to the competent DPA for approval. The content of the draft code, amendment or extension will not be reviewed further if it fails to fulfil the criteria for admissibility outlined below.

The first step for admissibility of a draft code of conduct is to have a “clear and concise explanatory statement”. This will include an explanation of: the purpose of the code; the scope of the code; and the way in which it will foster compliance with the GDPR. Supporting documentation will also provide additional clarity.

The draft code must be drafted by an association or other bodies representing categories of controllers and processors (Article 40(2) GDPR). The EDPB highlights that code owners must demonstrate to the competent authority that they fall within the meaning of “associations and other bodies” before submitting the code for approval. The Guidelines add that this entails providing proof of their capability to address the needs of controllers and processors and understanding of their processing activities.

The scope of application of the code must be sufficiently precise. This includes information on the type of processing performed, and the controllers and processors targeted by it. The drafters must clarify whether the code applies to processing within one or several Member States. This will then facilitate the determination of whether further steps must be taken (eg. general validity from the Commission, as elaborated upon in Article 40(9) GDPR).

The drafters must similarly ensure that steps for monitoring compliance are clearly laid out in the code of conduct. They must also provide for a monitoring body and the mechanisms that this body will apply to ensure compliance with it. The code drafters must consult relevant stakeholders such as data subjects, as well as controllers and processors, before the draft is considered admissible. This aspect is established in Recital 99 GDPR.

If national legislation applies, the association or other body drafting the code must confirm that it does not infringe such provisions. According to the EDPB, this is particularly the case if the code involves a sector which is specifically regulated by national law, or the processing at stake is subject to specific assessment requirements under national law.

The code must be written in the language in which the competent authority works in. Transnational codes, however, should also have an English version of the code, in addition to one in the competent DPA’s language. The code owner must ensure that they fulfil all the above conditions before submitting the code of conduct for approval. Annex 3 of the EDPB Guidelines provides a possible checklist for a code owner to verify this. They can then present it to the competent DPA.

Conditions for approval

The EDPB Guidelines also provide a series of criteria that must be fulfilled by code owners in order to gain formal approval for their code, amendment or extension from the competent DPA. The following sections reflect the minimum cumulative requirements for approval.

Firstly, the code must address a specific need or a data protection issue that is common in a sector, or in relation to a processing activity by a category of controllers or processors. The code owner must also demonstrate that it understands relevant processing issues, and clearly show how the code proposes to resolve them in an “effective and beneficial” way for their members and for data subjects. Without this, the code cannot get approval from the competent authority.

A key criterion for getting a code of conduct approved is described in Recital 98 GDPR: the code owner must ensure that the code “facilitate[s] the effective application of this Regulation” in the sector or processing activity it seeks to address. According to the EDPB Guidelines, in order to gain approval, the code drafters must ensure that the code of conduct specifies how the GDPR should apply in relation to the targeted processing activities or sector. This includes providing (non-exhaustively): clear improvements to ensure the targeted sector complies with the GDPR; realistic and attainable standards for the controllers and processors targeted; detailed information on data protection areas, such as those outlined in Article 40(2) GDPR; sufficiently clear and effective solutions to concerns over processing in this sector; an “operational meaning” of the Article 5 GDPR principles; and clarifications on any EDPD opinions or guidance for the specific sector.

The EDPB also clarifies that a code drafter cannot simply restate provisions within the GDPR. The codes must supplement the GDPR by providing information on how it “shall apply in a specific, practical and precise manner” which relates to the processing activity or sector at the heart of the code. This can be achieved by using, for example, sector-specific terminology without being too “legalistic”, and by giving examples of good practices.

As outlined in Article 40(5) GDPR, the code of conduct must provide sufficient appropriate safeguards, “taking into account the risk likely to result from the processing for the rights and freedoms of natural persons” (Recital 98 GDPR). An oversight and compliance monitoring mechanism is a requirement stipulated under Article 40(4) GDPR. According to the EDPB, structures and procedures for enforcing the code must be stipulated by the code owner before gaining approval. This includes identifying a monitoring body within the meaning of Article 41 GDPR. Such monitoring mechanisms must be “clear, suitable, attainable, efficient and enforceable (testable)”, according to the Guidelines.

Approval from the DPA

Subject to the code owners fulfilling the admissibility and approval requirements outlined above, the competent DPA can approve the draft code, amendment or extension pursuant to Article 40(5) GDPR. The EDPB Guidelines suggest that the DPA should do so within a “reasonable period of time” and update the code owners throughout the approval process. The DPA should motivate its approval in line with the prerequisite criteria for admissibility and approval, and in cases when it does not approve a code, it should provide a reasoning for its opinion. This can then enable the code owners to redraft and re-submit the code if they wish to do so.

(6) Publication of approved codes and codes with general validity

Article 40 GDPR provides additional requirements for publishing codes of conduct, amendments or extensions once they have been approved. This relates to both codes of conduct relating to processing activities in one Member State (national codes) and those relating to processing activities in several Member States (transnational codes, see below). The competent DPA that has approved a national code of conduct must then register and publish it in accordance with Article 40(6) GDPR. The same applies to any amendments or extensions submitted for approval. According to Article 40(10) GDPR, the EC is responsible for the “appropriate publicity” that should be given to a transnational code of conduct which has been granted “general validity”. It is uncertain whether the relevant DPAs will have to publish the transnational codes of conduct that they sought to approve prior to the cooperation mechanism, as they must do with national codes according to Article 40(6) GDPR.

(7-10) Role of the DPAs and the EDPB in the approval of codes with general validity

Codes of conduct relating to processing activities in several Member States are transnational codes, which must be granted “general validity” (Articles 40(7) GDPR to 40(10) GDPR).

The competent DPA with which the code owner has submitted the draft code, must determine whether this code fulfils the admissibility criteria mentioned above before proceeding. After this initial step, the authority will then notify other DPAs about the transnational code of conduct, pursuant to Article 40(7) GDPR. These DPAs will then confirm whether they are “supervisory authorities concerned” (see Article 4(22)(a)(b) GDPR). Finally, the competent DPA will cooperate with them in line with the consistency mechanism found under Article 63 GDPR. This includes sending a draft of the code of conduct that the main DPA intends to approve to the other concerned supervisory DPAs, which will have a 30 day time frame to give their feedback on it. As per Article 40(7) GDPR, the main DPA must then submit the draft code, amendment or extension, along with any responses from concerned DPAs, to the EDPB.

The EDPB will then generate an opinion as to whether the code of conduct complies with the GDPR, as per Article 40(7) GDPR. According to the terminology of Articles 40(7) and 40(8) GDPR, the EDPB’s opinion should identify whether the draft code provides “appropriate safeguards”. This opinion shall follow the Rules of Procedure of the EDPB, as well as Article 64 GDPR. After confirming that the code of conduct provides “appropriate safeguards”, there is an obligation[Wording: "shall".] imposed on the EDPB to “submit its opinion to the Commission” (Article 40(8) GDPR). After receiving the EDPB’s opinion, the EC will be the one to determine, “by way of implementing acts”, whether to grant the code of conduct “general validity within the Union” as per Article 40(9) GDPR. This provision specifies that the aforementioned “implementing acts” must be adopted in line with the examination procedure under Article 93(2) GDPR.

(11) Register of Codes of Conduct

Article 40(11) GDPR stipulates that the EDPB shall keep a register on “all approved codes of conduct, amendments and extensions” which is freely accessible and available to all “by way of appropriate means”. The wording in Article 40(11) GDPR only specifically refers to “approved codes” without mentioning those with “general validity”. This could lead to some ambiguity as to the scope of this provision. Nonetheless, it is presumed that this requirement to register codes of conducts applies to approved codes within the meaning of Articles 40(5) and (6) GDPR, as well as codes granted “general validity” by the European Commission as per Articles 40(7), (8), (9) and (10) GDPR. The reason behind this presumption is that it would not be logical for the EDPB to have to register codes of conduct approved by competent DPAs throughout the European Union, but not those subject to their opinion before submitting them to the European Commission for “general validity”. Additionally, the wording or Article 40(11) GDPR refers to “all approved codes of conducts”, which most likely includes the “[Commission] approved codes” referred to in Article 40(10) GDPR. The EDPB supports this view. The register can be found on the EDPB website. So far, only two codes of conduct (national ones) have been collated on this register. This includes a code of conduct by Nederland ICT (NL Digital) in the Netherlands, and one by Autocontrol (Asociación para la Autorregulación de la Comunicación Comercial) in Spain. However, it is apparent that there are various other codes of conduct that do not yet appear on the EDPB register, such as the codes of conduct approved by the Austrian, Dutch, or Italian DPAs.

Decisions

→ You can find all related decisions in Category:Article 40 GDPR