Last updated: November 8, 2026
Reviewed by a privacy professional (CIPP/US) on November 10, 2026.
A data processing agreement (DPA) is the contract that governs how a vendor handles personal data for you. The EU and UK GDPR make one mandatory whenever you use a processor, and Article 28 spells out its contents. In the US, California’s CCPA regulations and Virginia-style state privacy laws demand similar contracts with service providers and processors.
Short answer: A data processing agreement is a written contract between a controller (the business that decides why and how personal data is used) and a processor (the vendor that handles that data for the controller). GDPR Article 28 says it must cover processing only on documented instructions, confidentiality, security, sub-processors, help with individuals’ rights, deletion or return at the end, and audits. US state privacy laws call for similar terms.
Key takeaways
- GDPR Article 28(3) lists eight required processor obligations, labeled (a) to (h).
- Processors need the controller’s prior specific or general written authorization to use sub-processors.
- The initial processor stays fully liable to the controller for a sub-processor’s failures.
- Section 7051 of California’s CCPA regulations lists 10 required terms for service provider and contractor contracts.
- Virginia, Colorado, Connecticut and many newer state privacy laws require controller-processor contracts sharing a common core of terms.
Table of Contents
What a data processing agreement is
A data processing agreement, usually called a data processing addendum when it’s attached to a main services contract, lays down the rules for a vendor processing personal data on your behalf. Common examples:
- A payroll provider processing employee data.
- A CRM or email marketing platform storing customer contacts.
- A cloud host storing an app’s user database.
- An analytics or support tool that sees customer information.
Whoever decides the purposes and means of processing is the controller (in California’s terms, the business). The vendor processing data for it is the processor (in California, the service provider or contractor).

When the GDPR requires a data processing agreement
The GDPR and UK GDPR require any controller using a processor to have a contract or other legal act in place. The text of GDPR Article 28 adds:
- Controllers may use only processors that provide sufficient guarantees of appropriate technical and organizational measures.
- The contract must be in writing, and electronic form counts.
- A processor that starts deciding the purposes and means of processing becomes a controller for that processing.
The contract also has to describe the subject matter and duration of the processing, its nature and purpose, the types of personal data, the categories of data subjects, and the controller’s obligations and rights.
The eight required GDPR terms
Article 28(3) requires the processor to:
| Clause | What the processor must do |
|---|---|
| (a) | Process personal data only on documented instructions from the controller, including for international transfers, unless law requires otherwise |
| (b) | Make sure people authorized to process the data are bound by confidentiality |
| (c) | Take all security measures required by Article 32 |
| (d) | Follow the conditions for engaging sub-processors |
| (e) | Help the controller respond to data subject rights requests |
| (f) | Help the controller meet its obligations under Articles 32 to 36, such as security, breach notification and impact assessments |
| (g) | Delete or return all personal data at the end of the services, at the controller’s choice, unless law requires storage |
| (h) | Provide information needed to demonstrate compliance and allow audits and inspections |
Article 28 further requires the processor to tell the controller right away if it believes an instruction violates data protection law.
Sub-processors
Most vendors rely on other vendors for cloud hosting, email delivery or support tools. Article 28(2) and (4) govern that:
- Authorization: the processor needs the controller’s prior specific or general written authorization to engage a sub-processor.
- Notice and objection: with general authorization, the processor must tell the controller about intended changes so the controller can object.
- Flow-down: sub-processors must be bound by the same data protection obligations.
- Liability: if a sub-processor fails, the initial processor remains fully liable to the controller.
In practice, vendors post a sub-processor list and offer email or webhook alerts about changes. Controllers should sign up and actually read those alerts.
International transfers in a GDPR DPA
When a processor or sub-processor handles EU or UK personal data outside those regions, the DPA needs a transfer mechanism. The usual options are the European Commission’s standard contractual clauses, the UK’s international data transfer agreement or addendum, and, for certified US companies, the EU-US Data Privacy Framework. Most vendor DPAs pull in the relevant clauses by reference, with annexes describing the processing.
CCPA service provider contracts
California is more prescriptive. Under section 7051 of the CCPA regulations, a contract with a service provider or contractor must:
- Prohibit selling or sharing personal information.
- Identify the specific business purposes, not in generic terms.
- Prohibit use for any other purpose, except as the law allows.
- Prohibit use for any other commercial purpose.
- Prohibit use outside the direct business relationship, such as combining it with data from other sources, unless expressly permitted.
- Require compliance with the CCPA and the same level of privacy protection required of businesses.
- Give the business the right to take reasonable steps to confirm proper use, which may include assessments at least once every 12 months.
- Require notice if the provider can no longer meet its obligations.
- Give the business the right to stop and remediate unauthorized use.
- Enable the business to handle consumer requests, or require the business to pass requests and information to the provider.
The regulation also warns that a business that never enforces its contract or uses its audit rights may be unable to argue it had no reason to believe the provider was misusing data.

