Banner2.png

Article 29 GDPR: Difference between revisions

From GDPRhub
No edit summary
(Article 29)
Line 202: Line 202:
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>   
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>   
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.<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>   
''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}}
{{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}}But also other people than employees could be considered as persons acting under the authority of the controller or the processor. Especially in regards of freelancers, consultants or other relationships with similarities to employees, this could lead to difficult determinations. The respective assessment should be performed on a case by case basis and should, inter alia, consider the independence of the person.<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 13 (C.H. Beck 2024, 4th Edition).</ref>
 
Article 29 GDPR applies also to sub-processors; in this case, the requirements of Article 28 GDPR have to be considered as well.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 14 (C.H. Beck 2024, 4th Edition).</ref>
 
In any way, the fact that a person is subject to Article 29 GDPR should not be used as a factor to avoid the conclusion of a processing agreement under Article 28 GDPR.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 14 (C.H. Beck 2024, 4th Edition).</ref>


=== Shall not process ===
=== 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>
==== Except on the instructions from the controller ====
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.  
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 does so without their instructions. In other words, this persons are bound by the instructions of the controller (or processor).     
 
An instruction could be any order to do or refrain from doing something, e.g. regarding the implementation of technical and organisational measures or the performance of a processing activity. Article 29 GDPR does not provide any requirements for this instructions, but considering the potential liability and consequences, it is recommended that the actors document all instructions which should at the same time be sufficiently clear.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 15 et seq. (C.H. Beck 2024, 4th Edition).</ref> Persons under the authority of the controller or processor are generally not obliged to assess the lawfulness of the instruction.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 18 (C.H. Beck 2024, 4th Edition) with further references and potential exceptions.</ref> However, a processor is obliged to inform the controller, if it considers that instructions of the controller infringes the GDPR or other laws (see [[Article 28 GDPR|Article 28(3) GDPR]]). 


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&nbsp;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>
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&nbsp;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 ====
Article 29 GDPR provides for an exception of the general rule that personal data can only be processed according to the instructions of the controller. According to this provision, this rule does not apply when a person (including a processor) acting under the authority of the controller or of the processor, is otherwise required by Union or Member State law. 


==== unless required to do so by Union or Member State law ====
This could be the case if a person is legally obliged to provide data to authorities or to archive specific information. Insufficient is a provision in Union or Member State law that merely allows for the processing.<ref>''Hartung'', in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 19 (C.H. Beck 2024, 4th Edition).</ref>


==== Commonalities and differences in relation to [[Article 28 GDPR|Article 28(3)(b) GDPR]] ====
==== Commonalities and differences in relation to [[Article 28 GDPR|Article 28(3)(b) GDPR]] ====

Revision as of 10:57, 19 February 2025

Article 29 - Processing under the authority of the controller or processor
Gdpricon.png
Chapter 10: Delegated and implementing acts

Legal Text


Article 29 - Processing under the authority of the controller or processor

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

Recital 81: Entrusting a Processor
To ensure compliance with the requirements of this Regulation in respect of the processing to be carried out by the processor on behalf of the controller, when entrusting a processor with processing activities, the controller should use only processors providing sufficient guarantees, in particular in terms of expert knowledge, reliability and resources, to implement technical and organisational measures which will meet the requirements of this Regulation, including for the security of processing. The adherence of the processor to an approved code of conduct or an approved certification mechanism may be used as an element to demonstrate compliance with the obligations of the controller. The carrying-out of processing by a processor should be governed by a contract or other legal act under Union or Member State law, binding the processor to the controller, setting out the subject-matter and duration of the processing, the nature and purposes of the processing, the type of personal data and categories of data subjects, taking into account the specific tasks and responsibilities of the processor in the context of the processing to be carried out and the risk to the rights and freedoms of the data subject. The controller and processor may choose to use an individual contract or standard contractual clauses which are adopted either directly by the Commission or by a supervisory authority in accordance with the consistency mechanism and then adopted by the Commission. After the completion of the processing on behalf of the controller, the processor should, at the choice of the controller, return or delete the personal data, unless there is a requirement to store the personal data under Union or Member State law to which the processor is subject.

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.[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]

EDPB-icon.png

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

But also other people than employees could be considered as persons acting under the authority of the controller or the processor. Especially in regards of freelancers, consultants or other relationships with similarities to employees, this could lead to difficult determinations. The respective assessment should be performed on a case by case basis and should, inter alia, consider the independence of the person.[6]

Article 29 GDPR applies also to sub-processors; in this case, the requirements of Article 28 GDPR have to be considered as well.[7]

In any way, the fact that a person is subject to Article 29 GDPR should not be used as a factor to avoid the conclusion of a processing agreement under Article 28 GDPR.[8]

Shall not process

Except on the instructions from the controller

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).[9]

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 does so without their instructions. In other words, this persons are bound by the instructions of the controller (or processor).

An instruction could be any order to do or refrain from doing something, e.g. regarding the implementation of technical and organisational measures or the performance of a processing activity. Article 29 GDPR does not provide any requirements for this instructions, but considering the potential liability and consequences, it is recommended that the actors document all instructions which should at the same time be sufficiently clear.[10] Persons under the authority of the controller or processor are generally not obliged to assess the lawfulness of the instruction.[11] However, a processor is obliged to inform the controller, if it considers that instructions of the controller infringes the GDPR or other laws (see Article 28(3) GDPR).

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.[12]

Unless required to do so by Union or Member State law

Article 29 GDPR provides for an exception of the general rule that personal data can only be processed according to the instructions of the controller. According to this provision, this rule does not apply when a person (including a processor) acting under the authority of the controller or of the processor, is otherwise required by Union or Member State law.

This could be the case if a person is legally obliged to provide data to authorities or to archive specific information. Insufficient is a provision in Union or Member State law that merely allows for the processing.[13]

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.[14]

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.[15] 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

  1. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 1 (C.H. Beck 2024, 4th Edition).
  2. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 7 (C.H. Beck 2024, 4th Edition).
  3. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 10 (C.H. Beck 2024, 4th Edition).
  4. Bogendorfer, in Knyrim, DatKomm, Article 24 GDPR, margin numbers 18 (Manz 2022) with further reference.
  5. 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).
  6. 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 13 (C.H. Beck 2024, 4th Edition).
  7. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 14 (C.H. Beck 2024, 4th Edition).
  8. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 14 (C.H. Beck 2024, 4th Edition).
  9. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 6 (C.H. Beck 2024, 4th Edition).
  10. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 15 et seq. (C.H. Beck 2024, 4th Edition).
  11. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 18 (C.H. Beck 2024, 4th Edition) with further references and potential exceptions.
  12. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 5 (C.H. Beck 2024, 4th Edition).
  13. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 19 (C.H. Beck 2024, 4th Edition).
  14. Millard, Kamarinou, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 29 GDPR, p. 613 (Oxford University Press 2020).
  15. Millard, Kamarinou, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 29 GDPR, p. 615 (Oxford University Press 2020).