Receiving data does not make you a processor
Basic terms, part 12: as soon as data leaves the organisation, a data processing agreement is requested by reflex. Often it does not fit at all. The GDPR knows three set-ups with three different consequences, and which one applies is decided not by the contract but by who determines purposes and means.
The external payroll office gets the salary data, the law firm gets the personnel file for the unfair dismissal case, the cloud provider gets the entire mailbox, the neighbouring municipality gets the data for the shared citizen portal. In many organisations, the same sentence follows: we need a data processing agreement for that.
Sometimes that is right. Often it is not. The GDPR knows three set-ups in which personal data reaches another party, and each has different consequences.
The basic question: who decides?
Everything depends on the definition of the controller in Art. 4(7) GDPR: the body which, alone or jointly with others, determines the purposes and means of the processing of personal data. A processor, under Art. 4(8), is a body which processes personal data on behalf of the controller.
In its Guidelines 07/2020, the European Data Protection Board makes clear that reality is what counts. The role is to be determined on the basis of the actual activities in a specific situation, not on the formal designation, for example in a contract. A data processing agreement therefore does not make anyone a processor who in fact pursues their own purposes.
Processing on behalf: on instruction
A processor processes for someone else's purposes and on their instructions. It may decide on some practical details of implementation, which the guidelines call non-essential means. Not on purpose and essential means.
For this, Art. 28(3) requires a contract or other legal act with fixed minimum content: subject matter and duration, nature and purpose, types of data, categories of data subjects, obligations and rights of the controller, and above all the commitment to documented instructions. And Art. 28(10) draws the line: a processor that itself determines purposes and means is considered a controller for that processing.
Typical cases are a data centre, cloud storage, document shredding, remote maintenance. The guidelines also mention outsourced payroll: it may not use the data for its own purposes.
Joint controllership: deciding together
Art. 26(1) applies when two or more controllers jointly determine the purposes and means of processing. They then do not conclude a data processing agreement but determine in an arrangement, in a transparent manner, who complies with which obligation under the regulation, in particular regarding data subject rights and information duties. The essence of the arrangement is made available to the data subjects.
Responsibility does not have to be shared equally. The guidelines quote the Court of Justice: joint controllership does not necessarily imply equal responsibility. Externally, however, Art. 26(3) applies: data subjects may exercise their rights in respect of and against each of the controllers. A shared portal of several authorities or a jointly operated applicant portal of a group of companies are typical cases.
Transfer: to a controller in its own right
The third set-up has no article of its own and no contract type of its own. The GDPR names disclosure by transmission in Art. 4(2) as one form of processing. If data goes to a body that processes it for its own purposes and under its own responsibility, there is neither processing on behalf nor joint controllership. Each side is responsible for itself, and passing on the data needs a legal basis like any processing.
The guidelines' example is the law firm representing a company in court: for this processing, it is a controller itself. A data processing agreement with it would not just be superfluous, it would describe the roles wrongly.
A note on usage: Chapter V of the GDPR uses "transfer" for data flows to third countries. That is an additional question that can arise in any of the three set-ups, and the subject of a later part.
The test question
For every body that receives personal data from you: may it use the data for its own purposes, and who decided what is processed for and with what? The answer gives the set-up, and the set-up gives the contract.
In isidaten's contract management, the data processing agreement under Art. 28 and the arrangement under Art. 26 are set up as separate contract types.
Sources
Regulation (EU) 2016/679 (GDPR), consolidated version with corrigenda, Art. 4(2), (7) and (8), Art. 26 and Art. 28(3) and (10).
European Data Protection Board, Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.0 of 7 July 2021, paras. 12, 39, 169 and the payroll and law firm examples.
Next Sunday in Basic terms: erasure, restriction, anonymisation, pseudonymisation. The previous part: The BIA does not ask about the cause.
Questions about this update?
Talk to us – we are happy to show you this feature in a demo.