Other US state privacy laws
Most comprehensive state privacy laws copy the Virginia model. A Seyfarth Shaw analysis from May 2026 says laws in Virginia, Colorado, Connecticut and most later states require written controller-processor contracts that cover:
- Processing instructions, the nature and purpose of processing, the type of data and the duration.
- A duty of confidentiality for processor personnel.
- Flow-down to subcontractors, typically with notice and a chance to object.
- Assistance with consumer requests, assessments, breach notification and security.
- Audit, inspection or assessment rights.
- Deletion or return of data at the end.
These terms overlap heavily with GDPR Article 28, so a single well-drafted data processing agreement with jurisdiction-specific riders can handle most laws.
What a strong data processing agreement includes
Past the legal minimums, strong DPAs also cover:
- Breach notice timing: a specific window for the processor to notify you, short enough for you to meet your own deadlines.
- Security annex: a description of technical and organizational measures, such as encryption, access controls and testing.
- Audit mechanics: whether third-party reports such as SOC 2 satisfy audit rights, and when on-site audits are allowed.
- AI and model training: whether the vendor may use your data to train or improve models, which many customers now prohibit by default.
- Deletion certification: written confirmation that data was deleted at the end.
- Liability and indemnity: how data protection claims interact with the main contract’s liability caps.
- Order of precedence: which document wins if the DPA and the main agreement conflict.
Worked example: reviewing a vendor’s DPA
Take a hypothetical US software company with EU customers that’s signing up for a customer support platform.
- Roles: the software company is the controller for customer support data; the platform is a processor.
- Article 28 check: the vendor’s DPA covers all eight required terms, but its breach notice clause says “without undue delay” with no time limit. The company asks for 48 hours.
- Sub-processors: the vendor lists 14 sub-processors, including an AI provider. The company subscribes to change notices and confirms the AI provider can’t train on its data.
- Transfers: the DPA incorporates the EU standard contractual clauses with completed annexes.
- California: the company’s California customers’ data is also in scope, so it confirms the DPA includes the CCPA service provider terms or adds a CCPA rider.
- Audits: it accepts the vendor’s annual SOC 2 report in place of on-site audits, with the right to ask follow-up questions.
Controller vs processor: getting the roles right
A data processing agreement fits only when the vendor is a processor, and misjudging the roles produces the wrong contract:
- Processor: processes data on your instructions for your purposes, such as a cloud host, payroll platform or email service.
- Independent controller: decides its own purposes for the data, such as some professional advisers, payment networks or a marketing partner using data for its own ends. A data sharing agreement, not a DPA, usually fits.
- Joint controllers: two parties that decide purposes and means together. The GDPR requires an arrangement setting out their respective responsibilities under Article 26.
Article 28 itself warns that a processor that begins determining purposes and means turns into a controller for that processing. Vendors reusing customer data for their own product development can cross that line.
The UK and Canada
The UK GDPR keeps Article 28 in substantially the same form, so a GDPR-compliant data processing agreement usually works for UK data once UK-specific transfer terms are added. In Canada, PIPEDA’s accountability principle holds organizations responsible for personal information they hand to a third party for processing and expects contractual or other means to provide a comparable level of protection. A DPA is the normal way to meet that.
Negotiating a vendor’s data processing agreement
Big vendors seldom change their standard DPA, but many accept targeted edits or side letters. Put your effort into:
- Breach notice: a fixed number of hours instead of “without undue delay.”
- No-training language: a clear statement that your data won’t be used to train or improve models.
- Sub-processor notice: advance notice with a real objection right and, if needed, a termination right.
- Audit: acceptance of independent reports plus the right to ask follow-up questions.
- Liability: whether data protection breaches sit inside or outside the main liability cap.
A data processing agreement checklist
Run through this list when reviewing any data processing agreement:
- Parties and roles are correct: controller and processor, or business and service provider.
- Subject matter, duration, nature, purpose, data types and data subjects are described.
- Processing is limited to documented instructions and specific business purposes.
- Confidentiality, security measures and a security annex are included.
- Sub-processor authorization, notice and flow-down terms are clear.
- Assistance with rights requests, assessments and breach notification is required.
- Breach notice has a defined deadline.
- Deletion or return at the end is required, with certification.
- Audit or assessment rights are defined.
- Transfer mechanisms are in place for EU and UK data.
- CCPA and other state riders are included where needed.
- AI training and new AI sub-processors are addressed.
Managing data processing agreements at scale
A company with dozens or hundreds of vendors needs a system, not a folder of PDFs:
- Keep a vendor register listing each vendor, the personal data it handles, its role, the signed data processing agreement and the date it was last reviewed.
- Tie the DPA to procurement, so no vendor gets personal data until the agreement is signed.
- Track sub-processor notices in one shared inbox or ticket queue with an owner.
- Review high-risk vendors yearly, including security reports and any new AI features.
- Store transfer documents such as completed SCC annexes with the agreement.
- Plan exits: confirm deletion or return when a contract ends, and keep the certificate.
That turns the data processing addendum from a one-off signature into the ongoing oversight both GDPR Article 28 and California’s rules expect.
Common data processing agreement mistakes
- Not signing one at all because a vendor’s terms “mention privacy.”
- Accepting generic business purposes that fail California’s specificity rule.
- Ignoring sub-processor notices after signing.
- Missing transfer mechanisms for data leaving the EU or UK.
- No breach notice deadline, leaving you unable to meet your own.
- Never exercising audit rights, which California says can undercut your defenses.

