A well-scoped data processing agreement (DPA) turns GDPR requirements into practical responsibilities. This checklist explains how to distinguish a controller from a processor, which clauses to review, and how to check that the contract matches your real data flows before onboarding or renewing a provider.
Overview
A DPA is the contractual document used when one organization processes personal data on behalf of another. In GDPR terminology, the organization deciding why and how the processing occurs is generally the controller. The organization processing the data according to the controller’s documented instructions is generally the processor.
The label in a contract is not enough. The practical relationship depends on the parties’ actual decisions, services, and use of personal data. A SaaS provider may be a processor for customer records stored in its application, while acting as an independent controller for information it needs to administer its own account, billing, security, or legal obligations. Those separate purposes should be identified rather than hidden under one broad description.
A DPA should connect four things: the processing activity, the parties’ responsibilities, the technical and organizational safeguards, and the evidence needed to verify compliance. Use this checklist alongside your data map or Records of Processing Activities guide. This article is practical compliance guidance, not a substitute for advice on a specific contract or jurisdiction.
Controller versus processor
| Question | Likely controller | Likely processor |
|---|---|---|
| Who decides the purpose of processing? | The party deciding why personal data is collected or used. | Does not independently decide the purpose for the contracted activity. |
| Who determines the essential means? | Usually decides the important aspects of how processing supports its business purpose. | May choose practical or technical means within the controller’s instructions and contract. |
| Can the party reuse the data for its own purposes? | May use data for its own separately documented purposes, subject to applicable obligations. | Should not repurpose the data without an appropriate legal and contractual basis. |
| What contract is needed? | May need a DPA with its processor and clear arrangements with any other controller. | Needs processor terms covering the required processing instructions and safeguards. |
Document the conclusion for each processing activity. Do not assume that a provider is a processor merely because it is a technology vendor, or that every service offered by one provider has the same role.
Checklist by scenario
1. Before signing with a processor
- Identify the parties: Record the controller, processor, relevant affiliates, contact points, and the agreement that the DPA supports.
- Describe the subject matter and duration: State what service is provided, how long processing lasts, and which activities are in scope.
- List the processing details: Specify the purposes, categories of personal data, categories of data subjects, processing operations, and geographic locations where relevant.
- Define documented instructions: Explain what the processor may do with the data and how new instructions, feature changes, and conflicting instructions will be handled.
- Limit independent use: State whether the provider may use data for service analytics, product improvement, fraud prevention, support, or other purposes. Separate processor activities from any independent-controller activities.
- Check confidentiality: Require authorized personnel to have a confidentiality obligation and access personal data only when needed for the service.
- Review security measures: Address access control, authentication, encryption where appropriate, resilience, backups, logging, vulnerability management, secure development, staff training, and testing. The measures should reflect the risks and the data involved.
- Set incident cooperation terms: Require prompt notice of a personal data breach or suspected security incident affecting the data, together with useful details and ongoing updates. Avoid relying only on vague language such as “without undue delay” if operational teams need a clearer notification channel and escalation path.
- Cover data-subject requests: Establish how the processor will help with access, correction, deletion, restriction, portability, objection, and other requests that apply to the processing.
- Cover compliance assistance: Include cooperation for security assessments, impact assessments, regulator inquiries, and other controller obligations where the processor’s information or action is needed.
2. When the processor uses subprocessors
- Require prior specific or general authorization for subprocessors, using the mechanism agreed by the parties.
- Keep a current list or notice process that identifies subprocessors, their locations, and the service they provide.
- Define how proposed changes are communicated and how objections, alternatives, or termination rights operate.
- Require the processor to impose appropriate data protection obligations on each subprocessor and remain responsible for the contracted processing.
- Check the actual service architecture. A DPA that lists only the main vendor is incomplete if support, hosting, monitoring, email, analytics, or backup providers can access the data.
Use a structured vendor risk assessment checklist to compare the contract with the provider’s security documentation, subprocessor register, and technical design.
3. When data leaves the relevant jurisdiction
- Map where personal data is stored, accessed, supported, backed up, and transferred.
- Identify the approved transfer mechanism or other applicable legal arrangement before the transfer begins.
- Assign responsibility for transfer assessments, supplementary safeguards, government-access requests, and changes in the transfer route.
- Check whether the provider can change hosting regions or support locations without notice.
- Keep transfer documentation with the DPA, security review, and vendor record rather than treating the transfer clause as a standalone formality.
4. At the end of the service
- Choose whether the processor must return, export, or delete personal data.
- Define the format, timing, cost allocation, and assistance for data export.
- Address backups, disaster-recovery copies, legal retention, and secure deletion evidence.
- Require confirmation of deletion when appropriate, while recognizing any documented retention obligation.
- State how access is revoked and how credentials, keys, devices, and administrator accounts are handled after termination.
5. Audits, evidence, and liability
- Set a reasonable audit and inspection process, including notice, scope, confidentiality, frequency, and cost rules.
- Identify acceptable evidence such as independent assurance reports, penetration-test summaries, security policies, remediation records, and completed questionnaires.
- Define how material findings are corrected, tracked, and escalated.
- Check that liability, indemnity, insurance, and limitation clauses do not contradict the operational obligations in the DPA. These provisions often require legal review.
- Record the contract owner, review date, evidence location, and escalation contact in your compliance register.
What to double-check
Read the DPA against the real workflow, not just against a preferred template. Compare it with your data inventory, product configuration, privacy notice, security questionnaire, and provider documentation.
- Purpose alignment: Does the DPA describe what the business actually does with the service? A generic purpose such as “business operations” may not explain support tickets, recordings, identity data, or behavioral analytics.
- Data minimization: Are all listed data categories necessary? If a service receives special-category data, credentials, payment details, or children’s data, confirm that the safeguards and instructions address the additional risk.
- Security consistency: Do contractual promises match the provider’s security documentation and configuration? Check retention settings, administrator access, encryption options, logging, and backup behavior.
- Breach workflow: Does your team know who receives an incident notice, what information is required, and who decides whether regulator or individual notification is needed?
- Subprocessor visibility: Does the current list match the service’s integrations and support model? Set an owner to monitor changes.
- Transfer accuracy: Do the listed locations and mechanisms reflect actual access by support and engineering teams, not just the primary storage region?
- Evidence access: Can you obtain the records needed for your privacy compliance and cybersecurity compliance programs without accepting an unreviewable promise?
For broader infrastructure context, pair the DPA review with a website security and compliance audit and the relevant compliance evidence checklist.
Common mistakes
- Using a template without mapping the service: A template is a starting point, not proof that the processing description is complete.
- Accepting role labels without analysis: A provider may be a processor for one activity and a controller for another.
- Ignoring product changes: New artificial intelligence features, analytics, integrations, support tools, or hosting regions can change the data flow and the provider’s role.
- Relying on a security certification alone: Assurance reports can support review but do not replace contract terms, configuration checks, or risk-based due diligence.
- Leaving breach notices undefined: A contract should support an actionable response, including contacts, minimum information, cooperation, and updates.
- Forgetting termination: Return, deletion, backups, export, and access revocation should be agreed before the relationship ends.
- Failing to record exceptions: If a provider will not accept a requested clause, document the risk, compensating control, approval, and review date.
When to revisit
Review the DPA before onboarding a new provider, renewing a contract, adding a new product module, changing processing purposes, introducing a subprocessor, moving hosting regions, or collecting a new category of personal data. Revisit it after a significant security incident, material regulatory or contractual change, or a change in your privacy notice and data map.
At minimum, assign an owner to perform a periodic review before seasonal planning cycles and whenever workflows or tools change. Start with a short control loop:
- Export the current vendor, subprocessor, and data-flow information.
- Compare it with the signed DPA and the provider’s current documentation.
- Record discrepancies, risk decisions, owners, and deadlines.
- Update the contract, processing records, security configuration, and privacy notice where needed.
- Retain approval and supporting evidence in the contract or compliance repository.
A DPA is most useful when it remains connected to operational evidence. Treat it as a living part of vendor governance, rather than a document completed once and forgotten.