Banner2.png

Article 29 GDPR

From GDPRhub
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 (as defined in Article 4(8) GDPR) and anyone with access to personal data acting under the authority of the controller (as defined in Article 4(7) GDPR) 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 will stay the entity which determines 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

This provision applies to both 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 that is processed on the controller's behalf. It is not necessary that the personal data is actually accessed or otherwise processed by that person.[2]

Regarding the processor as the addressee of this obligation, it should be noted that there are similar and connected obligations in Article 28 GDPR (see commentary on Article 28 GDPR). A main feature of Article 29 GDPR is, however, that every person acting under the authority of the processor is also directly bound by 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 refers to legal persons as well as to natural persons.[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. Therefore, there must be some legal relationship between the person and the controller or processor.[5] This is the case for employees of the controller or processor.[6]

EDPB-icon.png

"Employees who have access to personal data within an organisation 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 people other than employees could also be considered as persons acting under the authority of the controller or the processor. Determinations of this requirement in respect of freelancers, consultants or other relationships with similarities to employees can all prove difficult. The respective assessment should be performed on a case-by-case basis and should, inter alia, consider the independence of the person.[7]

Example-icon.png

For example: A freelancer provides limited technical support for a company and potentially has access to the personal data of the company's employees while fixing some bugs in the system used by the controller to record its employees' working hours.


The company as controller and the freelancer have to asses whether the freelancer should be considered a processor or if it is only a person under the authority of the controller. Therefore they should consider, inter alia, how integrated the freelancer is in the controller's organisation, how the controller's authority over the freelancer (especially regarding data protection) is formulated in the respective agreement and the level of the freelancer's independence in fulfilling his duties.[8]


Regarding persons under the authority of a processor, reference can also be made to Article 28(3)(b) GDPR, which stipulates that a processing agreement has to oblige the processor to ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (see commentary on Article 28(3)(b) GDPR).[9]

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

In any event, 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.[11]

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 ensuring 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 controller's instructions and process the data only on the controller's behalf. Otherwise, they themselves would act as controllers; Article 28(10) GDPR specifically stipulates this consequence for processors.[12]

In order to achieve this goal, Article 29 GDPR prohibits any person acting under the authority of the controller or the processor who processes personal data on their behalf from doing so without their instructions. In other words, such 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 these 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.[13] Persons under the authority of the controller or processor are generally not obliged to assess the lawfulness of the instruction.[14] 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). Arguably, the recipient of an instructions is not bound by it if the instruction is clearly unlawful.[15]

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

Unless required to do so by Union or Member State law

Article 29 GDPR provides for an exception to the general rule that personal data can only be processed in accordance with 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. Provisions in Union or Member State law that merely allow for the processing are insufficient.[17] This provision also does not apply to the compliance with obligations that are directed at the controller.[18]

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); Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 29 GDPR, margin numbers 11 (NOMOS 2025, 2nd 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. Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 29 GDPR, margin numbers 11 (NOMOS 2025, 2nd 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 12 (C.H. Beck 2024, 4th Edition).
  7. 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); Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 29 GDPR, margin numbers 9 (NOMOS 2025, 2nd Edition).
  8. Bogendorfer, in Knyrim, DatKomm, Article 24 GDPR, margin numbers 17 (Manz 2022).
  9. Compare Millard, Kamarinou, in Kuner, Bygrave, Docksey, The EU General Data Protection Regulation (GDPR): A Commentary, Article 29 GDPR, p. 615 (Oxford University Press 2020).
  10. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 14 (C.H. Beck 2024, 4th Edition).
  11. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 14 (C.H. Beck 2024, 4th Edition).
  12. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 6 (C.H. Beck 2024, 4th Edition); Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 29 GDPR, margin numbers 16 (NOMOS 2025, 2nd Edition).
  13. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 15 et seq. (C.H. Beck 2024, 4th Edition); Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 29 GDPR, margin numbers 14 (NOMOS 2025, 2nd Edition).
  14. 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.
  15. Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 29 GDPR, margin numbers 18 (NOMOS 2025, 2nd Edition).
  16. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 5 (C.H. Beck 2024, 4th Edition).
  17. Hartung, in Kühling, Buchner, DS-GVO BDSG, Article 29 GDPR, margin number 19 (C.H. Beck 2024, 4th Edition).
  18. Petri, in Simitis, Hornung, Spiecker gen. Döhmann, Datenschutzrecht, Article 29 GDPR, margin numbers 19 (NOMOS 2025, 2nd Edition).