Data Processing Agreements
Article 28 GDPR agreements drafted, reviewed and negotiated for controllers and processors, including sub-processors and international transfers.
Pitch drafts and reviews data processing agreements. We establish who decides why the data is processed, check each clause against what the GDPR requires and what the supplier actually does, and propose changes in order of importance. We also check the transfer basis when data leaves the EEA and enter the processor in your register.
- By
- By Bart Lieben, Attorney-at-Law
- Published
- Updated
- 360 stage:
- Protect
Part of your goal: Grow your business, Contract, GDPR and privacy
The question
A supplier sends you its data processing agreement with a request to sign. A customer asks you to sign theirs. You have to judge whether it is adequate and what to ask to change.
Article 28 GDPR requires a binding contract whenever a processor handles personal data on behalf of a controller. The contract must set out the subject matter, duration, nature and purpose of the processing, the type of personal data and the categories of data subjects. It must oblige the processor to act only on documented instructions, to ensure confidentiality, to apply the security measures of Article 32, to respect the conditions for engaging sub-processors, to assist with data subject requests and with breach notification and impact assessments, to delete or return data at the end, and to allow audits.
Most agreements on the market contain those clauses. The problems lie elsewhere: a vague description of the processing, a security annex that says nothing, a sub-processor list nobody maintains, a transfer clause that no longer matches reality, or a role that is wrongly qualified. A processor that decides on purposes and means itself becomes a controller (Article 28(10)), and two parties who decide together are joint controllers under Article 26, which needs a different arrangement.
Our approach
We begin with the relationship. We establish who decides why the data is processed, and which data, systems, sub-processors and countries are involved. That determines whether you need a controller-to-processor agreement, a joint controller arrangement or a controller-to-controller allocation.
We then draft or review. For your own agreements we use our Document Studio, which builds the document from a fixed structure and our clause library and produces a Word file in the house style. For a supplier's agreement we check each clause against Article 28(3) and against what the supplier does, and we propose changes in order of importance, so that you negotiate on the points that matter.
Where data leaves the European Economic Area, we check the transfer basis: an adequacy decision, the standard contractual clauses or another instrument, together with the assessment that goes with it. International data transfers explains the framework. The agreement should also state retention and deletion in a way that can be carried out (see how long personal data may be kept).
Then we connect the agreement to your records. The processor and the agreement are entered in your register, which is what Article 30 expects, and renewal and sub-processor changes are followed on the compliance calendar. A lawyer reviews every agreement before it is sent or signed.
Typical triggers are a new SaaS or cloud supplier, a large customer that sends its own DPA as a condition of the contract, a supplier audit that finds agreements missing for half of your processors, a move of hosting to a provider outside the EEA, or the preparation of a financing round or sale in which the buyer asks for your data protection documents.
What you get
- A processing agreement with annexes that describe the real processing, the security measures, the sub-processors and the transfers.
- For supplier agreements: a clause-by-clause review with a prioritised list of requested changes and, where useful, our negotiation with the other side.
- A short note on the roles of the parties (controller, processor, joint controllers) and why.
- Documents prepared for your own recurring use, so that your team does not start from a blank page each time.
- The processor entered in your register with the agreement attached.
Limits apply. An agreement cannot repair processing that has no lawful basis, and a clause cannot make a transfer lawful if the destination country's law undermines it. We will tell you when the answer lies outside the contract.
A Leuven software company hosts customer data with a cloud provider and uses a support-ticket tool from a US vendor. Both vendors sent standard DPAs. Our review found that the cloud provider's agreement allowed sub-processors to be added with notice only after the event and gave no audit right, and that the support vendor's annex listed data categories the company never sends. We proposed prior notice with a right to object, an audit clause limited to reports and certificates, a corrected annex and a fallback to standard contractual clauses. The vendors accepted most points, and the final versions were entered in the register with their sub-processor lists.
Next step
Send us the agreement you are asked to sign, or a list of the suppliers who process personal data on your behalf. We will tell you what needs to change and what can stay.
In short
- Article 28 GDPR agreements that fit the real processing
- Review and negotiation of supplier DPAs
- Sub-processing chains and transfers addressed
- Linked to your record of processing
- Reviewed by a lawyer
Frequently asked questions
When do I need a data processing agreement?
Whenever a processor handles personal data on behalf of a controller, the GDPR requires a binding contract. Typical triggers are a new SaaS or cloud supplier, or a large customer that sends its own agreement as a condition of the contract. The contract must describe the processing and bind the processor to documented instructions.
What must the agreement contain?
The subject matter, duration, nature and purpose of the processing, the type of personal data and the categories of data subjects. The processor must act only on documented instructions, keep data confidential, apply security measures, respect conditions for sub-processors, assist with requests and breaches, delete or return data at the end, and allow audits.
What usually goes wrong in these agreements?
Most contain the required clauses. The problems are a vague description of the processing, a security annex that says nothing, a sub-processor list nobody maintains, a transfer clause that no longer matches reality, or a wrongly qualified role. A processor that decides on purposes and means itself becomes a controller.
What if my supplier is outside the EEA?
Then you need a transfer basis, such as an adequacy decision or the standard contractual clauses, together with the assessment that goes with it. A clause cannot make a transfer lawful if the destination country's law undermines it, so we tell you when the answer lies outside the contract.