DPA check
Do you need a DPA – and is your DPA structure robust?
This interactive check helps companies, SaaS providers, agencies, platform operators and digital business models with an initial assessment of whether there is processing on behalf under Art. 28 GDPR, joint controllership under Art. 26 GDPR or rather separate controllership.
What it is about in practice
A DPA is not just a form. What matters is who decides on the purposes and essential means, whether personal data is processed, whether the service provider has its own purposes and whether sub-processors, international access, TOMs, deletion, audit rights and support obligations are properly regulated.
- Clarify the role model before signing a contract, go-live, a tool change or vendor approval.
- Check DPA clauses, TOMs, sub-processors and transfer mechanisms against the actual processing.
- Keep evidence and responsibilities readily available for data breaches, data subject requests or audits.
Role logic
From data access to the right contract structure
Review path
Six steps to an initial assessment
Which data, data subjects and systems are affected?
Who determines purpose, means, retention period and recipients?
Check nature, purpose, data types, TOMs, instructions, deletion and audits.
Authorisation, transparency, notice periods and flow-down of equal obligations.
Consider third-country transfers, DPIA, TDDDG, AI, cloud, NIS2/CRA and incident processes.
Contract signing, customer, DPO, audit, authority or data breach determine the pressure to act.
Assessment
What this check does
The check does not replace a review of the individual case, but it structures typical decision points for DPA constellations. It combines the data protection role allocation with practical evidence, contract clauses and interfaces to digital regulation.
When is processing on behalf likely?
Processing on behalf is usually likely if a service provider processes personal data exclusively for the documented purpose of the client, pursues no purposes of its own and only determines technical or organisational detailed means.
When is a DPA probably not enough?
A pure DPA may be unsuitable if the service provider uses data for its own purposes such as product improvement, benchmarking, AI training, its own advertising or independent security analyses. The processing must then be split up or regulated differently.
Which interfaces are particularly important?
Particularly relevant are third-country transfers, sub-processors, TOMs, data breach processes, data subject rights, DPIA obligations, TDDDG tracking, AI tools, cloud switching, Data Act aspects and security evidence.
What are the limits of the check?
The assessment depends on the specific processing operation, the contracts, actual use, the technical setup and role practice. The result is therefore an initial orientation and not conclusive legal advice.
Interactive check
Review your DPA constellation
Answer the following questions. At the end you receive a preliminary assessment with risk level, priority, review points, a list of documents and a copyable short overview for your inquiry.
Preliminary result
Why this result?
Recommended next review points
Documents worth preparing
Risks & deadlines
Typical DPA risks and measures
| Signal | Why relevant? | Typical measure | Priority |
|---|---|---|---|
| No DPA despite processing bound by instructions | Art. 28(3) GDPR requires a contract or other legal act with specific minimum content; the Commission's standard contractual clauses (Implementing Decision (EU) 2021/915) can be used. | Set up a DPA, synchronise the main contract, document processing and TOMs. | hoch |
| Service provider's own purposes | A pure DPA usually does not properly reflect separate processing parts. | Separate roles, review legal bases, adapt privacy notices and contracts. | kritisch |
| Third-country transfer or international access | Transfer mechanisms, SCCs, TIA, sub-processors and supplementary measures may be required. | Review the transfer register, SCC/TIA, support locations and safeguards. | hoch |
| Data breach at the service provider | Controllers must generally be able to assess GDPR notification duties within 72 hours. | Secure the breach runbook, escalation chain, logs, DPA support and communication. | kritisch |
| Data subject rights affected | Access, erasure and other rights must generally be handled within one month. | Define the process, responsibilities, identity verification, data export and deletion logic. | hoch |
| Sub-processors or tool change | Duty to inform, authorisation, objection, TOMs and transfer situation may change. | Update the sub-processor list, change process, customer evidence and contract chain. | medium to high |
Sensible next steps
Related ITMR checkers and follow-up reviews
Have your DPA structure reviewed specifically
If a contract signing, customer audit, tool change, third-country transfer, sub-processor change or incident is coming up, the role and DPA structure should be reviewed on the basis of the specific documents.
Send an inquiry about the DPA checkLegal orientation note
This checker provides a structured initial orientation. It does not replace a legal review of the specific processing operation, the contract documents, the technical implementation, the sub-processor chain, the actual instructions and the international data flows. How we review and negotiate data processing agreements is explained under Data processing agreement; further basics can be found in the area of Data protection law.