Article 39 GDPR: Difference between revisions

From GDPRhub
 
(3 intermediate revisions by 2 users not shown)
Line 206: Line 206:


==Commentary==
==Commentary==
Article 39, titled "''Tasks of the data protection officer''", outlines the primary responsibilities of the Data Protection Officer (DPO).<ref>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.''”</ref> 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.  
Article 39, titled "''Tasks of the data protection officer''", outlines the primary responsibilities of the Data Protection Officer (DPO).<ref>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.''”</ref> 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 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 ===
=== (1) DPO's Tasks ===
Line 212: Line 212:


==== (a) Inform and advise ====
==== (a) Inform and advise ====
The first task of the DPO is to inform and advise the controller, processor, and employees about their respective obligations under the GDPR and other applicable data protection laws.
Regarding the scope of the obligation to inform and advise, all Chapter IV of the GDPR, which covers the general obligations of the controller and processor, becomes relevant. Notable elements include technical and organizational measures required to demonstrate compliance (Article 24), the selection of technical capabilities and default settings to ensure compliance with rights and the GDPR from the outset of data processing (Article 25), obligations related to joint controllers and processors (Articles 26 and 28, respectively), maintaining records of processing activities (Article 30), ensuring the security of processing (Article 32), responsibilities of the DPO in case of data breaches (Articles 33 and 34), and preparation of data protection impact assessments and prior consultation (Articles 35 and 36). Additionally, as correctly noted, the obligations of the controller or processor also arise from other chapters of the GDPR (e.g., regarding data subjects' exercise of rights) or from other applicable laws, both at the European level (e.g., the e-Privacy Directive) and the national level (due to various references made by the GDPR).
The obligation to inform covers any legal matters or developments concerning data protection, such as new legislative requirements, innovative judicial interpretations, or technical developments that could change previous risk assessments. This obligation is proactive, meaning that it is up to the DPO to inform the recipient (controller or processor) about such elements. On the other hand, the obligation to advise relates to specific  issues arising during data processing operations. In such cases, the DPO clarifies the obligations that arise in a specific situation and provides solutions in line with applicable laws. In practice, the data protection officer's responsibility for informing and advising can be carried out through various approaches.
A practical example could be the issuing a circular to the management, authority, or key personnel within the company or organization, highlighting the latest developments in data protection laws. This circular may also offer the assurance that the data protection officer is available to provide further elaboration and explanation on the raised issues if needed.<ref>''Drewes'', in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 39 GDPR, margin numbers 7-15 (C.H. Beck 2019).</ref>


==== (b) Monitor compliance ====
==== (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.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref>
Article 39(1)(b) assigns DPOs the responsibility to monitor compliance with the GDPR, as further specified in Recital 97, which states that the DPO should assist the controller or processor in monitoring internal compliance with the Regulation. As part of their duty to monitor compliance, DPOs may engage in various activities, such as collecting information to identify processing operations, analyzing and verifying the compliance of such operations, and providing information, advice, and recommendations to the controller or processor. It is essential to note that monitoring compliance does not imply personal responsibility on the part of the DPO in cases of non-compliance. The GDPR explicitly states that the controller, not the DPO, is obligated to implement appropriate technical and organizational measures to ensure and demonstrate that processing aligns with the Regulation (Article 24(1) GDPR). Therefore, data protection compliance is ultimately a corporate responsibility of the data controller and not that of the DPO.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref>
 
==== (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.''”<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref>


==== (d) Cooperate with the supervisory authority ====
==== (c) Advise on the DPIA ====
As per Article 35(1), conducting a data protection impact assessment (DPIA) is the responsibility of the controller, not the DPO, when deemed necessary. Nonetheless, the DPO can still play a valuable role in assisting the controller. In line with the principle of data protection by design, Article 35(2) explicitly states that the controller must "seek advice" from the DPO when undertaking a DPIA. Additionally, Article 39(1)(c) assigns to the DPO the task of providing advice, upon request, concerning the DPIA and monitoring its execution as outlined in Article 35.<blockquote><u>WP29</u>: The WP29 recommends that the controller seeks the advice of the DPO on various issues, including whether to conduct a DPIA, the appropriate methodology for the DPIA, whether to perform the DPIA internally or outsource it, what safeguards to apply to address risks to data subjects' rights and interests, and whether the DPIA has been correctly carried out and its conclusions comply with the GDPR.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]). The WP29 also recalls that Article 39(1) mentions the tasks of the DPO and indicates that the DPO shall have ‘''at least’'' the following tasks. Therefore, nothing prevents the controller from assigning the DPO other tasks than those explicitly mentioned in Article 39(1), or specifying those tasks in more detail.</ref></blockquote>Moreover, to the data protection officer is also assigned the responsibility to ''actively'' monitor the implementation of a DPIA, rather than solely upon request. The data protection officer is required to assess compliance with the requirements outlined in Article 35 and review the content assessments conducted. In doing so, the DPO should have access to the relevant documentation. Subsequently, the DPO should provide a report on the evaluation of the process, forwarding any significant deficiencies to the relevant staff. In cases of severe shortcomings, the report should also be escalated to management or the appropriate authority.<ref>''Drewes'', in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 39 GDPR, margin numbers 34 (C.H. Beck 2019). </ref>


==== (e) Contact point for the supevisory authority ====
==== (d)(e) Cooperatian with the supervisory 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.<ref>''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).</ref> This contact point function as an obligation for the controller or processor to involve the DPO in any contact with DPAs.<ref>''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).</ref> However, while DPAs can always contact the DPO, contacting other members of  an organisation is also possible.<ref>''Bergt'', in Kühling, Buchner, DS-GVO BDSG, Article 39 GDPR, margin number 18 (C.H. Beck 2020, 3rd Edition).</ref> Finally, although the DPO is bound by confidentiality,  they may still contact and seek advice from the DPA.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 19 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref>
Articles 39(1)(d) and (e) GDPR 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.<ref>''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).</ref> This contact point functions as an obligation for the controller or processor to involve the DPO in any contact with DPAs.<ref>''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).</ref> However, while DPAs can always contact the DPO, contacting other members of  an organisation is also possible.<ref>''Bergt'', in Kühling, Buchner, DS-GVO BDSG, Article 39 GDPR, margin number 18 (C.H. Beck 2020, 3rd Edition).</ref> Finally, although the DPO is bound by confidentiality, they may still contact and seek advice from the DPA.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 19 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref>


