Bodobalazs: 1 revision imported: GDPRHUB import 2023 04 18

2023-04-18T15:01:36Z

1 revision imported: GDPRHUB import 2023 04 18

New page

{| class="wikitable" style="width: 25%; margin-left: 10px; float:right;"
![[Article 35 GDPR|←]] Article 36 - Prior consultation [[Article 37 GDPR|→]]
|-
| style="padding: 20px; background-color:#003399;" |[[File:Gdpricon.png|100px|center|link=Overview_of_GDPR]]
|-
|

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 1: General provisions</div>
<div class="mw-collapsible-content">
<small>
[[Article 1 GDPR|Article 1: Subject-matter and objectives]]<br />
[[Article 2 GDPR|Article 2: Material scope]]<br />
[[Article 3 GDPR|Article 3: Territorial scope]]<br />
[[Article 4 GDPR|Article 4: Definitions]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 2: Principles</div>
<div class="mw-collapsible-content">
<small>
[[Article 5 GDPR|Article 5: Principles relating to processing of personal data]]<br />
[[Article 6 GDPR|Article 6: Lawfulness of processing]]<br />
[[Article 7 GDPR|Article 7: Conditions for consent]]<br />
[[Article 8 GDPR|Article 8: Conditions applicable to child’s consent in relation to information society services]]<br />
[[Article 9 GDPR|Article 9: Processing of special categories of personal data]]<br />
[[Article 10 GDPR|Article 10: Processing of personal data relating to criminal convictions and offences]]<br />
[[Article 11 GDPR|Article 11: Processing which does not require identification]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 3: Rights of the data subject</div>
<div class="mw-collapsible-content">
<small>
[[Article 12 GDPR|Article 12: Transparent information, communication and modalities for the exercise of the rights of the data subject]]<br />
[[Article 13 GDPR|Article 13: Information to be provided where personal data are collected from the data subject]]<br />
[[Article 14 GDPR|Article 14: Information to be provided where personal data have not been obtained from the data subject]]<br />
[[Article 15 GDPR|Article 15: Right of access by the data subject]]<br />
[[Article 16 GDPR|Article 16: Right to rectification]]<br />
[[Article 17 GDPR|Article 17: Right to erasure (‘right to be forgotten’)]]<br />
[[Article 18 GDPR|Article 18: Right to restriction of processing]]<br />
[[Article 19 GDPR|Article 19: Notification obligation regarding rectification or erasure of personal data or restriction of processing]]<br />
[[Article 20 GDPR|Article 20: Right to data portability]]<br />
[[Article 21 GDPR|Article 21: Right to object]]<br />
[[Article 22 GDPR|Article 22: Automated individual decision-making, including profiling]]<br />
[[Article 23 GDPR|Article 23: Restrictions]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 4: Controller and processor</div>
<div class="mw-collapsible-content">
<small>
[[Article 24 GDPR|Article 24: Responsibility of the controller]]<br />
[[Article 25 GDPR|Article 25: Data protection by design and by default]]<br />
[[Article 26 GDPR|Article 26: Joint controllers]]<br />
[[Article 27 GDPR|Article 27: Representatives of controllers or processors not established in the Union]]<br />
[[Article 28 GDPR|Article 28: Processor]]<br />
[[Article 29 GDPR|Article 29: Processing under the authority of the controller or processor]]<br />
[[Article 30 GDPR|Article 30: Records of processing activities]]<br />
[[Article 31 GDPR|Article 31: Cooperation with the supervisory authority]]<br />
[[Article 32 GDPR|Article 32: Security of processing]]<br />
[[Article 33 GDPR|Article 33: Notification of a personal data breach to the supervisory authority]]<br />
[[Article 34 GDPR|Article 34: Communication of a personal data breach to the data subject]]<br />
[[Article 35 GDPR|Article 35: Data protection impact assessment]]<br />
[[Article 36 GDPR|Article 36: Prior consultation]]<br />
[[Article 37 GDPR|Article 37: Designation of the data protection officer]]<br />
[[Article 38 GDPR|Article 38: Position of the data protection officer]]<br />
[[Article 39 GDPR|Article 39: Tasks of the data protection officer]]<br />
[[Article 40 GDPR|Article 40: Codes of conduct]]<br />
[[Article 41 GDPR|Article 41: Monitoring of approved codes of conduct]]<br />
[[Article 42 GDPR|Article 42: Certification]]<br />
[[Article 43 GDPR|Article 43: Certification bodies]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 5: Transfers of personal data</div>
<div class="mw-collapsible-content">
<small>
[[Article 44 GDPR|Article 44: General principle for transfers]]<br />
[[Article 45 GDPR|Article 45: Transfers on the basis of an adequacy decision]]<br />
[[Article 46 GDPR|Article 46: Transfers subject to appropriate safeguards]]<br />
[[Article 47 GDPR|Article 47: Binding corporate rules]]<br />
[[Article 48 GDPR|Article 48: Transfers or disclosures not authorised by Union law]]<br />
[[Article 49 GDPR|Article 49: Derogations for specific situations]]<br />
[[Article 50 GDPR|Article 50: International cooperation for the protection of personal data]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 6: Supervisory authorities</div>
<div class="mw-collapsible-content">
<small>
[[Article 51 GDPR|Article 51: Supervisory authority]]<br />
[[Article 52 GDPR|Article 52: Independence]]<br />
[[Article 53 GDPR|Article 53: General conditions for the members of the supervisory authority]]<br />
[[Article 54 GDPR|Article 54: Rules on the establishment of the supervisory authority]]<br />
[[Article 55 GDPR|Article 55: Competence]]<br />
[[Article 56 GDPR|Article 56: Competence of the lead supervisory authority]]<br />
[[Article 57 GDPR|Article 57: Tasks]]<br />
[[Article 58 GDPR|Article 58: Powers]]<br />
[[Article 59 GDPR|Article 59: Activity reports]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 7: Cooperation and consistency</div>
<div class="mw-collapsible-content">
<small>
[[Article 60 GDPR|Article 60: Cooperation between the lead supervisory authority and the other supervisory authorities concerned]]<br />
[[Article 61 GDPR|Article 61: Mutual assistance]]<br />
[[Article 62 GDPR|Article 62: Joint operations of supervisory authorities]]<br />
[[Article 63 GDPR|Article 63: Consistency mechanism]]<br />
[[Article 64 GDPR|Article 64: Opinion of the Board]]<br />
[[Article 65 GDPR|Article 65: Dispute resolution by the Board]]<br />
[[Article 66 GDPR|Article 66: Urgency procedure]]<br />
[[Article 67 GDPR|Article 67: Exchange of information]]<br />
[[Article 68 GDPR|Article 68: European Data Protection Board]]<br />
[[Article 69 GDPR|Article 69: Independence]]<br />
[[Article 70 GDPR|Article 70: Tasks of the Board]]<br />
[[Article 71 GDPR|Article 71: Reports]]<br />
[[Article 72 GDPR|Article 72: Procedure]]<br />
[[Article 73 GDPR|Article 73: Chair]]<br />
[[Article 74 GDPR|Article 74: Tasks of the Chair]]<br />
[[Article 75 GDPR|Article 75: Secretariat]]<br />
[[Article 76 GDPR|Article 76: Confidentiality]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 8: Remedies, liability and penalties</div>
<div class="mw-collapsible-content">
<small>
[[Article 77 GDPR|Article 77: Right to lodge a complaint with a supervisory authority]]<br />
[[Article 78 GDPR|Article 78: Right to an effective judicial remedy against a supervisory authority]]<br />
[[Article 79 GDPR|Article 79: Right to an effective judicial remedy against a controller or processor]]<br />
[[Article 80 GDPR|Article 80: Representation of data subjects]]<br />
[[Article 81 GDPR|Article 81: Suspension of proceedings]]<br />
[[Article 82 GDPR|Article 82: Right to compensation and liability]]<br />
[[Article 83 GDPR|Article 83: General conditions for imposing administrative fines]]<br />
[[Article 84 GDPR|Article 84: Penalties]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 9: Specific processing situations</div>
<div class="mw-collapsible-content">
<small>
[[Article 85 GDPR|Article 85: Processing and freedom of expression and information]]<br />
[[Article 86 GDPR|Article 86: Processing and public access to official documents]]<br />
[[Article 87 GDPR|Article 87: Processing of the national identification number]]<br />
[[Article 88 GDPR|Article 88: Processing in the context of employment]]<br />
[[Article 89 GDPR|Article 89: Safeguards and derogations relating to processing for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes]]<br />
[[Article 90 GDPR|Article 90: Obligations of secrecy]]<br />
[[Article 91 GDPR|Article 91: Existing data protection rules of churches and religious associations]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 10: Delegated and implementing acts</div>
<div class="mw-collapsible-content">
<small>
[[Article 92 GDPR|Article 92: Exercise of the delegation]]<br />
[[Article 93 GDPR|Article 93: Committee procedure]]<br />
</small>
</div></div>

<div class="toccolours mw-collapsible mw-collapsed" style="border-width: 0px" overflow:auto;">
<div style="font-weight:bold;line-height:1.6;">Chapter 11: Final provisions</div>
<div class="mw-collapsible-content">
<small>
[[Article 94 GDPR|Article 94: Repeal of Directive 95: /46: /EC]]<br />
[[Article 95 GDPR|Article 95: Relationship with Directive 20: 02: /58: /EC]]<br />
[[Article 96 GDPR|Article 96: Relationship with previously concluded Agreements]]<br />
[[Article 97 GDPR|Article 97: Commission reports]]<br />
[[Article 98 GDPR|Article 98: Review of other Union legal acts on data protection]]<br />
[[Article 99 GDPR|Article 99: Entry into force and application]]<br />
</small>
</div>
</div>
|}

==Legal Text==
<br /><center>'''Article 36 - Prior consultation'''</center>

<span id="1">1. The controller shall consult the supervisory authority prior to processing where a data protection impact assessment under Article 35 indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk.</span>

<span id="2">2. Where the supervisory authority is of the opinion that the intended processing referred to in paragraph 1 would infringe this Regulation, in particular where the controller has insufficiently identified or mitigated the risk, the supervisory authority shall, within period of up to eight weeks of receipt of the request for consultation, provide written advice to the controller and, where applicable to the processor, and may use any of its powers referred to in Article 58. That period may be extended by six weeks, taking into account the complexity of the intended processing. The supervisory authority shall inform the controller and, where applicable, the processor, of any such extension within one month of receipt of the request for consultation together with the reasons for the delay. Those periods may be suspended until the supervisory authority has obtained information it has requested for the purposes of the consultation.</span>

<span id="3">3. When consulting the supervisory authority pursuant to paragraph 1, the controller shall provide the supervisory authority with:</span>

::<span id="3a">(a) where applicable, the respective responsibilities of the controller, joint controllers and processors involved in the processing, in particular for processing within a group of undertakings;</span>

::<span id="3b">(b) the purposes and means of the intended processing;</span>

::<span id="3c">(c) the measures and safeguards provided to protect the rights and freedoms of data subjects pursuant to this Regulation;</span>

::<span id="3d">(d) where applicable, the contact details of the data protection officer;</span>

::<span id="3e">(e) the data protection impact assessment provided for in Article 35; and</span>

::<span id="3f">(f) any other information requested by the supervisory authority.</span>

<span id="4">4. Member States shall consult the supervisory authority during the preparation of a proposal for a legislative measure to be adopted by a national parliament, or of a regulatory measure based on such a legislative measure, which relates to processing.</span>

<span id="5">5. Notwithstanding paragraph 1, Member State law may require controllers to consult with, and obtain prior authorisation from, the supervisory authority in relation to processing by a controller for the performance of a task carried out by the controller in the public interest, including processing in relation to social protection and public health.</span>

==Relevant Recitals==
{{Recital/84 GDPR}}
{{Recital/89 GDPR}}
{{Recital/94 GDPR}}
{{Recital/95 GDPR}}
{{Recital/96 GDPR}}

==Commentary==
Directive 95/46/EC (the DPD) imposed a general obligation to notify the Data Protection Authority (DPA) of an operation which processed personal data. The rationale behind the provision was that the DPAs would conduct an assessment prior to the start of the processing operation and thereby manage the potentially high risks of certain operations. However, this general notification obligation did not always lead to a higher level of protection of personal data, and instead produced significant administrative and financial burdens.<ref>Recital 89 GDPR.</ref> For these reasons, Article 36 GDPR restricts the notification obligation only to those processing operations which, following the Data Protection Impact Assessment (DPIA) referred to in [[Article 35 GDPR]], continue to present high risks for the data subject after the risk mitigation measures that the controller has considered are reasonable are applied. Article 36 GDPR must therefore be read as one element within a wider framework of obligations in line with the accountability principle under [[Article 24 GDPR|Articles 5(2) and 24 GDPR]], and especially closely connected to [[Article 35 GDPR|Article 35 GDPR.]]<ref>''Alvarez Rigaudias, Spina'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 36 GDPR, p. 682 (Oxford University Press 2020) and ''Jandt'', in Kühling, Buchner, DS-GVO BDSG, Article 36 GDPR, margin number 1 (C.H. Beck 2020, 3rd Edition).</ref>

=== (1) Conditions Triggering the Prior Consultation ===
Article 36(1) GDPR establishes an obligation for the controller<ref>The obligation of prior consultation applies only to the controller or joint controllers according to the allocation of competences made in the joint controllership agreement referred to in Article 26 GDPR.</ref> to consult the DPA if the DPIA “''indicates that the processing would result in a high risk would result in a high risk in the absence of measures taken by the controller to mitigate the risk.''”

The wording here is clearly problematic and has led to multiple interpretations by different commentators. As ''Kelleher & Murray'' have noted,<ref>''Kelleher & Murray'', EU Data Protection Law (Bloomsbury Professional 2018), p. 279.</ref> if interpreted literally (and in isolation) this provision seems to imply that the consultation should always take place whenever a high risk is indicated by the DPIA, irrespective of the measures and safeguards incorporated by the controller to mitigate these risks in this assessment (ie. in their “''absence''”). For example, ''Rucker & Kugler'' take this literal approach, affirming that “[''t]his means that the consultation obligation applies even if the controller has taken sufficient risk mitigation measures.''”<ref>''Rücker & Kugler'', New European General Data Protection Regulation, a practitioner's guide: ensuring compliant corporate practice (C.H. Beck, Hart, Nomos, 2018) p. 142.</ref> On the other hand, others such as ''Alvarez Rigaudias & Spina'' have interpreted that the prior consultation is only required when the high risk “''cannot be mitigated through appropriate measures.''”<ref>''Alvarez Rigaudias, Spina'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 36 GDPR, p. 684 (Oxford University Press 2020).</ref>

Recital 94 sheds some light on this provision, if only by essentially contradicting it, as ''Kelleher & Murray'' also note.<ref>''Kelleher & Murray'', EU Data Protection Law (Bloomsbury Professional 2018), p. 279.</ref> According to this Recital, what actually triggers the consultation is when a DPIA indicates that without the adoption of mitigating measures the processing would result in a high risk “''and the controller is of the opinion that the risk cannot be mitigated by reasonable means in terms of available technologies and costs of implementation.''” The Article 29 Working Party (WP29) further elaborates on this point, clarifying that “''[w]henever the data controller cannot find sufficient measures to reduce the risks to an acceptable level (i.e. the residual risks are still high), consultation with the supervisory authority is required.''”<ref>WP29, Guidelines on Data Protection Impact Assessment (DPIA) and determining whether processing is “likely to result in a high risk” for the purposes of Regulation 2016/679, 4 October 2017, p. 19.</ref> Therefore, there are essentially two conditions for the application of the rules. First, the processing must present a high risk to the rights and freedoms of the data subject as defined in [[Article 35 GDPR|Articles 35(1)]], [[Article 35 GDPR|(3)]] and [[Article 35 GDPR|(4) GDPR]]. Second, after a DPIA has been carried out, the controller cannot find reasonable and sufficient mitigating measures to bring the risk to an acceptable level. It may of course be the case that, from a technical point of view, no containment measures exist.<ref>Some commentators give the example of blockchain technology, and propose that a consultation in this case would have the role of assessing the processing operation in line with the principle of proportionality. The DPA would then assess whether the operation is necessary and proportionate in a democratic society (suitable to achieving a legitimate aim, the least intrusive yet equally effective mean, as well as properly balancing the risks to individuals against the interest of the controller and society). See, ''Alvarez Rigaudias, Spina'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 36 GDPR, p. 684 (Oxford University Press 2020).</ref>

However, it may also happen that some measures exist but the controller decides not to adopt them because, say, they are too expensive.<ref>Some commentators emphasise that controllers would then risk that the DPA arrives at a different result after weighing the risks of the processing operation against the economic interests of the controllers in choosing not to take the appropriate mitigating measures. See ''Jandt'', in Kühling, Buchner, DS-GVO BDSG, Article 36 GDPR, margin number 5 (C.H. Beck 2020, 3rd Edition).</ref> In both cases, the prior consultation procedure is triggered and the DPA could prohibit the controller from moving forward with the processing operation, ''de facto'' making the prior consultation procedure work as an authorisation.<ref>''Jandt'', in Kühling, Buchner, DS-GVO BDSG, Article 36 GDPR, margin number 5 (C.H. Beck 2020, 3rd Edition).</ref> Under Article 36(1), the controller needs to consult the DPA after having conducted a DPIA but prior to processing. However, there can be exceptional cases when a controller needs to consult the DPA after the start of the processing operation. Such a situation could occur when technical or organizational changes alter the risk assessment and lead to residual risks which cannot be mitigated by the controller.<ref>''Alvarez Rigaudias, Spina'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 36 GDPR, p. 683 (Oxford University Press 2020).</ref>

=== (2) Procedural Aspects ===
According to Article 36(2) GDPR, where the DPA is of the opinion that the intended processing referred to in paragraph 1 would infringe the GDPR, in particular where the controller has insufficiently identified or mitigated the risk, the DPA has to provide written advice to the controller within eight weeks, which can be extended by another six weeks if the processing operation is especially complex.<ref>The supervisory authority shall inform the controller and, where applicable, the processor, of any such extension within one month of receipt of the request for consultation together with the reasons for the delay.</ref> During the consultation process, the DPA would first need to assess whether the controller has correctly identified the risks as well as the appropriate mitigating measures. In this context, the DPA must look at both legal aspects and the latest available technologies that would help mitigate the risks.<ref>''Jandt'', in Kühling, Buchner, DS-GVO BDSG, Article 36 GDPR, margin number 7 (C.H. Beck 2020, 3rd Edition).</ref> In addition, the DPA would need to look at the broader societal context of the processing operation and decide whether the potentially high risks it entails are proportionate even when appropriate (even if not sufficient) mitigation measures have been adopted, or according to the interests at stake (for e.g. an underlying public or private interest, and no objective possibility of mitigation).<ref>''Alvarez Rigaudias, Spina'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 36 GDPR, p. 685 (Oxford University Press 2020).</ref> A contested point about the nature of the consultation procedure is whether the advice of the DPA is indeed merely an advice, or whether it can be seen as an approval on moving forward with the processing operation.<ref>In this context, questions would also relate to whether the result of the consultation procedure can be seen as legally binding decision and therefore subject covered by Article 78 GDPR. See, ''Alvarez Rigaudias, Spina'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 36 GDPR, p. 686 (Oxford University Press 2020).</ref> The use of the term "''advice''", however, leaves little doubt in this respect. Therefore, although the submission of the consultation must be carried out before the processing starts, it does not actually prevent the controller from carrying out the processing despite the high risks involved.<ref>''Reibach'', in Taeger, Gabel, DSGVO BDSG, Article 36 GDPR, margin number 12 (C.H. Beck 2019, 3th Edition).</ref> The controller is free to ignore the advice received in the consultation, but assumes all responsibility if the DPA subsequently decides to sanction it for an eventual violation related to the processing it was advised on. This interpretation, moreover, is consistent with the reference that Article 36(2) GDPR itself makes to [[Article 58 GDPR]]. In the event of a breach, the DPA may always issue a corrective measure under [[Article 58 GDPR]]. The submission of the consultation, which must be carried out before the start of the processing, does not prevent the controller from carrying out the processing despite the high risks involved.<ref>''Reibach'', in Taeger, Gabel, DSGVO BDSG, Article 36 GDPR, margin number 12 (C.H. Beck 2019, 3th Edition).</ref> Finally, in the absence of a response within the fixed deadline, it can be implicitly assumed that the authority has no further recommendations.
=== (3) Information to be provided to the DPA ===
Under Article 36(3) GDPR, the controller shall provide the DPA with a range of information, including a description of: the responsibilities of the controller, joint controllers and processors involved in the processing, in particular for processing within a group of undertakings (Article 36(3)(a) GDPR); the purposes and means of the intended processing (Article 36(3)(b) GDPR);<ref>This information should be already available to the controller due to the previously done DPIA. See, [https://gdprhub.eu/Article%2035%20GDPR Article 35(7)(a) GDPR.]</ref> the measures and safeguards provided to protect the rights and freedoms of data subjects, including all technical, organisational or legal safeguards that mitigate the risks of processing (Article 36(3)(c) GDPR); the contact details of the Data Protection Officer (DPO) (Article 36(3)(d) GDPR); a copy of the DPIA (Article 36(3)(e) GDPR) as well as any other information requested by the DPA (Article 36(3)(f) GDPR). Furthermore, the DPO will need to act as contact point throughout the consultation process.<ref>[https://gdprhub.eu/Article%2039%20GDPR See Article 39(1)(e) GDPR].</ref>

=== (4) Member State's Prior Consultation Obligation ===
When preparing a proposal for primary or secondary legislation under national law related to processing, Member States should also carry out a prior consultation process with the DPA. However, this procedure is different in nature and scope than the one in Article 36(1) GDPR, since it involves those preparing national law provisions and not controllers, and it could be related to processing which does not necessarily result in high risks for data subjects’ rights and freedoms. Furthermore, from a procedural perspective, it is not subject to the same deadline as Article 36(1) GDPR, and it is still disputed whether the outcome of the procedure rather resembles that of [[Article 58 GDPR|Article 58(3)(a) GDPR]] or [[Article 58 GDPR|Article 58(3)(b) GDPR]].<ref>With regards to consultations in the context of legislative initiatives based on Article 36(4), it is still disputed whether the outcome of the procedure rather resembles that of Article 58(3)(a) GDPR or Article 58(3)(b) GDPR. See, ''Alvarez Rigaudias, Spina'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 36 GDPR, p. 686 (Oxford University Press 2020); ''Jandt'', in Kühling, Buchner, DS-GVO BDSG, Article GDPR, margin number 11 (C.H. Beck 2020, 3rd Edition).</ref>

=== (5) Member State Law May Provide for Stricter Requirements ===
Unlike the consultation process under Article 36(1) GDPR, this provision establishes that Member State law may require controllers to not only seek advice, but also a prior authorisation from the DPA, in order to carry out certain types of processing related performing tasks in the public interest.

==Decisions==
→ You can find all related decisions in [[:Category:Article 36 GDPR]]

==References==
<references />

[[Category:GDPR Articles]]

Article 36 GDPR - Revision history

Bodobalazs: 1 revision imported: GDPRHUB import 2023 04 18