Skip to content
DT Nova

Data processing agreement (DPA): what GDPR Article 28 requires and how to check one

A data processing agreement, or DPA, is the contract between a company that decides why personal data is processed (the controller) and a supplier that processes that data on its behalf (the processor). The GDPR makes it mandatory and lists what it must say. This guide explains when you need a data processing agreement, the clauses Article 28 requires, how sub-processors work, the standard clauses the European Commission has published, and a checklist for reviewing a supplier's DPA.

Legal text quoted is Regulation (EU) 2016/679 (GDPR) and Commission Implementing Decision (EU) 2021/915, both read on 12 November 2026. Some countries call the document a data processing addendum, a processor agreement or, in German, an Auftragsverarbeitungsvertrag; the requirements are the same. This guide is practical information, not legal advice.

Controller or processor: who needs a DPA

You need a DPA whenever a supplier handles personal data for you and only on your instructions. Typical processors are cloud hosting, email and newsletter tools, payroll and HR software, CRM and helpdesk software, IT support with access to your systems, and the software company that builds and maintains your app. The European Data Protection Board's Guidelines 07/2020 on the concepts of controller and processor (final version 7 July 2021) explain the distinction in detail: the controller decides the purposes and the essential means; the processor acts on its behalf.

Not every supplier is a processor. A bank, an accountant or a law firm usually decides how it handles the data under its own professional duties and is a controller in its own right. Two companies that each use shared data for their own purposes are separate or joint controllers, and need a different agreement.

What Article 28 requires

Article 28(3) requires the contract to set out the subject-matter and duration of the processing, its nature and purpose, the type of personal data, the categories of people concerned, and the obligations and rights of the controller. It must also stipulate, in particular, that the processor:

Article 28(3)The processor mustWhat to look for
(a)Process only on documented instructions, including on transfers outside the EUThe instructions are the contract and its annexes, plus written instructions you give later
(b)Ensure its staff are bound by confidentialityConfidentiality clauses or statutory duty
(c)Take the security measures of Article 32A concrete annex of technical and organisational measures, not a generic promise
(d)Respect the rules on sub-processorsA list of sub-processors and how you are told about changes
(e)Help you answer requests from people exercising their rightsHow export, correction and deletion requests are handled, and how fast
(f)Help you with Articles 32 to 36: security, breach notification, DPIAs, prior consultationBreach notice deadline to you, help with your DPIA
(g)At your choice, delete or return all personal data at the end of the serviceFormat and deadline for return, confirmation of deletion
(h)Give you the information needed to show compliance and allow audits, including inspectionsAudit rights, reports or certificates accepted instead of on-site audits

The processor must also tell you immediately if, in its opinion, an instruction infringes data protection law. Article 28(9) requires the agreement to be in writing, which includes electronic form, so a signed PDF or an accepted online agreement is enough.

The deletion or return clause works only if you know your own periods; see our data retention policy guide. Most SaaS contracts include a DPA; our SaaS guide lists the other clauses to check.

Sub-processors

Most processors use others: a hosting provider, an email delivery service, a support tool. Article 28(2) says a processor may not engage another processor without the controller's prior specific or general written authorisation. With general authorisation, the processor must tell you about intended additions or replacements and give you the chance to object. Article 28(4) requires the processor to impose the same data protection obligations on each sub-processor by contract, and keeps the processor fully liable to you if a sub-processor fails.

In practice, ask for the current sub-processor list with company names, what each does and where it processes data, and agree how many days' notice you get before a new one is added. The country column matters most: it shows whether your data leaves the EU.

The EU standard contractual clauses for processors

Article 28(7) lets the Commission adopt standard clauses for these contracts, and it did so in Implementing Decision (EU) 2021/915 of 4 June 2021. Article 1 of the decision states that the clauses in its annex fulfil the requirements of Article 28(3) and (4). They include, for example, a choice between prior specific authorisation and general written authorisation for sub-processors, with a notice period you fill in, and a clause on helping the controller with breach notifications under Articles 33 and 34. Using them is optional, but they are a neutral starting point that both sides can accept without long negotiation. They are not the same as the separate standard clauses for international transfers.

