A privacy policy tells the people whose data you collect what you do with it. A Data Processing Agreement, DPA, does something different: it’s a contract between two businesses that governs what a vendor is allowed to do with personal data you hand it. The two documents get confused constantly, partly because both use the same vocabulary, controller, processor, personal data, and partly because a lot of businesses only discover they need a DPA when a customer’s procurement team asks for one during contract review. This guide covers what a DPA actually is, which laws require one and when, what has to be in it, and how it’s different from the privacy policy you probably already have.
A DPA is a contract, not a disclosure
Your privacy policy is a one-to-many disclosure: one document, published once, read by anyone visiting your site, describing your own data practices toward your own users or customers. A DPA is a one-to-one contract: negotiated or accepted between exactly two businesses, governing one specific vendor relationship, and it’s usually never published publicly at all, it lives as an executed document, often incorporated into a master services agreement or signed as an addendum.
The relationship a DPA governs is also structurally different from the one a privacy policy describes. A privacy policy speaks in the voice of a controller, the business that decides why data is collected and what happens to it, addressing the data subject directly. A DPA speaks between a controller and a processor, the vendor that only touches the data because the controller instructed it to, for a purpose the controller defined, not one the processor chose on its own. If your company runs a SaaS product, you’re very likely in both roles at once: a processor to your customers (for whatever data they put into your product), and a controller relative to your own subprocessors (the vendors your product depends on). Our privacy policy guide for B2B SaaS companies covers that dual role in more depth, since it’s the source of a lot of confusion about which document says what.
Privacy policy vs DPA
| Privacy policy | DPA | |
|---|---|---|
| Audience | The public, data subjects | One named vendor or customer |
| Legal form | Disclosure | Contract |
| Published where | Public URL | Executed, usually private |
| Relationship covered | Controller to data subject | Controller to processor |
| Changes when | Your practices change | A vendor relationship starts or changes |
Who is the controller and who is the processor
Every DPA exists because two businesses are playing two different roles over the same personal data, and getting those roles right is the first step, because the whole rest of the agreement flows from it.
The controller decides why data is processed and what it’s used for. If you run an email marketing platform and a bakery signs up to send newsletters to its customer list, the bakery is the controller of that customer list: it decided to collect those email addresses, and it decides what they get used for. The processor acts on the controller’s instructions and doesn’t independently decide the purpose. In that same example, your email platform is the processor: you’re storing and sending to that list because the bakery told you to, not because you decided on your own that its customers should receive a newsletter.
This distinction matters because obligations attach differently to each role. Article 24 of GDPR puts the primary compliance burden on the controller, since the controller is the one who decided data should be collected in the first place. But Article 28 requires that whenever a controller uses a processor, that relationship has to be governed by a contract, specifically one containing the terms Article 28(3) lists out. That contract is the DPA. Without it, a controller handing data to a vendor is, technically, in violation of GDPR regardless of how secure or well-intentioned that vendor actually is, because the law requires the contractual safeguard to exist, not just the good behavior.
The independent-controller branch is worth pausing on, because it’s the case people miss most. Not every vendor that touches your data is a processor. A payment processor that runs its own fraud-screening program using your transaction data for its own risk-modeling purposes, separate from just authorizing your specific charge, may be acting as an independent controller for that use, not your processor. The test isn’t “does this company have access to personal data,” it’s “does this company decide, on its own, why that data gets used this way.” Get that wrong and you’ll either sign a DPA with a vendor that doesn’t need one, or skip one with a vendor that does.
When GDPR actually requires a DPA
GDPR Article 28(3) requires a written contract, the DPA, whenever a controller engages a processor to handle personal data on its behalf, with no minimum size or volume threshold. A five-person startup using a single email delivery vendor needs one exactly as much as an enterprise using a hundred vendors, because the requirement attaches to the relationship, not the scale of the business. That written contract has to specify, at minimum: the subject matter and duration of the processing, the nature and purpose of the processing, the type of personal data and categories of data subjects involved, and the obligations and rights of the controller.
Article 28(3) then lists specific clauses the contract has to contain. The processor must process data only on the controller’s documented instructions, including for international transfers, unless required to do otherwise by law. Anyone authorized to process the data has to be bound by confidentiality. The processor has to implement appropriate security measures under Article 32. The processor can’t engage a subprocessor without the controller’s prior authorization, general or specific, and if general authorization is given, the processor has to inform the controller of any intended changes so the controller has the chance to object. The processor has to assist the controller with data subject rights requests, with security obligations, and with breach notification. At the end of the relationship, the processor has to delete or return all personal data, at the controller’s choice. And the processor has to make available the information necessary to demonstrate compliance and allow for audits.
That’s a specific, non-negotiable checklist, not a general suggestion to “be careful with data.” A services agreement that says a vendor will “handle data responsibly” or “in accordance with applicable law,” without covering these specific points, doesn’t satisfy Article 28(3), no matter how good the vendor’s actual security practices are.
When CCPA (and similar US state laws) require one
CCPA uses different terminology, “business” instead of controller and “service provider” instead of processor, but the underlying structure is close enough that the same logic applies. Under CCPA, a business that shares personal information with a service provider needs a written contract that restricts the service provider to using that data only for the specific business purposes specified in the contract, prohibits the service provider from selling or sharing the data, and prohibits combining it with data from other sources except in specific permitted cases. Without that contract, and without the service provider actually operating within its terms, a transfer of personal information to a vendor can be treated as a sale or share under CCPA, which pulls in a much heavier compliance burden, including opt-out rights, that a properly contracted service-provider relationship doesn’t trigger.
Most other US comprehensive state privacy laws, Virginia, Colorado, Connecticut, and the rest, follow the same processor-contract pattern GDPR established, sometimes calling the vendor a “processor” directly and requiring substantially similar contract terms: purpose limitation, confidentiality, security obligations, subprocessor authorization, and assistance with data subject rights and deletion. If your DPA is built around Article 28’s requirements, it covers most of what these state laws separately require, though it’s worth confirming your specific document actually names the state laws you’re subject to rather than referencing GDPR alone. If you’re not sure which of these laws applies to your business in the first place, our guide to CCPA vs GDPR applicability walks through each law’s actual coverage test.
What has to be in the document itself
Putting the Article 28(3) list and the equivalent state-law requirements together, a working DPA needs to cover several groups of terms.
Party and scope terms identify the controller and processor by name and address, describe the subject matter, duration, nature, and purpose of the processing, and specify the categories of personal data and data subjects involved, ideally with enough detail that an auditor could confirm the processing matches what’s actually happening rather than a generic description that could apply to any vendor relationship.
Instruction and confidentiality terms bind the processor to act only on the controller’s documented instructions, and bind anyone with access to the data to confidentiality obligations, whether through employment terms or a separate confidentiality agreement.
Security terms require the processor to implement technical and organizational measures appropriate to the risk, often referencing a specific standard or certification (SOC 2, ISO 27001) as evidence, plus a defined breach notification timeframe, since “notify the controller promptly” reads very differently in a contract than “notify the controller within 72 hours,” and the second version is the one that actually lets the controller meet its own 72-hour regulatory notification clock under GDPR Article 33.
Subprocessor terms require the controller’s authorization, general or specific, before the processor engages any subprocessor, and a mechanism (usually a published list plus a notice period) for the controller to be informed of, and object to, new subprocessors.
Assistance and audit terms require the processor to help the controller respond to data subject rights requests and to demonstrate compliance, typically through audit rights or the right to request evidence like a SOC 2 report rather than an on-site audit for every customer.
International transfer terms specify the legal mechanism, most commonly the EU’s Standard Contractual Clauses, used to justify moving data outside the EEA or UK if the processor operates or stores data outside those regions.
End-of-relationship terms require deletion or return of all personal data once the processing relationship ends, at the controller’s choice, and specify the timeframe.
- Vendor will handle customer data responsibly and in accordance with applicable law.
- No named subprocessors, no deletion terms.
- Processing limited to documented instructions, with a named subprocessor list.
- Breach notice within a set number of hours; deletion or return at contract end.
Getting the DPA in place
Most vendors that regularly handle other businesses’ data as processors, hosting providers, email platforms, analytics tools, customer support software, keep a standard DPA ready to sign or click-accept, often incorporating the EU Standard Contractual Clauses by reference for international transfers. If you’re the vendor rather than the customer in a given relationship, having your own standard DPA ready, rather than negotiating one from scratch every time a customer’s procurement team asks, is usually what keeps a security review from stalling a deal. Our Data Processing Agreement generator builds one from the same underlying Article 28 requirements covered here, party details, processing purpose and data categories, security measures and breach notification timeframe, subprocessor authorization, and international transfer mechanism, so the document actually contains the specific clauses reviewers check for instead of a generic confidentiality paragraph repurposed from somewhere else.
Once the DPA exists, it isn’t a one-time signature. Any time the processing relationship changes, a new subprocessor gets added, data categories expand, retention periods shift, the DPA needs to reflect that change, the same discipline that a privacy policy’s retention section requires, as covered in our GDPR data retention guide. A DPA that accurately described a vendor relationship two product changes ago isn’t compliant today just because it was compliant when it was signed.
The information in this article is for informational purposes only and should not be construed as legal advice on any matter, and does not create a lawyer-client relationship.


![Biggest GDPR Fines of All Time: Top 50 Ranked [2026]](/_astro/biggest-gdpr-fines-all-time.CXlfdvkK_r9ma0.webp)



