What is a Data Processing Agreement (DPA)?
Direct answer
A Data Processing Agreement (DPA) is the written contract GDPR Article 28 requires whenever a controller engages a processor to handle personal data on its behalf. It must bind the processor to obligations covering the subject matter, duration, nature, and purpose of the processing, plus data subject rights assistance, breach notification, DPIA support, sub-processor controls, and audit access.
Without a compliant DPA the processing relationship is unlawful.
What must a DPA contain?
Article 28(3) sets the frame. The contract, or another legal act under EU or member state law, must be binding on the processor and 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. It must then require the processor to:
- process the data only on documented instructions from the controller, including for transfers to a third country, and tell the controller if the law requires otherwise;
- make sure that people authorised to process the data are bound by confidentiality;
- take all the security measures required by Article 32;
- respect the conditions for engaging another processor;
- help the controller answer data subject requests, such as access requests;
- help the controller with security, breach notification, DPIAs and prior consultation (Articles 32 to 36);
- delete or return all the data at the end of the services, at the controller’s choice;
- provide the information needed to demonstrate compliance and allow for audits, including inspections.
The processor must also immediately inform the controller if, in its opinion, an instruction infringes data protection law. The EDPB’s Guidelines 07/2020 add that the agreement should not merely restate the GDPR: it should say concretely how each requirement will be met and what level of security the processing requires.
How do sub-processors work under a DPA?
Under Article 28(2), a processor cannot engage another processor without the controller’s prior written authorisation, which can be specific or general. The EDPB explains the difference:
- Specific authorisation names a sub-processor for a given activity. Any change needs a new authorisation, and a request that goes unanswered within the agreed time counts as refused.
- General authorisation, usually with a list of approved sub-processors in an annex, obliges the processor to inform the controller of any intended addition or replacement so it can object. Silence within the agreed time counts as approval.
Either way, the controller should receive the list of sub-processors with their locations, what they will do and the safeguards in place, and the contract should set the time frame for objections and what happens after one. Each sub-processor must be bound by the same data protection obligations by contract (Article 28(4)), and the initial processor remains fully liable to the controller for the sub-processor’s performance.
Can you use standard clauses or the processor’s own terms?
Both are allowed. Article 28(7) lets the Commission adopt standard contractual clauses for controller and processor contracts, which it did in Implementing Decision (EU) 2021/915 of 4 June 2021, and Article 28(8) lets a supervisory authority adopt its own. The EDPB is clear that there is no obligation to use them: an individually negotiated contract is just as valid, as long as it covers Article 28(3).
Many providers offer a DPA within their standard terms. That is not a problem in itself, but the controller that accepts those terms also accepts full responsibility for their compliance, and an imbalance in negotiating power does not excuse unlawful clauses. Changes the processor proposes must be notified to and approved by the controller; the EDPB states that simply publishing them on the processor’s website does not comply with Article 28. The contract must be in writing, which includes electronic form (Article 28(9)).
A DPA does not cover transfers outside the EEA. Those need a Chapter V transfer tool and usually a transfer impact assessment.
What does the Swiss FADP require of processor contracts?
Article 9 of the revised FADP allows processing to be assigned to a processor by contract or by law if the processor only processes the data in the way the controller itself would be permitted to, and no statutory or contractual duty of confidentiality prohibits the assignment. The controller must satisfy itself in particular that the processor can guarantee data security, and the processor may only assign processing to a third party with the controller’s prior approval.
The FADP does not list mandatory clauses the way Article 28(3) does, so a contract written to the GDPR standard generally gives more detail than Swiss law asks for. Under Article 17(2) of the Data Protection Ordinance, a processor holding the data also helps the controller answer access requests where it does not answer them on its behalf. See the Swiss FADP guide.
How Acuna GRC handles it
Data Privacy in Acuna GRC generates the agreement as a Word document filled from the processing activity, tracks it through Draft, Active and Terminated, and shows a live DPA status on the supplier record in TPRM.
- Module
Data Privacy
Processing activities, data inventory and flows, DPIAs, DPAs, TIAs, data subject requests and breaches, with a public privacy portal.
- Module
TPRM (Supplier Shield)
Suppliers, questionnaires, assessments and campaigns, with a supplier portal and supplier risk intelligence: daily scans condensed into an A to F grade, with breach and sanctions checks.
- Solution
GDPR
Meet GDPR accountability: keep the Art. 30 record current, assess high-risk processing under Art. 35 and prove each request and breach met its deadline.
Sources
- Regulation (EU) 2016/679 (GDPR), Articles 28, 82 and 83(4)
- EDPB Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.0
- Commission Implementing Decision (EU) 2021/915 on standard contractual clauses between controllers and processors
- Federal Act on Data Protection (FADP), Article 9
This page explains the rules in general terms and is not legal advice.
Frequently asked
What happens if a processor uses the data for its own purposes?
Under Article 28(10), a processor that determines the purposes and means of processing in breach of the GDPR is considered a controller for that processing, with all the obligations that brings, without prejudice to fines and liability.
Who is liable to individuals when a processor causes damage?
Under Article 82(2), the controller is liable for damage caused by processing that infringes the GDPR. A processor is liable only where it has not complied with obligations directed specifically to processors or has acted outside or contrary to the controller’s lawful instructions.
What fine applies to a missing or incomplete DPA?
Obligations under Article 28 fall under Article 83(4)(a): fines of up to EUR 10 000 000 or, for an undertaking, up to 2 % of total worldwide annual turnover of the preceding financial year, whichever is higher. They can apply to the controller and to the processor.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

