DPA
Data processing agreement
How it works
The GDPR distinguishes two roles. The controller decides why and how data is processed. The processor handles it only for the controller and on their instructions: hosting, CRM, newsletter tool or tracking software. For this relationship, Art. 28 requires a contract, in writing or electronic form. Among other things, it sets out:
- subject matter, duration, nature and purpose of the processing, the type of data and whose data it is
- that the provider acts only on your documented instructions and binds its staff to confidentiality
- the technical and organizational measures (TOMs) for security
- that further processors (sub-processors) are only added with your authorization
- help with data subject requests, deletion or return of the data at the end, audit rights
Why it matters
You remain responsible, even when a provider does the work. You have to choose a provider that gives sufficient guarantees for data protection, and be able to show it. The DPA is the central document for that. A missing one can lead to a fine on its own. Tracking tools handle exactly the sensitive data: email addresses, phone numbers, IP addresses and click histories. TSO provides a DPA, published on this website.
Example
An online shop uses a hosting provider, a CRM and tracking software. The shop is the controller. It signs a DPA with all three providers, files them with their sub-processor lists in its record of processing activities, and names the recipients in its privacy policy. When the tracking provider announces a new sub-processor, the shop reviews it and can object.
Common mistakes
- Expecting a DPA with every platform: depending on the service, ad platforms such as Meta or Google don't act as processors but as independent or joint controllers. Other terms from their conditions apply then. Which role applies where is something to clarify with your data protection advisor.
- Mistaking the contract for a legal basis: a DPA governs your relationship with the provider. Whether you may process the data at all, for example based on consent, is a separate question it doesn't answer.
- Signing and forgetting: when services or sub-processors change, the contract has to keep up. Providers have to announce planned changes to their sub-processors.
- Overlooking third countries: if a sub-processor sits outside the EU, the transfer needs its own basis, such as an adequacy decision or standard contractual clauses.