Article 39 GDPR
Legal Text
1. The data protection officer shall have at least the following tasks:
- (a) to inform and advise the controller or the processor and the employees who carry out processing of their obligations pursuant to this Regulation and to other Union or Member State data protection provisions;
- (b) 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, including the assignment of responsibilities, awareness-raising and training of staff involved in processing operations, and the related audits;
- (c) to provide advice where requested as regards the data protection impact assessment and monitor its performance pursuant to Article 35;
- (d) to cooperate with the supervisory authority;
- (e) to act as the contact point for the supervisory authority on issues relating to processing, including the prior consultation referred to in Article 36, 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.
Relevant Recitals
Commentary
Article 39, titled "Tasks of the data protection officer", outlines the primary responsibilities of the Data Protection Officer (DPO).[1] Among these, paragraph 1 lists the obligation for the DPO to inform the controller, processor, and their staff about the obligations arising from the GDPR and other applicable data protection laws. The DPO is also required to monitor compliance with the GDPR within their assigned organization, which includes ensuring adherence to relevant internal policies, staff training, and conducting audits as necessary. Additionally, the DPO must provide support for the preparation of Data Protection Impact Assessments (DPIAs) in accordance with Article 35. They are further expected to cooperate with the Data Protection Authority (DPA) on any matters or issues related to data protection, including the requirement for prior consultation as specified in Article 36 of the GDPR. Finally, paragraph 2 emphasizes that, in fulfilling their duties, the DPO must take into account the risks associated with data processing operations, considering the nature, scope, context, and purposes of the processing.
(1) DPO's Tasks
Paragraph 1 provides a comprehensive list of tasks that the DPO must perform according to the GDPR, and these tasks cannot be restricted by national regulations. However, the use of the phrase "at least" implies that additional functions or duties may be assigned to the DPO, such as conducting training for the controller's employees. To include such additional functions, they must be explicitly specified in the appointment document or in relevant updates. In accordance with Article 38(2) of the GDPR, the DPO must receive all necessary resources to fulfill these supplementary tasks effectively. This ensures that the DPO is adequately equipped and supported to carry out their responsibilities in a comprehensive and efficient manner.[2]
(a) Inform and advise
(b) Monitor compliance
Under Article 39(1)(b) as well as Recital 97 GDPR, the DPO should not only inform and advise controllers or processing regarding compliance with data protection laws, but also monitor that compliance. In doing so, according to the Article 29 Working Party (WP29), the DPO may collect information to identify processing activities, analyse and check the compliance of processing activities, as well as inform, advise and issue recommendations to them.[3]
(c) Advise on and monitor over enforcement of the DPIA
Furthermore, the DPO has a central role throughout the Data Protection Impact Assessment (DPIA) process. While ultimately it is the controller or processor’s responsibility to ensure compliance and conduct a DPIA where needed, Article 39(1)(c) requires the DPO to “provide advice where requested as regards the [DPIA] and monitor its performance pursuant to Article 35.”[4]
(d) Cooperate with the supervisory authority
(e) Contact point for the supevisory authority
Articles 39(1)(d) and (e) GDPR and lay down the DPO’s obligations in relation to the Data Protection Authorities (DPAs). For example, the DPO could facilitate cooperation in prior consultation procedures or DPA investigations.[5] This contact point function as an obligation for the controller or processor to involve the DPO in any contact with DPAs.[6] However, while DPAs can always contact the DPO, contacting other members of an organisation is also possible.[7] Finally, although the DPO is bound by confidentiality, they may still contact and seek advice from the DPA.[8]
(2) High Risk Activities
According to Article 39(2) GDPR, the DPO must “have due regard to the risk associated with the processing operations, taking into account the nature, scope, context and purposes of processing.” While this provision is meant to help DPOs prioritise their tasks or choose the most adequate DPIA methodology, it does not mean that low-risk areas may ever be neglected.[9] A risk-based approach should never mean that processing activities which do not pose a high risk are exempt from any of the GDPR’s protections.
Decisions
→ You can find all related decisions in Category:Article 39 GDPR
References
- ↑ Just as Article 38 GDPR, Article 39 GDPR also shows similarities with Regulation 45/2001, which mandated each of the European Union institutions, bodies, and agencies to appoint a data protection officer (DPO). The roots of Article 39 GDPR can be partially retraced to the GDPR’s predecessor, the Directive 95/46/EC (DPD). In particular, Article 18 DPD mentioned the role of a ‘data protection official’ who ensured “that the rights and freedoms of the data subjects are unlikely to be adversely affected by the processing operations” and who was responsible in particular: (i) “for ensuring in an independent manner the internal application” of national data protection laws; and (ii) “for keeping an internal register of processing operations carried out by the controller.”
- ↑ Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 39 GDPR, margin number 10 (C.H. Beck 2020, 3rd edition).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available here).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available here).
- ↑ Alvarez Rigaudias, Spina, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 39 GDPR, p. 714 (Oxford University Press 2020).
- ↑ Alvarez Rigaudias, Spina, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 39 GDPR, p. 714 (Oxford University Press 2020).
- ↑ Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 39 GDPR, margin number 18 (C.H. Beck 2020, 3rd Edition).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 19 (available here).
- ↑ WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 18 (available here).