A data processing agreement (DPA) is the working contract that explains how a SaaS provider may handle personal data for your business. Use this reusable DPA checklist to review roles, processing instructions, subprocessors, international transfers, security, breach reporting, audits, deletion, and liability before onboarding or renewing a vendor.
Overview
A DPA is usually needed when one organization processes personal data on behalf of another. In a typical SaaS arrangement, your business may determine why and how customer, employee, or prospect data is used, while the software provider stores, analyzes, or otherwise handles that data according to your instructions. The legal labels can differ by jurisdiction and by the actual workflow, so do not rely only on the vendor's description of its role.
The agreement should connect three things: the data your business supplies, the services the vendor provides, and the controls used to protect the information. A short privacy addendum can be adequate for a low-risk service, but a generic document may leave important questions unanswered when the service involves sensitive data, automated decisions, user tracking, support access, or transfers across borders.
Before signing, gather the vendor's DPA, security summary, subprocessor list, data-location information, retention schedule, and relevant service terms. Then compare those documents with your own website legal compliance audit and internal data map. A DPA cannot fix a collection practice, privacy notice, or retention process that is already unclear.
| Review area | What the DPA should make clear | Evidence to request |
|---|---|---|
| Roles | Whether each party acts as controller, processor, or another legally defined role | Data-flow diagram and service description |
| Processing scope | Purpose, data categories, people affected, duration, and documented instructions | Completed processing schedule |
| Subprocessors | Who may access or handle the data and how changes are communicated | Current subprocessor register |
| Security | Practical technical and organizational safeguards | Security documentation or questionnaire |
| Incidents | How and when the vendor reports suspected or confirmed breaches | Incident-response terms and contact details |
| Exit | How data is returned, deleted, or preserved when the service ends | Deletion procedure and export format |
Checklist by scenario
1. Confirm the parties and roles
- Identify the legal names of the customer and provider, including the contracting entity.
- Describe which party decides the purpose and essential means of processing.
- Check whether the provider uses the data for its own product development, advertising, analytics, or other independent purposes. That use may require separate terms and analysis.
- List affiliates, support entities, hosting companies, and other organizations that may receive personal data.
Do not assume that every service provider is a processor for every feature. A vendor may provide one feature under your instructions and use another feature for its own purposes. Separate those activities in the contract and privacy documentation.
2. Define the processing instructions
- State the service purpose, such as hosting customer accounts, sending support messages, or managing subscriptions.
- List the categories of personal data, including account details, contact information, usage data, payment-related identifiers, or support content.
- Identify the categories of individuals, such as customers, website visitors, employees, contractors, or business contacts.
- Set the processing duration and explain whether backups follow a different retention period.
- Require the provider to process data only on documented instructions, subject to any legally required processing.
Make the schedule specific enough that a reviewer can determine whether a new integration falls within the agreement. “All data necessary to provide the service” is often less useful than a concise, feature-by-feature description.
3. Review subprocessors and international transfers
- Check the current list of subprocessors and the service each one performs.
- Understand whether the vendor gives advance notice of new subprocessors and what objection or termination options apply.
- Check where data is stored, accessed, supported, and backed up—not only where the primary server is located.
- Identify the transfer mechanism or other legal basis used when personal data moves across borders.
- Confirm who is responsible for documenting transfer assessments or supplementary safeguards where applicable.
Transfer language should match the actual data path. A statement that data is “processed globally” may be too broad for a business that needs to assess specific locations, access arrangements, or customer commitments.
4. Test security commitments against the service
- Look for access controls, authentication, encryption practices, logging, vulnerability management, backup protection, and recovery procedures.
- Check whether security measures are described in an attachment that can be updated without changing the DPA.
- Confirm how the provider restricts employee and contractor access to customer data.
- Ask whether the controls apply to development, testing, support, and production environments.
- Match the controls to the sensitivity and volume of the data you plan to share.
A DPA should not promise a vague standard such as “reasonable security” without any practical description. At the same time, avoid inserting controls that the vendor does not actually operate. The contract should reflect verifiable practice.
5. Clarify incidents, assistance, and individual rights
- Check the incident-notice process, including the approved contacts and information expected in an initial report.
- Confirm how the provider will support investigations, containment, notifications, and evidence preservation.
- Explain how the provider will help with access, correction, deletion, restriction, portability, or objection requests when those rights apply.
- Address data protection impact assessments, regulator inquiries, and other reasonable compliance assistance.
- Review whether assistance fees, response windows, or technical limitations are clearly stated.
Pay attention to the distinction between notifying your business and notifying affected individuals or regulators. The vendor may have a duty to alert you, while your business assesses and manages any required external notification.
6. Check audits and assurance
- Identify the reports, certifications, questionnaires, or summaries the provider makes available.
- Check whether you can request additional information when existing assurance does not answer a material question.
- Review audit notice periods, frequency limits, confidentiality rules, and cost allocation.
- Confirm what happens if an audit identifies a serious control failure.
Audit rights are most useful when they provide a realistic path to verify compliance. A clause that technically permits an audit but makes it impractical may not provide meaningful assurance.
7. Plan deletion, return, and exit
- Specify whether the provider must return data in a usable format at the end of the service.
- Set a deletion process for active systems, backups, test environments, and support records.
- Identify exceptions for legal retention and explain how retained data is isolated and protected.
- Coordinate the DPA with your contract renewal and notice dates. This contract renewal checklist can help organize that review.
What to double-check
Read the DPA together with the master services agreement, order form, privacy notice, acceptable-use terms, and security documentation. Conflicts often appear when one document says data is deleted after termination while another permits indefinite retention for analytics or service improvement.
Check definitions carefully. “Customer data,” “personal data,” “usage data,” and “de-identified data” may have different meanings across documents. If the vendor claims it can use aggregated or de-identified information, ask what safeguards and restrictions apply and whether the process matches your legal analysis.
Review liability separately from operational obligations. A DPA may contain strong security promises but a broad liability cap, a short claim period, or an exclusion that limits practical recovery. Neither a liability clause nor an indemnity automatically determines regulatory responsibility. For a higher-risk arrangement, consider professional advice through an online legal services comparison or qualified privacy counsel.
Finally, verify the vendor rather than accepting the document at face value. Record the version date, approval owner, subprocessor list, transfer information, security evidence, and unresolved exceptions in your vendor file.
Common mistakes
- Signing the vendor's template without mapping the data. A standard DPA cannot describe a workflow the business has not documented.
- Ignoring product changes. A new artificial-intelligence feature, analytics tool, support channel, or integration can change the roles and data flows.
- Reviewing only storage location. Remote support, monitoring, backups, and subprocessors may create additional access locations.
- Accepting a static subprocessor list. The change-notice process matters as much as the list itself.
- Using the DPA as a privacy notice. The DPA governs the relationship between organizations; it normally does not replace a clear notice to individuals.
- Leaving deletion until termination. Plan exports, migration testing, and account closure before the contract ends.
- Failing to document exceptions. If a provider cannot meet a requested term, record the risk decision, compensating control, and approval owner.
For related document workflows, see this guide to common contract terms and the broader small business legal compliance calendar.
When to revisit
Review the DPA before signing a new SaaS contract, adding a new data source, enabling a material product feature, changing hosting or support arrangements, or renewing the service. Revisit it after a security incident, a significant subprocessor change, a change in the types of personal data processed, or a change in the locations from which data is accessed.
At minimum, add DPA review to your regular vendor-management cycle and before seasonal planning or technology changes. Assign an owner, record the last review date, and keep the approved DPA version with the vendor record. Ask these five closing questions:
- Do the contractual roles match the real data flow?
- Are the processing purposes, data categories, and retention periods complete?
- Are subprocessors, transfer arrangements, and security measures documented?
- Can the vendor support incidents, rights requests, audits, and deletion?
- Have unresolved legal or operational risks been escalated and approved?
This checklist is practical guidance, not a substitute for legal advice. If the arrangement involves sensitive information, high-impact processing, complex international transfers, or materially negotiated liability terms, have a qualified professional review the DPA before you rely on it.