=== (2) High Risk Activities ===
=== (2) Risk-based approach ===
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.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 18 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref> 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.  
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 in prioritising certain tasks or in choosing the most adequate DPIA methodology, it does not mean that low-risk areas may ever be neglected. 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.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 18 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref>   
==Decisions==
==Decisions==
→ You can find all related decisions in [[:Category:Article 39 GDPR]]
→ You can find all related decisions in [[:Category:Article 39 GDPR]]

Latest revision as of 15:10, 27 July 2023

Article 39 - Tasks of the data protection officer
Gdpricon.png
Chapter 10: Delegated and implementing acts

Legal Text


Article 39 - Tasks of the data protection officer

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

Recital 77: Guidance on Evaluating Risks
Guidance on the implementation of appropriate measures and on the demonstration of compliance by the controller or the processor, especially as regards the identification of the risk related to the processing, their assessment in terms of origin, nature, likelihood and severity, and the identification of best practices to mitigate the risk, could be provided in particular by means of approved codes of conduct, approved certifications, guidelines provided by the Board or indications provided by a data protection officer. The Board may also issue guidelines on processing operations that are considered to be unlikely to result in a high risk to the rights and freedoms of natural persons and indicate what measures may be sufficient in such cases to address such risk.

Recital 97: Data Protection Officer
Where the processing is carried out by a public authority, except for courts or independent judicial authorities when acting in their judicial capacity, where, in the private sector, processing is carried out by a controller whose core activities consist of processing operations that require regular and systematic monitoring of the data subjects on a large scale, or where the core activities of the controller or the processor consist of processing on a large scale of special categories of personal data and data relating to criminal convictions and offences, a person with expert knowledge of data protection law and practices should assist the controller or processor to monitor internal compliance with this Regulation. In the private sector, the core activities of a controller relate to its primary activities and do not relate to the processing of personal data as ancillary activities. The necessary level of expert knowledge should be determined in particular according to the data processing operations carried out and the protection required for the personal data processed by the controller or the processor. Such data protection officers, whether or not they are an employee of the controller, should be in a position to perform their duties and tasks in an independent manner.

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 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

The first task of the DPO is to inform and advise the controller, processor, and employees about their respective obligations under the GDPR and other applicable data protection laws.

