Data Processing Agreement Checklist: Controller, Processor, Security, and Subprocessor Terms
data processing agreementsGDPRvendor managementprivacy compliancesubprocessorsinternational data transfers

Data Processing Agreement Checklist: Controller, Processor, Security, and Subprocessor Terms

LLegal Resources Editorial Team
2026-11-21
7 min read

Use this DPA checklist to review roles, security, subprocessors, transfers, rights assistance, deletion, and liability before sharing personal data.

A data processing agreement (DPA) should do more than attach standard privacy language to a vendor contract. This checklist helps your business confirm the parties’ roles, define permitted data use, assess security and subprocessors, address international transfers, and record what happens when the relationship ends.

Overview

Before sharing customer, employee, patient, or other personal data with a service provider, identify why the data is being shared and which organization controls each decision. A DPA is commonly used when one party processes personal data for another, but the correct agreement depends on the actual relationship and applicable law. Labels in a vendor’s contract do not determine the parties’ legal roles by themselves.

Use this article as a business legal compliance workflow, not as a substitute for legal advice. Privacy obligations can vary by jurisdiction, data type, industry, and the way a product operates. A DPA should also be read together with the main commercial agreement, security documentation, privacy notice, data-retention policy, and any applicable transfer terms.

Controller, processor, or independent controller?

ArrangementTypical responsibilityQuestions to confirm
Controller and processorThe controller determines the purposes and essential means of processing; the processor handles data on the controller’s documented instructions.Does the vendor use the data only to provide the contracted service? Can your instructions, audits, and deletion requirements be enforced?
Independent controllersEach organization decides its own purposes and means for at least some processing activities.What separate purpose does each party have? Which party provides notices, handles requests, and establishes its own retention period?
Joint controllersThe organizations jointly determine important purposes or means of processing.Have responsibilities been allocated clearly, including transparency, individual rights, security, and communications?

For each data flow, create a short record showing the data categories, individuals concerned, purpose, systems involved, geographic locations, retention period, and recipient. This record makes the DPA review more concrete and helps expose gaps that a generic vendor form may not address.

Checklist by scenario

1. Before onboarding a new SaaS vendor

  • Define the data: List personal data fields, sensitive or special-category data, account credentials, identifiers, communications, and any data that should not be uploaded.
  • Define the purpose: State the service function and prohibit unrelated advertising, profiling, sale, or product-development use unless separately authorized and legally supported.
  • Confirm the role: Ask the vendor whether it acts as a processor, independent controller, or in more than one role depending on the feature.
  • Check instructions: The agreement should identify whose instructions govern, how instructions are issued, and what happens if an instruction appears unlawful or technically impossible.
  • Review security: Look for access controls, authentication, encryption practices, backup and recovery, logging, vulnerability management, personnel training, and incident-response procedures. The level of detail should match the risk.
  • Set breach communications: Require prompt notice of a suspected or confirmed personal-data incident, with enough information to support investigation, legal assessment, and any required notices. Avoid relying only on an undefined phrase such as “without undue delay.”
  • List subprocessors: Identify material subprocessors, their locations, services, and the notice or objection process for changes. Confirm that the vendor remains responsible for its contracted obligations.
  • Address individual rights: Require reasonable assistance with access, correction, deletion, restriction, portability, objection, consent withdrawal, or other rights that may apply to the processing.
  • Cover impact assessments: Establish how the vendor will support risk assessments, regulator inquiries, investigations, and requests for information about its controls.
  • Set return and deletion terms: Specify what happens at termination, including active data, backups, test environments, exports, legal holds, and deletion evidence where appropriate.

2. When data crosses borders

Document where data is collected, accessed, stored, backed up, and supported. Identify every transfer route, including remote access by support personnel. Then confirm which transfer mechanism or additional safeguards are intended for the relevant jurisdictions. The DPA should not imply that a transfer is lawful merely because the vendor lists several possible mechanisms; the parties should identify the mechanism they expect to use and who is responsible for maintaining it.

Ask whether the vendor receives government or law-enforcement requests, how it evaluates them, and whether it can notify the customer unless legally prohibited. Review whether contractual commitments match the vendor’s actual hosting and support model.

3. During renewal, product expansion, or an integration change

Compare the current data map with the proposed service. New analytics, artificial-intelligence features, mobile applications, tracking tools, support channels, or identity integrations can change the purpose and risk of processing. Recheck the vendor’s privacy documentation, subprocessor list, security materials, retention settings, and international-access arrangements before approving the change.

