Article
5 mins read
Updated on 7 September 2022
Our subject expert
Becky White
Senior Solicitor - Data Protection & Privacy
Data processing agreements (DPAs) are no longer box-ticking paperwork. Whenever a supplier or cloud platform handles your personal data, regulators, customers and investors look for a signed, fully-compliant DPA as shorthand that your business takes data protection seriously. Get it wrong and deals can stall, trust can evaporate and the ICO can reach for its fine calculator.
This FAQ is for founders, operations, and compliance leaders who need to draft or review DPAs without drowning in legalese. We’ll unpack the mandatory Article 28 clauses, flag negotiation flashpoints (from sub-processing chains to liability caps) and give you a practical checklist you can plug straight into your vendor-due-diligence process — helping you speed up onboarding, cut compliance risk and showcase robust data governance.
Need an expert eye on a supplier contract? Talk to our data protection solicitors about tailoring a watertight DPA that keeps both you and your processors compliant.
A Data Processing Agreement (DPA) is a contract that is usually entered into between the Controller and the Processor.
A Controller is a natural or legal person, public authority, agency, or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data (Article 4(7) of the GDPR). Essentially Controllers make decisions about processing activities.
A Processor is a natural or legal person, public authority, agency, or other body which processes personal data on behalf of the controller (Article 4(8) of the GDPR). Essentially Processors act on behalf of the Controller and under their instructions and authority.
In short, it’s whenever a Processor conducts any processing on your behalf. According to the Information Commissioners Office, contracts between controllers and processors ensure they both understand their obligations, responsibilities, and liabilities. Contracts also help them comply with the UK GDPR, and assist controllers in demonstrating to individuals and regulators, their compliance as required by the accountability principle.
If your organisation is subject to the General Data Protection Act (GDPR), then it’s pertinent to have in place a DPA with all your data processors. Article 28 of the GDPR sets out what should be included within the DPA (see below; “what are the common clauses?”).
Should a Processor use another company to assist in processing activities for the Controller client, it would need to ensure it has a DPA (DPA – Processor to Sub-Processor) in place with that Sub-Processor. The terms of that DPA should offer an equivalent level of protection for the personal data as does the initial DPA between the Controller client and the initial Processor. It’s the Processor’s responsibility that any other Sub-Processor(s) in the chain complies with the requirements of the GDPR and conform to the same level of protection as the initial Controller and Processor. A Processor may not instruct a Sub-Processor without the Controller client’s prior specific or general written authorisation.
The DPA would explain the responsibilities, liabilities, and obligations for all involved parties to the said agreement to act upon, to ensure processing tasks are carried out in accordance with the UK GDPR. DPA’s also assist in demonstrating compliance as per the accountability principle.
Article 28(3) of the GDPR sets out the clauses required in a DPA: -
Furthermore, a DPA should stipulate:-
The above are the minimum requirements essential in a DPA, but a DPA would not be complete without the relevant annexes, which would include the following:
You should never blindly accept the Processor’s version of DPA, the same way a Processor would never accept the Controller’s version of DPA. Like any contract, the drafting party would always draft in a way that it’s pro-them. Whilst the above clauses must be contained in the DPA, it’s necessary to check the details of the clauses. For example, how would you know the technical measures that the Processor has put in place are appropriate to the personal data they are processing for you? It’s likely that you would want a cyber security professional to cast an eye over these. There may be other due diligence that you may wish to conduct, such as checking if any breaches have previously occurred, when and how, as well as any preventative measures put place, so this doesn’t happen again. If this is an area of concern, here we discuss in more detail what to do if your supplier has a data breach.
Whether you are the Controller needing a Processors’ DPA to be checked, or a Processor needing the Controllers version to be checked, our specialist data protection solicitors can assist in evaluating the actual risk against the nature and purpose of processing and provide specific advice in drafting of templates or checking DPA’s from the otherside to ensure they are satisfactory to the level of risk.
About our expert
Senior Solicitor - Data Protection & Privacy
Becky is a highly experienced data protection solicitor who qualified in 2002. She helps growth-focused businesses navigate data protection law with confidence, turning compliance from a burden into a genuine competitive advantage. Becky understands both the legal requirements and the real-world pressures her clients face, building privacy compliance programmes that are commercially fit for purpose.
Commercial Contracts Data Breaches & Incident Management Data Governance Data Processing Agreements Data Protection & Privacy Law Data Protection Health Check Data Protection Impact Assessments and 10 more...
21 May
How to create a data protection complaints process...
17 June
What is a data processing agreement?...
17 June
Your guide to data sharing agreements...
16 June
Data protection compliance and monitoring staff...
16 June