Regarding the scope of the obligation to inform and advise, all Chapter IV of the GDPR, which covers the general obligations of the controller and processor, becomes relevant. Notable elements include technical and organizational measures required to demonstrate compliance (Article 24), the selection of technical capabilities and default settings to ensure compliance with rights and the GDPR from the outset of data processing (Article 25), obligations related to joint controllers and processors (Articles 26 and 28, respectively), maintaining records of processing activities (Article 30), ensuring the security of processing (Article 32), responsibilities of the DPO in case of data breaches (Articles 33 and 34), and preparation of data protection impact assessments and prior consultation (Articles 35 and 36). Additionally, as correctly noted, the obligations of the controller or processor also arise from other chapters of the GDPR (e.g., regarding data subjects' exercise of rights) or from other applicable laws, both at the European level (e.g., the e-Privacy Directive) and the national level (due to various references made by the GDPR).

The obligation to inform covers any legal matters or developments concerning data protection, such as new legislative requirements, innovative judicial interpretations, or technical developments that could change previous risk assessments. This obligation is proactive, meaning that it is up to the DPO to inform the recipient (controller or processor) about such elements. On the other hand, the obligation to advise relates to specific issues arising during data processing operations. In such cases, the DPO clarifies the obligations that arise in a specific situation and provides solutions in line with applicable laws. In practice, the data protection officer's responsibility for informing and advising can be carried out through various approaches.

A practical example could be the issuing a circular to the management, authority, or key personnel within the company or organization, highlighting the latest developments in data protection laws. This circular may also offer the assurance that the data protection officer is available to provide further elaboration and explanation on the raised issues if needed.[3]

(b) Monitor compliance

Article 39(1)(b) assigns DPOs the responsibility to monitor compliance with the GDPR, as further specified in Recital 97, which states that the DPO should assist the controller or processor in monitoring internal compliance with the Regulation. As part of their duty to monitor compliance, DPOs may engage in various activities, such as collecting information to identify processing operations, analyzing and verifying the compliance of such operations, and providing information, advice, and recommendations to the controller or processor. It is essential to note that monitoring compliance does not imply personal responsibility on the part of the DPO in cases of non-compliance. The GDPR explicitly states that the controller, not the DPO, is obligated to implement appropriate technical and organizational measures to ensure and demonstrate that processing aligns with the Regulation (Article 24(1) GDPR). Therefore, data protection compliance is ultimately a corporate responsibility of the data controller and not that of the DPO.[4]

(c) Advise on the DPIA

As per Article 35(1), conducting a data protection impact assessment (DPIA) is the responsibility of the controller, not the DPO, when deemed necessary. Nonetheless, the DPO can still play a valuable role in assisting the controller. In line with the principle of data protection by design, Article 35(2) explicitly states that the controller must "seek advice" from the DPO when undertaking a DPIA. Additionally, Article 39(1)(c) assigns to the DPO the task of providing advice, upon request, concerning the DPIA and monitoring its execution as outlined in Article 35.

WP29: The WP29 recommends that the controller seeks the advice of the DPO on various issues, including whether to conduct a DPIA, the appropriate methodology for the DPIA, whether to perform the DPIA internally or outsource it, what safeguards to apply to address risks to data subjects' rights and interests, and whether the DPIA has been correctly carried out and its conclusions comply with the GDPR.[5]

Moreover, to the data protection officer is also assigned the responsibility to actively monitor the implementation of a DPIA, rather than solely upon request. The data protection officer is required to assess compliance with the requirements outlined in Article 35 and review the content assessments conducted. In doing so, the DPO should have access to the relevant documentation. Subsequently, the DPO should provide a report on the evaluation of the process, forwarding any significant deficiencies to the relevant staff. In cases of severe shortcomings, the report should also be escalated to management or the appropriate authority.[6]

(d)(e) Cooperatian with the supervisory authority

Articles 39(1)(d) and (e) GDPR 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.[7] This contact point functions as an obligation for the controller or processor to involve the DPO in any contact with DPAs.[8] However, while DPAs can always contact the DPO, contacting other members of  an organisation is also possible.[9] Finally, although the DPO is bound by confidentiality, they may still contact and seek advice from the DPA.[10]

(2) Risk-based approach

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 in prioritising certain tasks or in choosing the most adequate DPIA methodology, it does not mean that low-risk areas may ever be neglected. 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.[11]

Decisions

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

References

  1. 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.
  2. Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 39 GDPR, margin number 10 (C.H. Beck 2020, 3rd edition).
  3. Drewes, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 39 GDPR, margin numbers 7-15 (C.H. Beck 2019).
  4. WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available here).
  5. WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 17 (available here). The WP29 also recalls that Article 39(1) mentions the tasks of the DPO and indicates that the DPO shall have ‘at least’ the following tasks. Therefore, nothing prevents the controller from assigning the DPO other tasks than those explicitly mentioned in Article 39(1), or specifying those tasks in more detail.
  6. Drewes, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 39 GDPR, margin numbers 34 (C.H. Beck 2019).
  7. 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).
  8. 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).
  9. Bergt, in Kühling, Buchner, DS-GVO BDSG, Article 39 GDPR, margin number 18 (C.H. Beck 2020, 3rd Edition).
  10. WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 19 (available here).
  11. WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev.01, 5 April 2017, p. 18 (available here).