A client asks you to sign a data processing agreement (DPA) when you will handle personal data on their behalf, such as their customers' emails or their users' accounts. That usually makes you a processor under GDPR, and Article 28 says the agreement must cover a fixed list of points. Most of the list is standard; the risk sits in what clients add on top of it.
You are a processor when you handle personal data only to deliver a service to the client, following their instructions: building a newsletter list, maintaining a customer database, running support for their users. If you decide for yourself why the data is used, or the essentials of how (which data, for how long, who receives it), you are a controller for that data instead, alone or jointly with the client, and an Article 28 DPA is the wrong document. Choosing your own tools and methods does not on its own make you a controller.
The agreement must describe the processing: its subject matter, duration, nature and purpose, the types of personal data and the categories of people concerned, and the client's rights and obligations. It must then commit you to process only on the client's documented instructions, including on any transfer outside the EU, keep the people working on the data bound to confidentiality, and apply appropriate security measures under Article 32.
It must also cover sub-processors, which means the tools you use to do the work, such as hosting, email or file storage; helping the client answer people's data requests; helping the client meet its own duties on security, breach notification and impact assessments; deleting or returning the data when the work ends; and giving the client the information they need to verify compliance, including allowing audits and inspections. If a clause on that list is missing, the draft is incomplete, and asking for it protects you both.
The required clauses are the easy part. Read what the client added after them.
Unlimited liability. Many client templates make the processor liable without a cap. Ask for a cap tied to the contract value or your insurance cover. A cap only limits what you owe the client; it cannot limit what the people whose data it is can claim under GDPR Article 82.
Breach deadlines you can't meet. GDPR Article 33(2) asks processors to notify the controller without undue delay after becoming aware of a breach. The client has its own 72-hour deadline to tell the authority, so a fixed window such as 24 or 48 hours from confirming a breach is a fair counter-offer. A template that demands notice within a few hours of any suspected incident, at any time of day, sets a bar a one-person business will miss.
Audits at your cost. Article 28 requires you to allow and contribute to the client's audits, including inspections, but on-site audits on short notice at your expense are a negotiation point. Offer documentation first and audits with reasonable notice.
List the tools that will touch the client's data and check that the DPA allows them, either by name or through a general authorisation with notice of changes and a chance to object. Make sure the security measures annex describes what you actually do, not an enterprise standard you don't meet.
This is general information, not individualised legal advice. If the client's template is long or one-sided, a short review by a professional costs less than the liability you would otherwise accept.
This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.
← Back to blog