Transfers outside the EU

A DPA must say whether personal data may leave the EU and on whose instructions (Article 28(3)(a)). The transfer itself needs a legal basis under Chapter V of the GDPR, such as an adequacy decision for the destination country or appropriate safeguards like standard data protection clauses under Article 46. When the hosting, backups and support access all stay in the EU, that whole layer of work and risk disappears, which is one reason we host in EU regions by default.

Common mistakes in DPAs

  • No real description of the processing. The annex says "customer data" instead of listing the data categories, the people concerned and the purposes.
  • Security annex copied from a template. It promises measures the supplier does not run. Ask how each measure is actually done.
  • A liability cap that leaves data protection uncovered. Read the main contract's liability clause together with the DPA.
  • No breach notice deadline. Article 33 asks you to notify the authority without undue delay and, where feasible, within 72 hours of becoming aware; agree that the processor tells you well within that time.
  • No exit clause. Article 28(3)(g) requires deletion or return at your choice. Agree the format of the return, so the data is usable in the next system.
  • Old DPAs that no longer match the service. New features, new sub-processors and new regions should trigger an update.

A checklist for reviewing a DPA

  1. Are the roles right: are you the controller and the supplier the processor?
  2. Does the annex describe the subject-matter, duration, nature, purpose, data types and categories of people?
  3. Are all eight points of Article 28(3)(a) to (h) covered?
  4. Is there a concrete annex of technical and organisational measures?
  5. Is there a sub-processor list with countries, and a notice period for changes with a right to object?
  6. Where is the data hosted and from where is it accessed, and if outside the EU, on what transfer basis?
  7. How fast will the processor tell you about a personal data breach?
  8. How and in what format is data returned or deleted at the end?
  9. Which audit evidence is accepted: reports, certificates, questionnaires, inspections?
  10. Does the main contract's liability clause fit the risk of the data?

Penalties

The obligations of controllers and processors under Articles 25 to 39, which include Article 28, fall under Article 83(4): administrative fines of up to 10 million euro or, for an undertaking, up to 2 % of total worldwide annual turnover of the preceding financial year, whichever is higher. A processor that starts deciding the purposes and means itself is treated as a controller for that processing (Article 28(10)).

How we work with DPAs

When we build or maintain software that handles your personal data, we act as your processor and sign a DPA with you. Our standard setup keeps hosting, backups and support access in EU regions, in accounts in your company's name, so the sub-processor list is short and you can see it. We provide the security annex as it actually runs, help with your data protection impact assessment, and return the data in open formats at the end. You own the code. See how this works in our managed IT services and SaaS development work.

Questions people ask

Is a data processing agreement mandatory?

Yes, whenever a processor handles personal data on behalf of a controller. Article 28(3) of the GDPR requires the processing to be governed by a contract or other legal act that is binding on the processor, and Article 28(9) requires it to be in writing, which includes electronic form. Without it, both parties are in breach.

Is a DPA the same as a data sharing agreement?

No. A DPA covers a processor acting on the controller's instructions. When two organisations each decide their own purposes for the data, they are separate controllers, or joint controllers under Article 26, and they need a different kind of agreement. The label in the contract does not decide this; the facts of who decides the purposes and means do.

Can we just accept the supplier's standard DPA?

Often, yes, for large cloud services where you cannot negotiate. Read it anyway against the Article 28(3) list, check the sub-processor list and the hosting regions, and note the notice period for new sub-processors. For smaller or custom suppliers, you can usually propose your own DPA or the EU standard contractual clauses.

Who signs the DPA, controller or processor?

Both. The controller is the customer that decides why the data is processed; the processor is the supplier that processes it on the customer's behalf. When the processor uses sub-processors, it must sign an agreement with each of them with the same data protection obligations, under Article 28(4).

Does a DPA cover transfers outside the EU?

Not by itself. The DPA must say whether data may be transferred and on whose instructions, but the transfer itself needs a basis under Chapter V of the GDPR, such as an adequacy decision or standard data protection clauses for international transfers. Keeping hosting and support in the EU avoids most of that work.

Sources