Free Data Processing Addendum (DPA) Template
A data processing addendum for vendors processing personal data, covering instructions, security, subprocessors, breach notice, assistance, deletion and audits.
A data processing addendum (DPA) sets the rules for a vendor that processes personal data on a customer's behalf: only on instructions, with security, approved subprocessors, breach notification, help with individuals' requests, and deletion at the end. Many US state privacy laws and the GDPR require such terms.
Fill in this template online
Answer the blanks, choose the options, see a live preview and download your completed document. Free, no account needed.
DATA PROCESSING ADDENDUM
This Data Processing Addendum ("DPA") forms part of the [AGREEMENT NAME] dated [DATE] ("Agreement") between [CUSTOMER LEGAL NAME] ("Customer") and [VENDOR LEGAL NAME] ("Processor").
1. DEFINITIONS. "Personal Data" means information relating to an identified or identifiable individual that Processor processes for Customer under the Agreement. "Data Protection Laws" means all privacy and data protection laws that apply to the processing, including US state consumer privacy laws such as the California Consumer Privacy Act as amended, and, where applicable, the EU and UK GDPR. "Security Incident" means a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data.
2. ROLES AND SCOPE. Customer is the controller (or business) and Processor is the processor (or service provider or contractor). Details of the processing are in Annex 1.
3. INSTRUCTIONS. Processor will process Personal Data only on Customer's documented instructions, including the Agreement, and only to provide the services. Processor will inform Customer if it believes an instruction violates Data Protection Laws.
4. RESTRICTIONS. Processor will not: sell or share Personal Data; retain, use or disclose it for any purpose other than performing the services, including training machine learning models; combine it with other data except as permitted by Data Protection Laws; or process it outside the direct business relationship with Customer. Processor certifies that it understands and will comply with these restrictions.
5. CONFIDENTIALITY. Processor will ensure that personnel authorised to process Personal Data are bound by confidentiality obligations.
6. SECURITY. Processor will implement appropriate technical and organisational measures described in Annex 2, including encryption in transit and at rest, access controls, logging, vulnerability management and staff training.
7. SUBPROCESSORS. Customer authorises the subprocessors listed in Annex 3. Processor will give at least [30] days' notice of new subprocessors, and Customer may object on reasonable data protection grounds; if unresolved, Customer may terminate the affected services with a refund of prepaid fees. Processor will impose data protection terms on subprocessors at least as protective as this DPA and remains liable for their performance.
8. SECURITY INCIDENTS. Processor will notify Customer without undue delay, and within [48] hours, after becoming aware of a Security Incident, providing the information reasonably available about its nature, scope, affected data and remediation, and will cooperate with Customer's investigation and any required notifications.
9. ASSISTANCE. Processor will assist Customer, taking into account the nature of processing, in responding to individuals' requests to exercise rights (access, deletion, correction, portability, opt-out), and with data protection assessments and consultations with regulators.
10. DELETION OR RETURN. On termination of the services, Processor will, at Customer's choice, return or delete all Personal Data within [30] days, and certify deletion on request, except where retention is required by law, in which case it remains protected by this DPA.
11. AUDITS. Processor will make available information reasonably necessary to demonstrate compliance, including its most recent [SOC 2 Type II report / ISO 27001 certificate]. Customer may conduct an audit once per year on [30] days' notice, or after a Security Incident, at Customer's cost, subject to confidentiality.
12. INTERNATIONAL TRANSFERS. Processor will not transfer Personal Data outside [the United States / the EEA] without Customer's consent and appropriate safeguards, such as the EU Standard Contractual Clauses where required.
13. LIABILITY. Each party's liability under this DPA is subject to the limitations in the Agreement[, except that the Agreement's data breach cap applies to Processor's breach of this DPA].
14. PRECEDENCE. If this DPA conflicts with the Agreement on the processing of Personal Data, this DPA controls.
CUSTOMER: _____________________ Date: __________
PROCESSOR: ____________________ Date: __________
ANNEX 1: Details of processing (subject matter, duration, nature and purpose, types of Personal Data, categories of individuals)
ANNEX 2: Technical and organisational security measures
ANNEX 3: Authorised subprocessors (name, location, service)
---
This free template is provided by ClauseAudit for general informational purposes and is not legal advice. Have it reviewed before use. Replace all [BRACKETED] placeholders.When to use this template
- A vendor will process customers', employees' or users' personal data for you.
- A SaaS company responding to customer procurement and privacy reviews.
- US state privacy laws or the GDPR require contract terms with processors.
How to fill it in
- Describe the processing in Annex 1.
- List security measures in Annex 2 and subprocessors in Annex 3.
- Set breach notification and subprocessor notice periods.
- Keep the restrictions on selling, sharing and training.
- Add transfer terms, such as Standard Contractual Clauses, if data leaves the US or EU.
Key clauses to check
- Instructions and restrictions
- Required by state privacy laws for service providers.
- Subprocessors
- Notice and objection rights let you control who touches your data.
- Breach notice
- Short timelines help you meet your own legal deadlines.
- Deletion
- Data should not linger after the contract ends.
- Audits
- Reports such as SOC 2 are the practical way to verify security.
Frequently asked questions
When do I need a data processing addendum?
When a vendor processes personal data on your behalf. Many state privacy laws and the GDPR require specific contract terms.
What is a subprocessor?
A third party the vendor uses to process your personal data, such as a hosting provider.
Does a DPA stop vendors training AI on my data?
It can. A strong DPA restricts use of personal data to providing the services, which excludes model training.
Is a DPA required under US law?
There is no single federal requirement, but several state privacy laws, including California's, require written contracts with service providers or processors that limit how they use personal information. The GDPR requires one when processing EU personal data. Even when not strictly required, a DPA is a practical way to show reasonable data protection and to control what vendors can do with customer data.
What should a data processing addendum include?
A DPA should describe the data and purpose of processing, limit use to the customer's instructions, require confidentiality and security measures, list and control subprocessors, set breach notification timelines, support data subject requests, allow audits or reports, and require deletion or return of data at the end. It should also address cross border transfers if data leaves the country.
Want to check if a contract is fair before you sign?
If someone sent you a saas contract, don't guess. We flag risky clauses in plain English, tuned to your state, with a downloadable report and suggested-fix redline.
Read before you sign
- What Is a Data Processing Addendum (DPA), and Do You Need One?A DPA sets the rules for how a SaaS vendor handles the personal data you send it, required under GDPR and central to CCPA compliance. Here are the terms that actually protect you.
- My SaaS Vendor Was Breached. What Does the Contract Actually Cover?When a software vendor suffers a security breach involving your data, the contract decides notification, cooperation and compensation. Here is what to check.
- Getting Your Data Out When You Cancel a SaaS ContractWhen a software subscription ends, access to your data can end with it. Here is how to check export rights, deletion timelines and formats before you cancel.
- How to Negotiate a SaaS Contract: 10 Terms Vendors Will Actually ChangeA SaaS contract negotiation checklist: the 10 terms vendors will actually change, from renewal price caps and data rights to the liability cap and exit terms.
More SaaS & Commercial templates
This free template is general information, not legal advice, and is no substitute for a qualified attorney. Laws vary by state; have it reviewed by a lawyer before you use or sign it.