https://gdprhub.eu/index.php?title=Article_39_GDPR&feed=atom&action=historyArticle 39 GDPR - Revision history2024-03-28T19:39:55ZRevision history for this page on the wikiMediaWiki 1.39.6https://gdprhub.eu/index.php?title=Article_39_GDPR&diff=34285&oldid=prevMg: /* (b) Monitor compliance */2023-07-27T15:10:19Z<p><span dir="auto"><span class="autocomment">(b) Monitor compliance</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 15:10, 27 July 2023</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l221">Line 221:</td>
<td colspan="2" class="diff-lineno">Line 221:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (b) Monitor compliance ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (b) Monitor compliance ====</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Article 39(1)(b) assigns <del style="font-weight: bold; text-decoration: none;">Data Protection Officers (</del>DPOs<del style="font-weight: bold; text-decoration: none;">) with </del>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 <del style="font-weight: bold; text-decoration: none;">activities</del>, analyzing and verifying the compliance of such <del style="font-weight: bold; text-decoration: none;">activities</del>, 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></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">operations</ins>, analyzing and verifying the compliance of such <ins style="font-weight: bold; text-decoration: none;">operations</ins>, 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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (c) Advise on the DPIA ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (c) Advise on the DPIA ====</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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 <del style="font-weight: bold; text-decoration: none;">and crucial </del>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 the DPO <del style="font-weight: bold; text-decoration: none;">with </del>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, 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></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">to </ins>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, <ins style="font-weight: bold; text-decoration: none;">to </ins>the data protection officer is also assigned the responsibility to <ins style="font-weight: bold; text-decoration: none;">''</ins>actively<ins style="font-weight: bold; text-decoration: none;">'' </ins>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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (d)(e) Cooperatian with the supervisory authority ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (d)(e) Cooperatian with the supervisory authority ====</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Articles 39(1)(d) and (e) GDPR <del style="font-weight: bold; text-decoration: none;">and </del>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 <del style="font-weight: bold; text-decoration: none;">function </del>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,<del style="font-weight: bold; text-decoration: none;"> they </del>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></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">functions </ins>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,<ins style="font-weight: bold; text-decoration: none;"> they </ins>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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== (2) Risk-based approach ===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== (2) Risk-based approach ===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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 <del style="font-weight: bold; text-decoration: none;">prioritise their </del>tasks or <del style="font-weight: bold; text-decoration: none;">choose </del>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> </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">in prioritising certain </ins>tasks or <ins style="font-weight: bold; text-decoration: none;">in choosing </ins>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> </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td></tr>
</table>Mghttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=34284&oldid=prevMg: /* Commentary */2023-07-27T14:59:43Z<p><span dir="auto"><span class="autocomment">Commentary</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 14:59, 27 July 2023</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l206">Line 206:</td>
<td colspan="2" class="diff-lineno">Line 206:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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 <del style="font-weight: bold; text-decoration: none;">assigned </del>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. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== (1) DPO's Tasks ===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== (1) DPO's Tasks ===</div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l214">Line 214:</td>
<td colspan="2" class="diff-lineno">Line 214:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Regarding the scope of the obligation to inform and advise, 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 <del style="font-weight: bold; text-decoration: none;">parts </del>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).</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Regarding the scope of the obligation to inform and advise, <ins style="font-weight: bold; text-decoration: none;">all </ins>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 <ins style="font-weight: bold; text-decoration: none;">chapters </ins>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).</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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 the DPO <del style="font-weight: bold; text-decoration: none;">must voluntarily </del>inform the recipient about such elements. On the other hand, the obligation to advise relates to specific <del style="font-weight: bold; text-decoration: none;">problematic </del>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. <del style="font-weight: bold; text-decoration: none;">For instance, one approach involves </del>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></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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 <ins style="font-weight: bold; text-decoration: none;">that it is up to </ins>the DPO <ins style="font-weight: bold; text-decoration: none;">to </ins>inform the recipient <ins style="font-weight: bold; text-decoration: none;">(controller or processor) </ins>about such elements. On the other hand, the obligation to advise relates to specific <ins style="font-weight: bold; text-decoration: none;"> </ins>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. </div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">A practical example could be the </ins>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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (b) Monitor compliance ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (b) Monitor compliance ====</div></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-34249:rev-34284 -->
</table>Mghttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=34249&oldid=prevSR: /* (c) Advise on and monitor over enforcement of the DPIA */2023-07-25T14:32:22Z<p><span dir="auto"><span class="autocomment">(c) Advise on and monitor over enforcement of the DPIA</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 14:32, 25 July 2023</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l221">Line 221:</td>
<td colspan="2" class="diff-lineno">Line 221:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Article 39(1)(b) assigns Data Protection Officers (DPOs) with 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 activities, analyzing and verifying the compliance of such activities, 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></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Article 39(1)(b) assigns Data Protection Officers (DPOs) with 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 activities, analyzing and verifying the compliance of such activities, 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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>==== (c) Advise on <del style="font-weight: bold; text-decoration: none;">and monitor over enforcement of </del>the DPIA ====</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>==== (c) Advise on the DPIA ====</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 and crucial 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 the DPO with 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, 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></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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 and crucial 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 the DPO with 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, 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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-34248:rev-34249 -->
</table>SRhttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=34248&oldid=prevSR: /* Commentary */2023-07-25T14:29:15Z<p><span dir="auto"><span class="autocomment">Commentary</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 14:29, 25 July 2023</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l212">Line 212:</td>
<td colspan="2" class="diff-lineno">Line 212:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (a) Inform and advise ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (a) Inform and advise ====</div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">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.</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Regarding the scope of the obligation to inform and advise, 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 parts 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).</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">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 the DPO must voluntarily inform the recipient about such elements. On the other hand, the obligation to advise relates to specific problematic 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. For instance, one approach involves 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></ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (b) Monitor compliance ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (b) Monitor compliance ====</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Under </del>Article 39(1)(b) as <del style="font-weight: bold; text-decoration: none;">well as </del>Recital 97 <del style="font-weight: bold; text-decoration: none;">GDPR</del>, the DPO should <del style="font-weight: bold; text-decoration: none;">not only inform and advise controllers </del>or <del style="font-weight: bold; text-decoration: none;">processing regarding </del>compliance with <del style="font-weight: bold; text-decoration: none;">data protection laws, but also </del>monitor <del style="font-weight: bold; text-decoration: none;">that </del>compliance<del style="font-weight: bold; text-decoration: none;">. In doing so</del>, <del style="font-weight: bold; text-decoration: none;">according to the Article 29 Working Party (WP29)</del>, <del style="font-weight: bold; text-decoration: none;">the DPO may collect </del>information to identify processing activities, <del style="font-weight: bold; text-decoration: none;">analyse </del>and <del style="font-weight: bold; text-decoration: none;">check </del>the compliance of <del style="font-weight: bold; text-decoration: none;">processing </del>activities, <del style="font-weight: bold; text-decoration: none;">as well as inform</del>, <del style="font-weight: bold; text-decoration: none;">advise </del>and <del style="font-weight: bold; text-decoration: none;">issue </del>recommendations to <del style="font-weight: bold; text-decoration: none;">them</del>.<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></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Article 39(1)(b) <ins style="font-weight: bold; text-decoration: none;">assigns Data Protection Officers (DPOs) with the responsibility to monitor compliance with the GDPR, </ins>as <ins style="font-weight: bold; text-decoration: none;">further specified in </ins>Recital 97, <ins style="font-weight: bold; text-decoration: none;">which states that </ins>the DPO should <ins style="font-weight: bold; text-decoration: none;">assist the controller </ins>or <ins style="font-weight: bold; text-decoration: none;">processor in monitoring internal </ins>compliance with <ins style="font-weight: bold; text-decoration: none;">the Regulation. As part of their duty to </ins>monitor compliance, <ins style="font-weight: bold; text-decoration: none;">DPOs may engage in various activities</ins>, <ins style="font-weight: bold; text-decoration: none;">such as collecting </ins>information to identify processing activities, <ins style="font-weight: bold; text-decoration: none;">analyzing </ins>and <ins style="font-weight: bold; text-decoration: none;">verifying </ins>the compliance of <ins style="font-weight: bold; text-decoration: none;">such </ins>activities, <ins style="font-weight: bold; text-decoration: none;">and providing information, advice</ins>, and recommendations to <ins style="font-weight: bold; text-decoration: none;">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</ins>.<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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (c) Advise on and monitor over enforcement of the DPIA ====</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==== (c) Advise on and monitor over enforcement of the DPIA ====</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Furthermore</del>, the DPO <del style="font-weight: bold; text-decoration: none;">has </del>a <del style="font-weight: bold; text-decoration: none;">central </del>role <del style="font-weight: bold; text-decoration: none;">throughout </del>the <del style="font-weight: bold; text-decoration: none;">Data Protection Impact Assessment </del>(<del style="font-weight: bold; text-decoration: none;">DPIA</del>) <del style="font-weight: bold; text-decoration: none;">process. While ultimately it is </del>the controller <del style="font-weight: bold; text-decoration: none;">or processor’s responsibility to ensure compliance and conduct </del>a DPIA <del style="font-weight: bold; text-decoration: none;">where needed</del>, Article 39(1)(c) <del style="font-weight: bold; text-decoration: none;">requires </del>the DPO <del style="font-weight: bold; text-decoration: none;">to “''provide </del>advice <del style="font-weight: bold; text-decoration: none;">where requested as regards </del>the <del style="font-weight: bold; text-decoration: none;">[</del>DPIA<del style="font-weight: bold; text-decoration: none;">] </del>and <del style="font-weight: bold; text-decoration: none;">monitor </del>its <del style="font-weight: bold; text-decoration: none;">performance pursuant to </del>Article 35.'<del style="font-weight: bold; text-decoration: none;">'”</del><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></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">As per Article 35(1), conducting a data protection impact assessment (DPIA) is the responsibility of the controller</ins>, <ins style="font-weight: bold; text-decoration: none;">not </ins>the DPO<ins style="font-weight: bold; text-decoration: none;">, when deemed necessary. Nonetheless, the DPO can still play </ins>a <ins style="font-weight: bold; text-decoration: none;">valuable and crucial </ins>role <ins style="font-weight: bold; text-decoration: none;">in assisting </ins>the <ins style="font-weight: bold; text-decoration: none;">controller. In line with the principle of data protection by design, Article 35</ins>(<ins style="font-weight: bold; text-decoration: none;">2</ins>) <ins style="font-weight: bold; text-decoration: none;">explicitly states that </ins>the controller <ins style="font-weight: bold; text-decoration: none;">must "seek advice" from the DPO when undertaking </ins>a DPIA<ins style="font-weight: bold; text-decoration: none;">. Additionally</ins>, Article 39(1)(c) <ins style="font-weight: bold; text-decoration: none;">assigns </ins>the DPO <ins style="font-weight: bold; text-decoration: none;">with the task of providing </ins>advice<ins style="font-weight: bold; text-decoration: none;">, upon request, concerning </ins>the DPIA and <ins style="font-weight: bold; text-decoration: none;">monitoring </ins>its <ins style="font-weight: bold; text-decoration: none;">execution as outlined in </ins>Article 35.<ins style="font-weight: bold; text-decoration: none;"><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</ins>' <ins style="font-weight: bold; text-decoration: none;">rights and interests, and whether the DPIA has been correctly carried out and its conclusions comply with the GDPR.</ins><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])<ins style="font-weight: bold; text-decoration: none;">. 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</ins>.</ref><ins style="font-weight: bold; text-decoration: none;"></blockquote>Moreover, 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 </ins>with the <ins style="font-weight: bold; text-decoration: none;">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 </ins>authority<ins style="font-weight: bold; text-decoration: none;">.<ref>''Drewes'', in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 39 GDPR, margin numbers 34 (C.H. Beck 2019). </ref></ins></div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">==== (d) Cooperate </del>with the <del style="font-weight: bold; text-decoration: none;">supervisory </del>authority <del style="font-weight: bold; text-decoration: none;">====</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>==== (e) <del style="font-weight: bold; text-decoration: none;">Contact point for </del>the <del style="font-weight: bold; text-decoration: none;">supevisory </del>authority ====</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>==== <ins style="font-weight: bold; text-decoration: none;">(d)</ins>(e) <ins style="font-weight: bold; text-decoration: none;">Cooperatian with </ins>the <ins style="font-weight: bold; text-decoration: none;">supervisory </ins>authority ====</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>=== (2) <del style="font-weight: bold; text-decoration: none;">High </del>Risk <del style="font-weight: bold; text-decoration: none;">Activities </del>===</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>=== (2) Risk<ins style="font-weight: bold; text-decoration: none;">-based approach </ins>===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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> <del style="font-weight: bold; text-decoration: none;">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. </del> </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>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<ins style="font-weight: bold; text-decoration: none;">. 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</ins>.<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> </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-34231:rev-34248 -->
</table>SRhttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=34231&oldid=prevSR: /* Commentary */2023-07-25T13:23:02Z<p><span dir="auto"><span class="autocomment">Commentary</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 13:23, 25 July 2023</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l206">Line 206:</td>
<td colspan="2" class="diff-lineno">Line 206:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>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.''” </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Article 39, titled "''Tasks of the data protection officer''", outlines the primary responsibilities of the Data Protection Officer (DPO).<ref></ins>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.''”<ins style="font-weight: bold; text-decoration: none;"></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. </ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== (1) DPO's Tasks ===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== (1) DPO's Tasks ===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Under Articles 39(</del>1<del style="font-weight: bold; text-decoration: none;">)(</del>a<del style="font-weight: bold; text-decoration: none;">) </del>and <del style="font-weight: bold; text-decoration: none;">(b) as well as Recital 97 GDPR</del>, the DPO <del style="font-weight: bold; text-decoration: none;">should not only inform and advise controllers or processing regarding compliance with data protection laws</del>, <del style="font-weight: bold; text-decoration: none;">but also monitor that compliance</del>. <del style="font-weight: bold; text-decoration: none;">In doing so</del>, <del style="font-weight: bold; text-decoration: none;">according to </del>the Article <del style="font-weight: bold; text-decoration: none;">29 Working Party </del>(<del style="font-weight: bold; text-decoration: none;">WP29</del>),the DPO <del style="font-weight: bold; text-decoration: none;">may collect information </del>to <del style="font-weight: bold; text-decoration: none;">identify processing activities, analyse and check </del>the <del style="font-weight: bold; text-decoration: none;">compliance of processing activities, as well as inform, advise </del>and <del style="font-weight: bold; text-decoration: none;">issue recommendations </del>to <del style="font-weight: bold; text-decoration: none;">them</del>.<ref><del style="font-weight: bold; text-decoration: none;">WP29</del>, <del style="font-weight: bold; text-decoration: none;">‘Guidelines on Data Protection Officers (‘DPO’s)’</del>, <del style="font-weight: bold; text-decoration: none;">16/EN WP 243 rev.01</del>, <del style="font-weight: bold; text-decoration: none;">5 April 2017</del>, <del style="font-weight: bold; text-decoration: none;">p. 17 </del>(<del style="font-weight: bold; text-decoration: none;">available [https://ec</del>.<del style="font-weight: bold; text-decoration: none;">europa</del>.<del style="font-weight: bold; text-decoration: none;">eu/newsroom/just/document.cfm?doc_id=44100 here]</del>).</ref> </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Paragraph </ins>1 <ins style="font-weight: bold; text-decoration: none;">provides </ins>a <ins style="font-weight: bold; text-decoration: none;">comprehensive list of tasks that the DPO must perform according to the GDPR, </ins>and <ins style="font-weight: bold; text-decoration: none;">these tasks cannot be restricted by national regulations. However</ins>, <ins style="font-weight: bold; text-decoration: none;">the use of the phrase "''at least''" implies that additional functions or duties may be assigned to </ins>the DPO, <ins style="font-weight: bold; text-decoration: none;">such as conducting training for the controller's employees</ins>. <ins style="font-weight: bold; text-decoration: none;">To include such additional functions</ins>, <ins style="font-weight: bold; text-decoration: none;">they must be explicitly specified in </ins>the <ins style="font-weight: bold; text-decoration: none;">appointment document or in relevant updates. In accordance with </ins>Article <ins style="font-weight: bold; text-decoration: none;">38</ins>(<ins style="font-weight: bold; text-decoration: none;">2</ins>) <ins style="font-weight: bold; text-decoration: none;">of the GDPR</ins>, the DPO <ins style="font-weight: bold; text-decoration: none;">must receive all necessary resources </ins>to <ins style="font-weight: bold; text-decoration: none;">fulfill these supplementary tasks effectively. This ensures that </ins>the <ins style="font-weight: bold; text-decoration: none;">DPO is adequately equipped </ins>and <ins style="font-weight: bold; text-decoration: none;">supported </ins>to <ins style="font-weight: bold; text-decoration: none;">carry out their responsibilities in a comprehensive and efficient manner</ins>.<ref><ins style="font-weight: bold; text-decoration: none;">''Bergt'', in Kühling</ins>, <ins style="font-weight: bold; text-decoration: none;">Buchner</ins>, <ins style="font-weight: bold; text-decoration: none;">DS-GVO BDSG</ins>, <ins style="font-weight: bold; text-decoration: none;">Article 39 GDPR</ins>, <ins style="font-weight: bold; text-decoration: none;">margin number 10 </ins>(<ins style="font-weight: bold; text-decoration: none;">C</ins>.<ins style="font-weight: bold; text-decoration: none;">H</ins>. <ins style="font-weight: bold; text-decoration: none;">Beck 2020, 3rd edition</ins>).</ref></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">==== (a) Inform and advise ====</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">==== (b) Monitor compliance ====</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">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></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">==== (c) Advise on and monitor over enforcement of the DPIA ====</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">==== (d) Cooperate with the supervisory authority ====</ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">==== (e) Contact point for the supevisory authority ====</ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>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></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-25607:rev-34231 -->
</table>SRhttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=25607&oldid=prevSR: /* Overview */2022-04-28T11:31:13Z<p><span dir="auto"><span class="autocomment">Overview</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 11:31, 28 April 2022</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l206">Line 206:</td>
<td colspan="2" class="diff-lineno">Line 206:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td></tr>
<tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">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.''” </ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>=== <del style="font-weight: bold; text-decoration: none;">Overview </del>===</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>=== <ins style="font-weight: bold; text-decoration: none;">(1) DPO's Tasks </ins>===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Same </del>as <del style="font-weight: bold; text-decoration: none;">[[Article 38 </del>GDPR<del style="font-weight: bold; text-decoration: none;">]]</del>, <del style="font-weight: bold; text-decoration: none;">Article 39 GDPR shows similarities </del>with <del style="font-weight: bold; text-decoration: none;">[https://eur-lex</del>.<del style="font-weight: bold; text-decoration: none;">europa.eu/legal-content/en/TXT/?uri=CELEX:32001R0045 Regulation 45/2001]</del>, <del style="font-weight: bold; text-decoration: none;">which mandated each </del>of <del style="font-weight: bold; text-decoration: none;">the European Union institutions</del>, <del style="font-weight: bold; text-decoration: none;">bodies</del>, and <del style="font-weight: bold; text-decoration: none;">agencies </del>to <del style="font-weight: bold; text-decoration: none;">appoint a data protection officer</del>. <del style="font-weight: bold; text-decoration: none;">The roots of Article 39 GDPR can be partially retraced to the GDPR’s predecessor</del>, <del style="font-weight: bold; text-decoration: none;">the </del>[https://<del style="font-weight: bold; text-decoration: none;">eur-lex</del>.europa.eu/<del style="font-weight: bold; text-decoration: none;">legal-content</del>/<del style="font-weight: bold; text-decoration: none;">EN/TXT</del>/?<del style="font-weight: bold; text-decoration: none;">uri</del>=<del style="font-weight: bold; text-decoration: none;">celex:31995L0046 Directive 95/46/EC</del>]<del style="font-weight: bold; text-decoration: none;">. In particular, Article 18 of the Directive mentioned the role of ‘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</del>) <del style="font-weight: bold; text-decoration: none;">“for ensuring in an independent manner the internal application” of the national data protection laws; and (ii) “for keeping an internal register of processing operations carried out by the controller</del>.<del style="font-weight: bold; text-decoration: none;">” </del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Under Articles 39(1)(a) and (b) </ins>as <ins style="font-weight: bold; text-decoration: none;">well as Recital 97 </ins>GDPR, <ins style="font-weight: bold; text-decoration: none;">the DPO should not only inform and advise controllers or processing regarding compliance </ins>with <ins style="font-weight: bold; text-decoration: none;">data protection laws, but also monitor that compliance</ins>. <ins style="font-weight: bold; text-decoration: none;">In doing so, according to the Article 29 Working Party (WP29),the DPO may collect information to identify processing activities</ins>, <ins style="font-weight: bold; text-decoration: none;">analyse and check the compliance </ins>of <ins style="font-weight: bold; text-decoration: none;">processing activities</ins>, <ins style="font-weight: bold; text-decoration: none;">as well as inform</ins>, <ins style="font-weight: bold; text-decoration: none;">advise </ins>and <ins style="font-weight: bold; text-decoration: none;">issue recommendations </ins>to <ins style="font-weight: bold; text-decoration: none;">them.<ref>WP29, ‘Guidelines on Data Protection Officers (‘DPO’s)’, 16/EN WP 243 rev</ins>.<ins style="font-weight: bold; text-decoration: none;">01, 5 April 2017</ins>, <ins style="font-weight: bold; text-decoration: none;">p. 17 (available </ins>[https://<ins style="font-weight: bold; text-decoration: none;">ec</ins>.europa.eu/<ins style="font-weight: bold; text-decoration: none;">newsroom</ins>/<ins style="font-weight: bold; text-decoration: none;">just</ins>/<ins style="font-weight: bold; text-decoration: none;">document.cfm</ins>?<ins style="font-weight: bold; text-decoration: none;">doc_id</ins>=<ins style="font-weight: bold; text-decoration: none;">44100 here</ins>]).<ins style="font-weight: bold; text-decoration: none;"></ref> </ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">=== Monitoring Compliance ===</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Furthermore, the DPO has a central role throughout the Data Protection Impact Assessment (DPIA) process. While ultimately it is </ins>the <ins style="font-weight: bold; text-decoration: none;">controller </ins>or <ins style="font-weight: bold; text-decoration: none;">processor’s responsibility to ensure </ins>compliance <ins style="font-weight: bold; text-decoration: none;">and conduct a DPIA where needed</ins>, Article 39(1)(<ins style="font-weight: bold; text-decoration: none;">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</ins>)<ins style="font-weight: bold; text-decoration: none;">’</ins>, <ins style="font-weight: bold; text-decoration: none;">16/EN WP 243 rev.01, 5 April 2017, p. 17 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here])</ins>.</ref></div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">In assisting </del>the <del style="font-weight: bold; text-decoration: none;">processor </del>or <del style="font-weight: bold; text-decoration: none;">controller with ensuring </del>compliance,<del style="font-weight: bold; text-decoration: none;"><ref></del>Article 39(1)(<del style="font-weight: bold; text-decoration: none;">b</del>) <del style="font-weight: bold; text-decoration: none;">GDPR</del>, <del style="font-weight: bold; text-decoration: none;">Recital 97 GDPR</del>.</ref> <del style="font-weight: bold; text-decoration: none;">the DPO may, in particular:</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">· </del> <del style="font-weight: bold; text-decoration: none;"> collect information to identify processing activities</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">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,</ins> <ins style="font-weight: bold; text-decoration: none;">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></ins></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">· analyse and check the compliance of processing activities</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>=<ins style="font-weight: bold; text-decoration: none;">== </ins>(<ins style="font-weight: bold; text-decoration: none;">2</ins>) High Risk Activities ===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>According to Article 39(2) GDPR, the DPO must <ins style="font-weight: bold; text-decoration: none;">“''have </ins>due regard to the risk associated with the processing operations, taking into account the nature, scope, context and purposes of processing.<ins style="font-weight: bold; text-decoration: none;">''</ins>” 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, <ins style="font-weight: bold; text-decoration: none;">‘Guidelines </ins>on Data Protection Officers (<ins style="font-weight: bold; text-decoration: none;">‘DPO’s</ins>)<ins style="font-weight: bold; text-decoration: none;">’</ins>, <ins style="font-weight: bold; text-decoration: none;">16/EN </ins>WP 243 rev.01, 5 April 2017, p. 18 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref> <ins style="font-weight: bold; text-decoration: none;">A </ins>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. <ins style="font-weight: bold; text-decoration: none;"> </ins></div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">· inform, advise and issue recommendations to the controller or the processor<ref>WP29, Guidelines on Data Protection Officers (“DPOs”)”, WP 243 rev.01, 5 April 2017, p. 17 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id</del>=<del style="font-weight: bold; text-decoration: none;">44100 here]).</ref></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Furthermore, the DPO has a central role throughout the DPIA process.<ref>Article 39</del>(<del style="font-weight: bold; text-decoration: none;">1)(c</del>) <del style="font-weight: bold; text-decoration: none;">GDPR.</ref> While it is the controller or processor’s responsibility to ensure compliance and conduct a DPIA where needed, the DPO has a duty to “provide advice where requested as regards the [DPIA] and monitor its performance pursuant to Article 35.”<ref>Article 39(1)(c) GDPR; WP29, Guidelines on Data Protection Officers (“DPOs”)”, WP 243 rev.01, 5 April 2017, p. 17 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">=== </del>High Risk Activities ===</div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>According to Article 39(2) GDPR, the DPO must <del style="font-weight: bold; text-decoration: none;">“have </del>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, <del style="font-weight: bold; text-decoration: none;">Guidelines </del>on Data Protection Officers (<del style="font-weight: bold; text-decoration: none;">“DPOs”</del>)<del style="font-weight: bold; text-decoration: none;">”</del>, WP 243 rev.01, 5 April 2017, p. 18 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref> <del style="font-weight: bold; text-decoration: none;">Indeed, the </del>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. </div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">=== DPOs and Supervisory Authorities ===</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Articles 39(1)(d)(e) GDPR and lay down the DPO’s obligations in relation to the supervisory authorities. For example, the DPO could facilitate cooperation of the organisation in prior consultation procedures or DPA investigations.<ref>''Alvarez Rigaudias'', ''Spina'', in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 39 GDPR, p. 714 (Oxford University Press 2020).</ref> Furthermore, some commentators read this contact point function as an obligation for the organisation to involve the DPO in any contact with supervisory authorities.<ref>''Alvarez Rigaudias'', ''Spina'', in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 39 GDPR, p. 714 (Oxford University Press 2020).</ref> However, while DPAs can always contact the DPO, contacting other members of the organisation is also possible.<ref>''Bergt'', in Kühling, Buchner, DS-GVO BDSG, Article 39 GDPR, margin number 18 (C.H. Beck 2020).</ref> Finally, although the DPO is bound by confidentiality, he or she may still contact and seek advice from the DPA.<ref>WP29, Guidelines on Data Protection Officers (“DPOs”)”, WP 243 rev.01, 5 April 2017, p. 18 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-24249:rev-25607 -->
</table>SRhttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=24249&oldid=prevGb: style consistency2022-03-08T10:24:49Z<p>style consistency</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 10:24, 8 March 2022</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l185">Line 185:</td>
<td colspan="2" class="diff-lineno">Line 185:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Legal Text==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Legal Text==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><br /><center>'''Article 39 - Tasks of the data protection officer'''</center<del style="font-weight: bold; text-decoration: none;">><br /</del>></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><br /><center>'''Article 39 - Tasks of the data protection officer'''</center></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><span id="1">1. The data protection officer shall have at least the following tasks:</span></div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div><span id="1">1. The data protection officer shall have at least the following tasks:</span></div></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-19391:rev-24249 -->
</table>Gbhttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=19391&oldid=prevFD at 09:48, 10 September 20212021-09-10T09:48:27Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 09:48, 10 September 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l208">Line 208:</td>
<td colspan="2" class="diff-lineno">Line 208:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== Overview ===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== Overview ===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Same as [[Article 38 GDPR]], Article 39 GDPR shows similarities with [https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX:32001R0045 Regulation 45/2001], which mandated each of the European Union institutions, bodies, and agencies to appoint a data protection officer. The roots of Article 39 GDPR can be partially retraced to the GDPR’s predecessor, the [<del style="font-weight: bold; text-decoration: none;">[</del>Directive 95/46/EC<del style="font-weight: bold; text-decoration: none;">]</del>]. In particular, Article 18 of the Directive mentioned the role of ‘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 the national data protection laws; and (ii) “for keeping an internal register of processing operations carried out by the controller.” </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Same as [[Article 38 GDPR]], Article 39 GDPR shows similarities with [https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX:32001R0045 Regulation 45/2001], which mandated each of the European Union institutions, bodies, and agencies to appoint a data protection officer. The roots of Article 39 GDPR can be partially retraced to the GDPR’s predecessor, the [<ins style="font-weight: bold; text-decoration: none;">https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex:31995L0046 </ins>Directive 95/46/EC]. In particular, Article 18 of the Directive mentioned the role of ‘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 the national data protection laws; and (ii) “for keeping an internal register of processing operations carried out by the controller.” </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== Monitoring Compliance ===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== Monitoring Compliance ===</div></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-18688:rev-19391 -->
</table>FDhttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=18688&oldid=prevJS at 13:27, 24 August 20212021-08-24T13:27:49Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 13:27, 24 August 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l202">Line 202:</td>
<td colspan="2" class="diff-lineno">Line 202:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Relevant Recitals==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Relevant Recitals==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"><span id="r77"></del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">{{</ins>Recital<ins style="font-weight: bold; text-decoration: none;">/</ins>77 <ins style="font-weight: bold; text-decoration: none;">GDPR}}</ins></div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"><div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"><div>'''</del>Recital 77<del style="font-weight: bold; text-decoration: none;">''' </div></del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">{{Recital</ins>/97 <ins style="font-weight: bold; text-decoration: none;">GDPR}}</ins></div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"><div class="mw-collapsible-content"></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">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.</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"></div><</del>/<del style="font-weight: bold; text-decoration: none;">div></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div> </div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"><span id="r97"></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"><div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;"><div>'''Recital </del>97<del style="font-weight: bold; text-decoration: none;">''' </div></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"><div class="mw-collapsible-content"></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">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.</del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"></div></div></del></div></td><td colspan="2" class="diff-side-added"></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Commentary==</div></td></tr>
<!-- diff cache key gdprwiki:diff::1.12:old-18486:rev-18688 -->
</table>JShttps://gdprhub.eu/index.php?title=Article_39_GDPR&diff=18486&oldid=prevJS at 10:39, 19 August 20212021-08-19T10:39:10Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 10:39, 19 August 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l234">Line 234:</td>
<td colspan="2" class="diff-lineno">Line 234:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== DPOs and Supervisory Authorities ===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== DPOs and Supervisory Authorities ===</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Articles 39(1)(d)(e) GDPR and lay down the DPO’s obligations in relation to the supervisory authorities. For example, the DPO could facilitate cooperation of the organisation in prior consultation procedures or DPA investigations.<ref>''Alvarez Rigaudias'', ''Spina'', in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 39 GDPR, p. 714 (Oxford University Press 2020).</ref> Furthermore, some commentators read this contact point function as an obligation for the organisation to involve the DPO in any contact with supervisory authorities.<ref>''Alvarez Rigaudias'', ''Spina'', in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 39 GDPR, p. 714 (Oxford University Press 2020).</ref> However, while DPAs can always contact the DPO, contacting other members of the organisation is also possible.<ref>''Bergt'', in Kühling, Buchner, DS-GVO BDSG, <del style="font-weight: bold; text-decoration: none;">Art. </del>39 GDPR, margin number 18 (C.H. Beck 2020).</ref> Finally, although the DPO is bound by confidentiality, he or she may still contact and seek advice from the DPA.<ref>WP29, Guidelines on Data Protection Officers (“DPOs”)”, WP 243 rev.01, 5 April 2017, p. 18 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Articles 39(1)(d)(e) GDPR and lay down the DPO’s obligations in relation to the supervisory authorities. For example, the DPO could facilitate cooperation of the organisation in prior consultation procedures or DPA investigations.<ref>''Alvarez Rigaudias'', ''Spina'', in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 39 GDPR, p. 714 (Oxford University Press 2020).</ref> Furthermore, some commentators read this contact point function as an obligation for the organisation to involve the DPO in any contact with supervisory authorities.<ref>''Alvarez Rigaudias'', ''Spina'', in Kuner et al., The EU General Data Protection Regulation (GDPR), Article 39 GDPR, p. 714 (Oxford University Press 2020).</ref> However, while DPAs can always contact the DPO, contacting other members of the organisation is also possible.<ref>''Bergt'', in Kühling, Buchner, DS-GVO BDSG, <ins style="font-weight: bold; text-decoration: none;">Article </ins>39 GDPR, margin number 18 (C.H. Beck 2020).</ref> Finally, although the DPO is bound by confidentiality, he or she may still contact and seek advice from the DPA.<ref>WP29, Guidelines on Data Protection Officers (“DPOs”)”, WP 243 rev.01, 5 April 2017, p. 18 (available [https://ec.europa.eu/newsroom/just/document.cfm?doc_id=44100 here]).</ref></div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Decisions==</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>→ You can find all related decisions in [[:Category:Article 39 GDPR]]</div></td></tr>
</table>JS