For security due diligence that pairs with a DPA, see our AI vendor questionnaire guide and our explainer on SOC 2 Type 1 vs Type 2.
Our Take / Expert Perspective
Our take: the data processing agreement has quietly turned into one of the most important documents in vendor management, yet most companies still treat it as boilerplate.
On paper, DPAs look standardized: Article 28 sets the core, and US state laws borrow much of it. The real value sits in what the law leaves open: breach notice timing, sub-processor controls, audit mechanics and, more and more, whether a vendor can train AI models on your data. Those clauses decide what happens when something goes wrong.
AI is where the pressure lands next year. Vendors are adding AI features and AI sub-processors quickly, and many DPAs signed two or three years ago never anticipated them. Controllers that don’t watch sub-processor changes may find customer data flowing to model providers they never assessed. We expect more customers to add explicit no-training clauses and AI-specific sub-processor approvals; that’s a forecast from what buyers are asking for, not a legal requirement.
California’s regulation adds an enforcement twist: a contract you never enforce may not protect you, which turns the DPA from a signature into an ongoing process.
Our recommendation: list every vendor that touches personal data, confirm each one has a current DPA with a breach notice deadline and no-training language, and name someone to review sub-processor change notices every month.
Frequently Asked Questions
What is a data processing agreement?
It’s a contract between a controller and a processor setting out how the processor may handle personal data for the controller. Under the GDPR it has to include the Article 28 terms, and US state privacy laws require similar contracts.
Is a data processing agreement required by law?
Yes, under the GDPR and UK GDPR, whenever a controller uses a processor. California’s CCPA regulations and many US state privacy laws also require written contracts with service providers and processors containing specific terms.
What’s the difference between a DPA and a data processing addendum?
Usually they mean the same thing. “Addendum” just signals that the data terms are attached to a main services agreement instead of standing alone.
Who signs a data processing agreement?
The controller, the business that decides why and how personal data is processed, and the processor, the vendor processing it on the controller’s behalf. Processors also sign similar agreements with their own sub-processors.
Does a DPA need standard contractual clauses?
Only when personal data covered by the GDPR or UK GDPR goes to a country without an adequacy decision and no other transfer mechanism applies. That’s why many vendor DPAs include the clauses by reference.
What happens if I don’t have a DPA?
Under the GDPR, missing processor contract obligations can bring regulatory fines and complaints. Under California’s rules, a business lacking proper service provider terms may face enforcement, and one that never enforces its contract may lose a key defense.
This article is for general information only and is not legal advice. Laws differ by state, province and country; consult a qualified attorney for your situation.
Sources
- GDPR-Info: Article 28 GDPR, Processor, checked November 8, 2026
- Prighter: CCPA Regulations section 7051, contract requirements for service providers and contractors, checked November 8, 2026
- Seyfarth Shaw via Mondaq: The paper trail: state privacy law contracting requirements, checked November 8, 2026
- California Privacy Protection Agency: Regulations, checked November 8, 2026
- aiandblog: Editorial Policy
Photos: FlyD, Andras Vas, Jefferson Santos and Dane Deaner on Unsplash.








Leave a Reply