4. Vendor questionnaire

Use these questions as a starting point and request documentary answers rather than relying on verbal assurances:

  1. What personal data will you receive, from which systems, and for which service functions?
  2. Do you process the data only on our instructions, or do you determine any independent purposes?
  3. Where is data stored, accessed, supported, and backed up?
  4. Which subprocessors are involved, and how are changes communicated?
  5. What is your process and target timing for notifying us about security incidents?
  6. How do you authenticate users, limit employee access, and review privileges?
  7. How will you help with data-subject requests, investigations, and impact assessments?
  8. What retention, export, deletion, and backup-erasure options are available?
  9. What audit reports, certifications, penetration-test summaries, or other assurance materials can you provide?
  10. What liability, indemnification, cooperation, and insurance terms apply to privacy or security failures?

What to double-check

Use restrictions and confidentiality

Check that the vendor may not repurpose data simply because it is technically able to do so. Confidentiality obligations should cover personnel, contractors, and subprocessors with access to the information. Confirm that personnel receive appropriate privacy and security instructions and that access is limited to a business need.

Audit rights that work in practice

A clause promising an audit is not useful if it provides no practical route to verify controls. Review notice periods, reasonable limits, confidentiality protections, costs, use of independent reports, and what happens when a report identifies a material gap. Consider whether the audit process is sufficient for the risk and data involved.

Security commitments and remedies

Compare the DPA’s security promises with the vendor’s technical appendix and sales materials. Look for conflicts about encryption, access logging, deletion, availability, incident response, or data location. Read liability caps, exclusions, indemnities, and insurance provisions together with the DPA; a strong operational promise may have limited value if the contract removes meaningful remedies.

DPA review worksheet

Review itemRecord before approvalStatus
Roles and processing purposeParties, role for each feature, data subjects, data categories, documented purposeOpen / Complete
SecurityTechnical measures, organizational measures, access model, incident contactOpen / Complete
SubprocessorsCurrent list, locations, notice process, objection and replacement processOpen / Complete
TransfersLocations, access routes, transfer mechanism, supplementary safeguards if neededOpen / Complete
Rights and cooperationRequest handling, investigations, assessments, regulator cooperationOpen / Complete
End of serviceExport format, return deadline, deletion scope, backup treatment, certificationOpen / Complete
Commercial riskLiability, indemnification, insurance, suspension, termination, dispute processOpen / Complete

Common mistakes

  • Accepting a generic DPA without checking the product: A vendor may offer different processing models across features or service tiers.
  • Confusing security compliance with privacy compliance: A security report can provide useful assurance but does not answer questions about purpose, lawful use, rights, retention, or transfers.
  • Ignoring support access: Data may be accessed from another country even when production hosting is local.
  • Failing to control new subprocessors: A silent or unclear change process can leave the customer unaware of a material data-flow change.
  • Leaving deletion undefined: “Delete upon termination” should be tested against backups, exports, logs, legal retention, and account recovery systems.
  • Relying on a privacy notice alone: A public notice explains an organization’s practices but does not replace negotiated vendor obligations.
  • Separating legal review from procurement: Procurement, security, privacy, and business owners should use the same data map and approval record.

For related contract controls, see the contract review checklist for small businesses, and for electronic execution records, see the electronic signature legal checklist. Businesses should also compare the DPA with their website privacy and terms requirements.

When to revisit

Do not treat a DPA as a one-time onboarding document. Revisit it before seasonal planning cycles and whenever workflows or tools change. A practical review trigger list includes a new vendor, renewal, new product feature, integration, subprocessor change, acquisition, security incident, change in data categories, expansion into a new jurisdiction, or change in retention practice.

At least annually, assign an owner to confirm that the data map, vendor list, transfer assumptions, security materials, contact details, and deletion process remain accurate. Also check whether privacy-law definitions, regulator guidance, standard contractual clauses, breach-notification expectations, or state and regional requirements have changed. If the relationship involves sensitive data, large-scale monitoring, high-risk processing, or complex international access, obtain qualified legal advice before approval.

Next step: Choose one active vendor, complete the worksheet, compare its actual data flows with the signed DPA, and record every unresolved point with an owner and deadline. Repeat the process for high-risk vendors first, then incorporate the checklist into procurement and renewal workflows.

Related Topics

#data processing agreements#GDPR#vendor management#privacy compliance#subprocessors#international data transfers
L

Legal Resources Editorial Team

Legal Compliance Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.