Article 29 GDPR: Difference between revisions
No edit summary |
|||
Line 195: | Line 195: | ||
Article 29 GDPR obliges processors and anyone with access to personal data that acts under the authority of the controller or processor to only process those data on instructions from the controller, unless required to do otherwise by Union or Member State law. | Article 29 GDPR obliges processors and anyone with access to personal data that acts under the authority of the controller or processor to only process those data on instructions from the controller, unless required to do otherwise by Union or Member State law. | ||
===Commonalities and differences in relation to [[Article 28 GDPR|Article 28(3)(b) GDPR]]=== | Therefore, this provision establishes an obligation for anybody processing the data on behalf of a controller, to follow the controller's instructions in order for the controller to stay in control of the purposes and means of the processing.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 1 (C.H. Beck 2024, 4th Edition).</ref> | ||
=== Any person acting under the authority of the controller or the processor === | |||
==== Who has access to personal data ==== | |||
Addressee of this provision is the processor and any person acting under the authority of the controller or of the processor, who has access to personal data. "Access to personal data" should be understood as the mere possibility to access the data. It is not necessary that the personal data actually is accessed or otherwise processes by that person.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 7 (C.H. Beck 2024, 4th Edition).</ref> | |||
Regarding the ''processor'' as addressee of this obligation, it should be noted that there are similar and connected obligations in Article 28 GDPR (see below). A main feature of Article 29 GDPR is, however, that also every person acting under the authority of the processor is directly bound it. This could potentially lead to conflicts, when a person under the authority of the processor (e.g. an employee of the processor) receives different instructions from the controller and the processor.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 10 (C.H. Beck 2024, 4th Edition).</ref> | |||
''Any person'' acting under the authority of the controller or the processor could be a legal or a natural person.<ref>''Bogendorfer'', in Knyrim, DatKomm, Article 24 GDPR, margin numbers 18 (Manz 2022) with further reference.</ref> A requirement is that the controller or processor has some authority over the person regarding the processing of personal data on behalf of the controller or processor. This is the case for employees of the controller or processor.<ref>''Bogendorfer'', in Knyrim, DatKomm, Article 29 GDPR, margin numbers 17 (Manz 2022); ''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 12 (C.H. Beck 2024, 4th Edition).</ref> | |||
{{Quote-EDPB|"Employees who have access to personal data within an rganisation are generally not considered as “controllers” or “processors”, but rather as “persons acting under the authority of the controller or of the processor” within the meaning of article 29 GDPR"|EDPB, 'Guidelines 07/2020 on the concepts of controller and processor in the GDPR', 7 July 2021 (Version 2.1), foot note 9.|4=https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-072020-concepts-controller-and-processor-gdpr_en}} | |||
=== Shall not process === | |||
Article 29 GDPR, together with various other provisions like [[Article 24 GDPR|Article 24]] and [[Article 28 GDPR|28 GDPR]], aims at a clear distribution of responsibilities for the processing of personal data. The controller is the ultimate decision maker and determines the purposes and means of the processing (see [[Article 4 GDPR|Article 4(7) GDPR]]). On the other hand, everybody else involved in the processing, should follow the controllers instructions and process the data only on the controller's behalf. Otherwise, they themselves would act as controllers (e.g. see commentary on [[Article 28 GDPR|Article 28(10) GDPR]]).<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 6 (C.H. Beck 2024, 4th Edition).</ref> | |||
In order to archive this goal, Article 29 GDPR prohibits that any person acting under the authority of the controller or the processor who processes personal data on their behalf to do so without their instructions. | |||
This provision directly obliges its addressees without the need to first contractually agree on this obligation, which is a significant difference to [[Article 28 GDPR|Article 28(3)(a) GDPR]]. Processors and any other person acting under the authority of the controller (or processor) are therefore directly bound by this provision even if respective contractual clause with the controller or processor was concluded.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 5 (C.H. Beck 2024, 4th Edition).</ref> | |||
==== Except on the instructions from the controller ==== | |||
==== unless required to do so by Union or Member State law ==== | |||
==== Commonalities and differences in relation to [[Article 28 GDPR|Article 28(3)(b) GDPR]] ==== | |||
After deliberations during negotiations between the Council, Parliament and Commission, the provision was maintained in the final text of the GDPR despite some arguments against its relevance. The provision is aimed at reinforcing the processor’s obligations to only act in line with the controller’s instructions, as well as at clarifying that these obligations extend to any person acting under the authority of the controller or processor.<ref>''Millard, Kamarinou'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 29 GDPR, p. 613 (Oxford University Press 2020).</ref> | After deliberations during negotiations between the Council, Parliament and Commission, the provision was maintained in the final text of the GDPR despite some arguments against its relevance. The provision is aimed at reinforcing the processor’s obligations to only act in line with the controller’s instructions, as well as at clarifying that these obligations extend to any person acting under the authority of the controller or processor.<ref>''Millard, Kamarinou'', in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 29 GDPR, p. 613 (Oxford University Press 2020).</ref> | ||
Revision as of 09:25, 19 February 2025
Legal Text
The processor and any person acting under the authority of the controller or of the processor, who has access to personal data, shall not process those data except on instructions from the controller, unless required to do so by Union or Member State law.
Relevant Recitals
Commentary
Article 29 GDPR obliges processors and anyone with access to personal data that acts under the authority of the controller or processor to only process those data on instructions from the controller, unless required to do otherwise by Union or Member State law.
Therefore, this provision establishes an obligation for anybody processing the data on behalf of a controller, to follow the controller's instructions in order for the controller to stay in control of the purposes and means of the processing.[1]
Any person acting under the authority of the controller or the processor
Who has access to personal data
Addressee of this provision is the processor and any person acting under the authority of the controller or of the processor, who has access to personal data. "Access to personal data" should be understood as the mere possibility to access the data. It is not necessary that the personal data actually is accessed or otherwise processes by that person.[2]
Regarding the processor as addressee of this obligation, it should be noted that there are similar and connected obligations in Article 28 GDPR (see below). A main feature of Article 29 GDPR is, however, that also every person acting under the authority of the processor is directly bound it. This could potentially lead to conflicts, when a person under the authority of the processor (e.g. an employee of the processor) receives different instructions from the controller and the processor.[3]
Any person acting under the authority of the controller or the processor could be a legal or a natural person.[4] A requirement is that the controller or processor has some authority over the person regarding the processing of personal data on behalf of the controller or processor. This is the case for employees of the controller or processor.[5]
"Employees who have access to personal data within an rganisation are generally not considered as “controllers” or “processors”, but rather as “persons acting under the authority of the controller or of the processor” within the meaning of article 29 GDPR"
Shall not process
Article 29 GDPR, together with various other provisions like Article 24 and 28 GDPR, aims at a clear distribution of responsibilities for the processing of personal data. The controller is the ultimate decision maker and determines the purposes and means of the processing (see Article 4(7) GDPR). On the other hand, everybody else involved in the processing, should follow the controllers instructions and process the data only on the controller's behalf. Otherwise, they themselves would act as controllers (e.g. see commentary on Article 28(10) GDPR).[6]
In order to archive this goal, Article 29 GDPR prohibits that any person acting under the authority of the controller or the processor who processes personal data on their behalf to do so without their instructions.
This provision directly obliges its addressees without the need to first contractually agree on this obligation, which is a significant difference to Article 28(3)(a) GDPR. Processors and any other person acting under the authority of the controller (or processor) are therefore directly bound by this provision even if respective contractual clause with the controller or processor was concluded.[7]
Except on the instructions from the controller
unless required to do so by Union or Member State law
Commonalities and differences in relation to Article 28(3)(b) GDPR
After deliberations during negotiations between the Council, Parliament and Commission, the provision was maintained in the final text of the GDPR despite some arguments against its relevance. The provision is aimed at reinforcing the processor’s obligations to only act in line with the controller’s instructions, as well as at clarifying that these obligations extend to any person acting under the authority of the controller or processor.[8]
The discussions on the relevance of Article 29 GDPR were rooted in the fact that Article 28(3)(b) GDPR already seems to cover much of the scope of Article 29 GDPR. More specifically, Article 28(3)(b) GDPR states that the contract between the controller and processor shall stipulate that the processor “ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality”.
While Article 28(3)(b) GDPR seems to already designate the controller as liable for violations carried out by its employees, Millard and Kamarinou suggest that “Article 29 GDPR exists to reiterate that, despite the processor’s increased responsibilities under the GDPR, it is ultimately the controller’s instructions which should be followed at every stage of the processing.”[9] As such, Article 29 GDPR explicitly extends the obligations arising from the data processing agreement in Article 28(3)(b) GDPR to all persons acting under the authority of the controller and processor.
Decisions
→ You can find all related decisions in Category:Article 29 GDPR
References
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 1 (C.H. Beck 2024, 4th Edition).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 7 (C.H. Beck 2024, 4th Edition).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 10 (C.H. Beck 2024, 4th Edition).
- ↑ Bogendorfer, in Knyrim, DatKomm, Article 24 GDPR, margin numbers 18 (Manz 2022) with further reference.
- ↑ Bogendorfer, in Knyrim, DatKomm, Article 29 GDPR, margin numbers 17 (Manz 2022); Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 12 (C.H. Beck 2024, 4th Edition).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 6 (C.H. Beck 2024, 4th Edition).
- ↑ Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 5 (C.H. Beck 2024, 4th Edition).
- ↑ Millard, Kamarinou, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 29 GDPR, p. 613 (Oxford University Press 2020).
- ↑ Millard, Kamarinou, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 29 GDPR, p. 615 (Oxford University Press 2020).