Article 38 GDPR
Legal Text
1. The controller and the processor shall ensure that the data protection officer is involved, properly and in a timely manner, in all issues which relate to the protection of personal data.
2. The controller and processor shall support the data protection officer in performing the tasks referred to in Article 39 by providing resources necessary to carry out those tasks and access to personal data and processing operations, and to maintain his or her expert knowledge.
3. The controller and processor shall ensure that the data protection officer does not receive any instructions regarding the exercise of those tasks. He or she shall not be dismissed or penalised by the controller or the processor for performing his tasks. The data protection officer shall directly report to the highest management level of the controller or the processor.
4. Data subjects may contact the data protection officer with regard to all issues related to processing of their personal data and to the exercise of their rights under this Regulation.
5. The data protection officer shall be bound by secrecy or confidentiality concerning the performance of his or her tasks, in accordance with Union or Member State law.
6. The data protection officer may fulfil other tasks and duties. The controller or processor shall ensure that any such tasks and duties do not result in a conflict of interests.
Relevant Recitals
Commentary
While it brings a novel element, the data protection officer (DPO) role draws inspiration from Regulation 45/2001, which foresaw a similar position for European Union institutions, bodies, and agencies. Indeed, the GDPR’s DPO position shows many common elements with the aforementioned Regulation.[1] In addition, although Directive 95/46/EC did not require organisations to appoint a DPO, this nevertheless became an increasingly widespread practice in some Member States.[2]
(1)(2) The Role of the DPO in the Organisation
According to Article 38(1) GDPR, the DPO must be involved in a timely manner in all issues which relate to the protection of personal data. In this context, a timely manner would be the earliest possible stage, ideally at the stage of conceptualising the processing operation.[For example, this could be the design and development of a product, as well as the creation of a new service or modification of an existing one by adding new features.] In any case, the DPO should be involved at a stage when fundamental decisions can still be made.[3] Among others, the early involvement is also necessary in order to adequately conduct a Data Protection Impact Assessment (DPIA) and facilitate a privacy by design approach.[4] DPOs should also be regularly involved in management meetings, and opinions of the DPO should be given due weight. In case management disagrees with the DPO’s opinions, the Article 29 Working Party recommends documenting the reasons for not following the DPO’s position.[5] Indeed, this best practice seems highly important for implementing the principle of accountability (Articles 5(2) and 24 GDPR). In any case, the DPO will not be held personally liable for the non-compliance of the organisation.[6] As reflected in Article 38(2) GDPR, the DPO must be provided with all necessary resources to carry out their tasks, including by having access to personal data and processing operations. Member States cannot limit the controlling competences of the DPO.[7] In addition, the DPO must be allowed to enter all premises where personal data is or may be processed, including on the premises of data processors.[8]
(3)(5) Independence and Confidentiality
According to Article 38(3) GDPR, the DPO’s independence in the organisation must be guaranteed by the controller or processor. In particular, the DPO may not receive any instructions from either of them regarding their tasks, and may not be dismissed or sanctioned for performing these tasks. This extends to the personnel working under the DPO, which should only receive substantive directions from the DPO and not from the controller or processor.[9] Regarding penalties or sanctions related to the exercise of the DPO’s functions, a broad interpretation must be followed. For example, the DPO may not suffer disadvantages in the form of threats, absence or delay of promotion, or denial from benefits which other employees receive. Regarding the confidentiality requirements of Article 38(5) GDPR, it is worth emphasising that the “obligation of secrecy/confidentiality does not prohibit the DPO from contacting and seeking advice from the supervisory authority”.[10] Furthermore, Member States may regulate and limit the confidentiality requirements at the national level, as well as the legal consequences of breaching these requirements.[11]
(6) Conflicts of Interest
Tightly connected to the independence requirement is Article 38(6) GDPR which emphasises that while the DPO may fulfill other tasks and duties, these should not result in a conflict of interest. When interpreting this requirement, the WP29 has stated that the DPO may not hold positions which result in determining the purposes and means of the processing. Examples of such conflicting positions could be “senior management positions (such as chief executive, chief operating, chief financial, chief medical officer, head of marketing department, head of Human Resources or head of IT departments) but also other roles lower down in the organisational structure if such positions or roles lead to the determination of purposes and means of processing”.[12] Some commentators also have also interpreted that a possible indicator of a conflict of interest is related to the cases where the DPO may benefit economically from the success of the organisation they are working for.[13]
Decisions
→ You can find all related decisions in Category:Article 38 GDPR
References
- ↑ Alvarez Rigaudias, Spina, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 38 GDPR, p. 702 (Oxford University Press 2020).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPOs’)’, 16/EN WP 243 rev.01, 5 April 2017, p. 4 (available here).
- ↑ Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 38 GDPR, margin number 14 (C.H. Beck 2020, 3rd Edition).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPOs’)’, 16/EN WP 243 rev.01, 5 April 2017, p. 13 (available here).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPOs’)’, 16/EN WP 243 rev.01, 5 April 2017, p. 14 (available here).
- ↑ Alvarez Rigaudias, Spina, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 38 GDPR, p. 707 (Oxford University Press 2020).
- ↑ Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 38 GDPR, margin number 18 (C.H. Beck 2020, 3rd Edition).
- ↑ Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 38 GDPR, margin number 20 (C.H. Beck 2020, 3rd Edition).
- ↑ Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 38 GDPR, margin number 26 (C.H. Beck 2020, 3rd Edition).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPOs’)’, 16/EN WP 243 rev.01, 5 April 2017, p. 18 (available here).
- ↑ See Article 35(3) GDPR.
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPOs’)’, 16/EN WP 243 rev.01, 5 April 2017, p. 16 (available here).
- ↑ Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 38 GDPR, margin number 41 (C.H. Beck 2020, 3rd Edition).