A data processing agreement (DPA) defines how a SaaS or cloud vendor may handle personal data on a customer’s behalf. This review checklist helps you evaluate the agreement clause by clause, record open issues, assign negotiation owners, and establish a repeatable review cycle for new contracts, renewals, and subprocessor changes.
Overview
A DPA review is more than a legal formality. It connects the vendor contract to your privacy operations, security controls, incident response process, retention schedule, and vendor risk program. A well-maintained DPA also gives engineering, security, procurement, and customer-facing teams a shared understanding of who is responsible for what.
Start by identifying the relationship and the data flows. In a typical SaaS arrangement, the customer may act as the controller and the SaaS provider as the processor, but the roles depend on the actual purposes and means of processing. A vendor can also process some data as a processor while determining its own purposes for other activities. Do not accept role labels without checking them against the product, service terms, usage analytics, support process, and marketing practices.
Use the checklist below for both initial reviews and renewals. It is a practical control for privacy compliance, not a substitute for advice tailored to your organization, jurisdictions, data types, or contractual risk.
| Review area | What to confirm | Evidence or follow-up |
|---|---|---|
| Roles and scope | Controller, processor, or another role is accurately described. | Data-flow diagram, service description, and role rationale. |
| Processing instructions | Purposes, data categories, subjects, duration, and documented instructions are clear. | Completed processing schedule or statement of work. |
| Security | Technical and organizational measures match the risk and service architecture. | Security exhibit, assurance report, or control mapping. |
| Subprocessors | Current subprocessors, notice process, and objection rights are documented. | Subprocessor list, change notifications, and approval record. |
| International transfers | Transfer locations and applicable safeguards are identified. | Transfer assessment and signed mechanism where required. |
| Incidents | Security incident notice, cooperation, and escalation expectations are workable. | Incident response contacts and notification procedure. |
| Data-subject rights | The vendor can support access, deletion, correction, restriction, or portability requests as applicable. | Request workflow, service levels, and cost terms. |
| Retention and deletion | Return, deletion, backup handling, and legal-retention exceptions are defined. | Deletion certificate or documented deletion process. |
| Audit and assurance | Review rights provide meaningful evidence without creating unmanageable operational burden. | Audit procedure, report access, and remediation process. |
| Liability and exceptions | Risk allocation, exclusions, and conflicts with the main agreement are understood. | Legal risk decision and approved fallback language. |
What to track
1. Roles, instructions, and processing scope
Confirm that the DPA identifies the parties, services, processing purposes, personal-data categories, data-subject categories, processing duration, and documented instructions. Check whether the agreement permits the vendor to use data for product improvement, service analytics, fraud prevention, advertising, or other independent purposes. These uses should not be hidden in broad language that conflicts with the intended controller-processor relationship.
Compare the DPA with your records of processing activities, data inventory, privacy notice, and product documentation. If the agreement says the vendor processes support-ticket information but the service also receives identity data, usage logs, or uploaded customer content, record the discrepancy before signing.
2. Security measures
Look for a security schedule that is specific enough to evaluate. It should address access control, authentication, encryption where appropriate, logging, vulnerability management, resilience, secure development, personnel confidentiality, backup and recovery, and security testing at a level suitable for the service. Avoid treating a certification or audit report as a complete substitute for reviewing the controls that protect your data.
Ask whether the measures apply to production systems, support tools, backups, development environments, and subcontractors. Map important commitments to your own cloud security baseline and vendor risk assessment. A useful security commitment should be measurable or verifiable, while still allowing the vendor to improve its controls without requiring a contract amendment for every technical change.
3. Subprocessors and cloud dependencies
Review the current subprocessor list and identify where each provider operates, what it does, and what data it may access. The DPA should explain how new subprocessors are announced, how objections work, and what happens if an objection cannot be resolved. Check whether the list includes cloud hosting, customer support, monitoring, email delivery, analytics, identity, and backup providers—not only companies that receive a direct copy of customer records.
Assign an owner to monitor notices. A subprocessor change can affect transfer analysis, security review, data location, and customer commitments even when the primary vendor’s product appears unchanged.
4. International transfers
Record the countries and regions from which data may be accessed or stored, including support and disaster-recovery locations. Confirm the transfer mechanism identified in the contract and whether the parties have completed any required supporting assessment. Transfer language should align with the actual architecture and should not rely on a location statement that excludes remote access or operational support.
Because transfer rules and contractual mechanisms can change, route unusual or high-risk arrangements to qualified privacy counsel. Keep the decision, assumptions, and approved fallback position with the contract record.
5. Incidents and cooperation
Check how the DPA defines a security incident or personal-data breach, when notice begins, which contact channels are used, and what information the vendor will provide. The agreement should support investigation, containment, regulatory analysis, customer communications, and evidence preservation. Confirm whether the vendor must provide updates as facts develop and whether it will cooperate with reasonable questions after the initial notice.
Test the clause against your incident response policy. A notification obligation is only useful if your team knows who receives it, how it is escalated, and which vendor identifiers connect the incident to affected systems and data.
6. Data-subject requests
Confirm how the vendor will help with access, correction, deletion, restriction, objection, portability, or other applicable requests. The DPA should explain how requests are submitted, what technical assistance is available, how identity and authority are handled, and whether assistance fees or unusual-request conditions apply. Link this process to your privacy request workflow so that response deadlines, approvals, and evidence are tracked consistently.
7. Retention, deletion, and audit rights
Make deletion obligations precise. Identify what happens at contract termination, how long the vendor may retain data for legal obligations, and how backups are handled. Specify whether data is returned in a usable format and whether the vendor can provide confirmation of deletion. Compare these terms with your retention and deletion policy rather than accepting a generic “commercially reasonable” commitment.
For audits, assess whether the agreement provides access to relevant reports, certifications, questionnaires, summaries, or targeted assessments. Record notice periods, confidentiality restrictions, frequency limits, cost allocation, and remediation expectations. The goal is meaningful assurance that is proportionate to the service risk.
8. Liability, conflicts, and operational ownership
Read the DPA together with the master service agreement, security addendum, order form, and privacy notice. Identify precedence rules when documents conflict. Escalate caps, exclusions, indemnities, regulatory cooperation costs, and customer audit expenses for a documented risk decision. Do not allow unresolved commercial language to silently weaken a privacy or security commitment.
- Vendor, service, contract owner, and renewal date
- Processing role and approved processing purpose
- Data categories, subject categories, locations, and systems involved
- Missing or unclear clause
- Risk if unchanged
- Negotiation owner and legal reviewer
- Approved fallback language or accepted exception
- Required evidence, such as a security report or subprocessor list
- Decision date, approver, and next review date
Cadence and checkpoints
Run a full review before signing a new vendor contract and during each material renewal. A quarterly operational check is useful for higher-risk vendors: compare the DPA with the current subprocessor list, service architecture, data inventory, security evidence, open incidents, and deletion records. Lower-risk vendors may follow a different schedule, but the rationale should be documented.
Use event-based checkpoints as well. Reopen the review when the vendor adds a subprocessor, changes hosting or support locations, introduces a new data use, launches a material product feature, experiences a significant incident, changes its security commitments, or requests a revised DPA. Product and engineering release reviews should provide a route for privacy teams to learn about these changes before customer commitments are affected.
Maintain one contract record with version history. Link the signed DPA to the vendor risk assessment, security questionnaire, transfer assessment, data-flow record, and approved exceptions. This creates an audit-ready trail without requiring reviewers to reconstruct the decision from email.
How to interpret changes
Not every wording change creates the same risk. Classify changes by their effect on purpose, access, location, security, rights support, retention, and accountability. A revised company name may require a record update; a new analytics purpose or support region may require legal, technical, and customer-impact analysis.
Use a simple decision path:
- Describe the change: identify the clause, system, data, and effective date.
- Compare it with operations: check architecture, subprocessors, logs, retention settings, and support procedures.
- Assess impact: consider data sensitivity, volume, affected individuals, jurisdictions, and customer promises.
- Choose an action: accept, negotiate, request evidence, restrict the service, or escalate for formal risk acceptance.
- Record closure: capture the owner, approver, evidence, contract version, and next checkpoint.
Patterns matter. Repeated delays in data-subject requests may indicate a process or integration gap. Frequent subprocessor changes may justify closer monitoring. Vague deletion responses may require a technical validation rather than another contract reminder. Treat the DPA as an operational control that should be tested against what the service actually does.
When to revisit
Revisit this checklist at least annually and whenever regulatory guidance, transfer mechanisms, security terminology, product architecture, or standard contract language materially changes. Also schedule a review before each renewal, after a significant incident, and when a vendor sends a new DPA or subprocessor notice. A monthly review is appropriate for the small set of vendors handling sensitive data or supporting critical services; a quarterly review can cover the broader vendor portfolio.
To make the next review practical, set a renewal reminder now, confirm the contract owner, and request the latest DPA, subprocessor list, security documentation, and data-location information. Then compare the documents with your RoPA, DPIA where applicable, retention schedule, and privacy request process. Use the vendor risk assessment template to structure the supplier review, the data retention and deletion policy template to test lifecycle commitments, and the privacy request fulfillment workflow to validate rights assistance. Close each review with a documented decision rather than an informal “no change” assumption.