Website hosting, a cloud payroll system, an IT support company, an accounting firm with access to staff lists. Each of these suppliers may process personal data on a company’s behalf, and the GDPR then requires an agreement that sets out what the supplier may do with that data. Such a contract is called a data processing agreement (DPA).
Article 28(3) of the GDPR defines its content, and the European Data Protection Board, in its Guidelines 07/2020, points out that the document should not merely restate the regulation. For a company’s cybersecurity, the data processing agreement is one of the few places where the controller can require specific safeguards, breach reporting rules and control over sub-processors from a supplier. An agreement that only repeats the article gives the controller no tools for that.
What is a data processing agreement?
A data processing agreement is a contract between a controller and a processor under which the processor processes personal data on the controller’s behalf. Article 28(3) of the GDPR states that processing by a processor is governed by a contract or other legal act that binds both parties.
Article 4 of the GDPR defines the parties. The controller is the body which, alone or jointly with others, determines the purposes and means of the processing of personal data (point 7). The processor is the body which processes personal data on behalf of the controller (point 8).
Legal position as of 21 November 2026. The GDPR has applied since 25 May 2018, and Articles 4, 28 and 29 have not been changed by any amending act since the regulation was adopted in 2016. Commission Implementing Decision (EU) 2021/915 with the standard contractual clauses has no amending acts either.
Under Article 28(1) the controller may use only processors providing sufficient guarantees to implement appropriate technical and organisational measures. The agreement is therefore the second step. The first is assessing whether the supplier offers such guarantees at all.
Article 28(5) suggests how such guarantees can be demonstrated: the processor may do so, among other things, by adhering to an approved code of conduct (Article 40) or an approved certification mechanism (Article 42). In practice the controller also checks what the supplier can show straight away: its security policy, audit results, an information security management system certificate and a description of who on the supplier’s side has access to the data. Assessing this before signing is simpler than withdrawing from the contract once the data is already with the supplier.
When do you need a data processing agreement, and when don’t you?
You need a data processing agreement when an external party processes personal data on your company’s behalf and on its instructions. You do not need one when the other party decides on the purposes and means of processing itself, because it is then a separate controller.
The boundary is not always obvious. In its Guidelines 07/2020 on the concepts of controller and processor, the European Data Protection Board (EDPB) explains that the actual influence on the purposes and means of processing is decisive, not merely the label given to a party in the contract. The guidelines were adopted on 7 July 2021, and version 2.1 with minor corrections was published on 20 September 2022.
In practice the test question is: does the supplier use the data only to deliver the service to your company, or also for its own purposes? A hosting company storing an online shop’s customer database acts on the shop’s behalf. A supplier that uses the same data for its own analytics or marketing goes beyond the processor role, and that has to be settled before the agreement is signed.
You do not conclude a data processing agreement with your own employees. People employed by the controller process data under its authority on the basis of Article 29 of the GDPR. The difference between these documents is covered in the article on staff authorisation to process personal data.
What must a data processing agreement contain under Article 28(3) of the GDPR?
The agreement must set out the subject matter and duration of the processing, its nature and purpose, the type of personal data, the categories of data subjects, and the obligations and rights of the controller. In addition, Article 28(3) lists eight commitments of the processor, marked with letters (a) to (h).
The processor:
- processes the data only on documented instructions from the controller, including for transfers to a third country (point a);
- ensures that persons authorised to process the data have committed themselves to confidentiality or are under a statutory obligation of confidentiality (point b);
- takes the measures required under Article 32, that is, the security of processing (point c);
- respects the conditions for engaging another processor (point d);
- assists the controller in responding to requests from data subjects (point e);
- assists the controller in meeting the obligations of Articles 32 to 36, including breaches and impact assessments (point f);
- at the end of the services deletes or returns the data and deletes copies, at the controller’s choice (point g);
- makes available the information needed to demonstrate compliance and allows audits, including inspections (point h).
The same paragraph adds an obligation that is easy to overlook: the processor immediately informs the controller if, in its opinion, an instruction infringes data protection rules. It is therefore worth stating in the agreement who on the controller’s side issues instructions and to whom the supplier sends such concerns. Without this, instructions arrive by email from different people, and the supplier does not know which of them are binding.
Key points:
- You need a data processing agreement when a supplier processes personal data on your company’s behalf and on its instructions.
- Article 28(3) of the GDPR lists the elements describing the processing and eight commitments of the processor (points a–h).
- The agreement must be in writing, including electronic form (Article 28(9)).
- The Commission’s standard contractual clauses in Decision 2021/915 can be used instead of negotiating your own text.
Why shouldn’t the agreement simply restate Article 28 of the GDPR?
An agreement that only repeats Article 28 does not say how the supplier will meet the requirements. The EDPB put this plainly in Guidelines 07/2020: the processing agreement should not merely restate the provisions of the GDPR, but should include specific, concrete information on how the requirements will be met and which level of security is required.
In practice the difference shows in the safeguards. The sentence “the processor applies the measures referred to in Article 32” complies with the law, but it allows nothing to be checked. A clause stating that data is encrypted at rest and in transit, backups are tested and administrative access requires multi-factor authentication gives the controller a reference point during an audit.
The same principle applies to breach reporting. Article 28(3)(f) obliges the processor to assist with the obligations of Articles 33 and 34. The agreement can specify the deadline and channel by which the supplier reports a breach to the controller and what information it provides.
How should you regulate the use of sub-processors?
The processor may not engage another processor without the controller’s prior specific or general written authorisation (Article 28(2)). With general authorisation it informs the controller of any intended addition or replacement of a sub-processor and gives the controller the opportunity to object.
Article 28(4) requires the same data protection obligations as in the main agreement to be imposed on the other processor. If the other processor fails to fulfil them, the initial processor remains fully liable to the controller.
The Commission’s standard contractual clauses offer two options here. Under option one, the processor needs prior specific authorisation for each sub-processor, and the list goes into Annex IV. Under option two, a general authorisation applies, with a period for raising objections. It is worth agreeing the option before signing: specific authorisation gives more control, but requires a new authorisation for every change of sub-processor.
Can you use the Commission’s standard contractual clauses?
Yes. Commission Implementing Decision (EU) 2021/915 of 4 June 2021 adopted standard contractual clauses between controllers and processors. According to Article 1 of the decision, the clauses meet the requirements for contracts set out in Article 28(3) and (4) of the GDPR.
The clauses have a fixed wording. Under Clause 2 the parties undertake not to modify them, except for adding or updating information in the annexes. They may, however, include the clauses in a wider contract and add other provisions as long as these do not contradict the clauses. The decision is published in official language versions, including Polish and English, so an agreement with a supplier can rely directly on an official text without a translation of your own.
The annexes are where the agreement stops being generic. Annex I lists the parties, Annex II describes the processing (categories of data subjects and data, sensitive data, purpose, duration), Annex III sets out the technical and organisational measures, and Annex IV lists sub-processors where specific authorisation applies.
Which security measures should you describe in a data processing agreement?
Describe the security measures in the agreement so that they can be checked. The explanatory note to Annex III of the standard contractual clauses says that the technical and organisational measures must be described specifically rather than generically.
The starting point is Article 32 of the GDPR, to which Article 28(3)(c) refers: the controller and the processor implement measures ensuring a level of security appropriate to the risk. A description for a particular supplier may include encryption, access control and its reviews, event logging, backups with restore tests, segmentation of the environment and the way breaches are reported.
A description only makes sense if the controller can verify it. The right to audit in Article 28(3)(h) allows you to ask for test reports, information security management system certificates or review results. For suppliers with access to key systems, it is worth agreeing which evidence the supplier provides every year without a separate request.
What should happen to the data when the agreement ends?
At the end of the services the processor, at the controller’s choice, deletes or returns the data and deletes existing copies, unless the law requires storage (Article 28(3)(g)). The agreement should settle which option applies, in what format and by when the data is returned, and how the supplier confirms deletion.
This point is often skipped at signing and comes back when the supplier changes. A company that has not agreed a return format may, when migrating to a new system, receive an export that is hard to import. It is also worth agreeing what happens to the supplier’s backups that still contain the data after the end date of the agreement. For larger deployments the agreement can also provide a transition period in which the current supplier continues the service until the data reaches the new system.
How do you check a data processing agreement before signing?
Before signing a data processing agreement, go through the list of Article 28 elements and ask for each whether the clause can be checked. Vague wording most easily passes for compliance in the clauses on security, breaches and audits.
| Element | Provision | What to check in the text | Warning sign |
|---|---|---|---|
| Description of processing | Article 28(3), first sentence | Subject matter, duration, purpose, type of data, categories of data subjects | A generic description that fits any service |
| Controller’s instructions | Article 28(3)(a) | How the controller issues and documents instructions | No clause on transfers outside the EEA |
| Security | Article 28(3)(c), Article 32 | Specific measures and how they are verified | A bare reference to Article 32 |
| Sub-processors | Article 28(2) and (4) | Type of authorisation, list, objection period | No information on changes of sub-processors |
| Breaches | Article 28(3)(f) | Reporting deadline and channel, scope of information | Reporting “without undue delay” with no channel or contact person |
| End of the agreement | Article 28(3)(g) | Deletion or return, format, confirmation | No rules for backups |
| Audits | Article 28(3)(h) | Which evidence and how often | Audit possible only “by agreement” with no timeframe |
The warning signs in the table mark the places where the agreement complies with the law but gives the controller no means of control. Such places are worth fixing before signing, because once the service starts the controller’s negotiating position weakens.
How can nFlo help you put your data processing agreements in order?
The Comprehensive GDPR Review and Advisory at nFlo covers, among other things, an inventory of processing, an assessment of legal bases and a review of data processing agreements with suppliers such as hosting, CRM and marketing providers. The Data Protection Officer (DPO) Outsourcing service provides an external officer who performs the role required by Articles 37 to 39 of the GDPR and carries out ongoing compliance oversight. nFlo does not provide legal services, so the final text of an agreement is settled by the parties’ lawyers. The rules described here come from EU law; in Poland the supervisory authority is UODO.
The wider context of a controller’s obligations is covered in the guide What is the GDPR (RODO in Polish), and the concepts in the GDPR glossary entry. Other articles on data protection are collected in the GDPR section of the knowledge base. If you want to check your supplier agreements against Article 28, contact us.
What else should you know about data processing agreements?
Does a data processing agreement have to be signed on paper?
No. Article 28(9) of the GDPR requires written form, including electronic form. An agreement concluded electronically, for example as part of service terms accepted by the controller, meets this requirement if it contains the elements of Article 28(3).
Does the GDPR provide a template data processing agreement?
The GDPR provides a list of mandatory elements, not a template. A ready text is offered by the European Commission’s standard contractual clauses in Implementing Decision (EU) 2021/915, which the parties can use unchanged while completing the annexes.
Who is liable for the supplier’s sub-processor?
Under Article 28(4) of the GDPR, if the other processor fails to fulfil its data protection obligations, the initial processor remains fully liable to the controller.
Do a company’s employees need a data processing agreement?
No. An employee acts under the authority of the controller on the basis of Article 29 of the GDPR, not as a separate processor. A data processing agreement concerns external companies and individuals processing data on the controller’s behalf.
What happens to the data when a data processing agreement ends?
Article 28(3)(g) of the GDPR requires the processor, at the controller’s choice, to delete or return the data and delete existing copies, unless the law requires storage of the data.
