Guide · AT-R23REV. 2026-A
Do I need a data processing agreement (Auftragsverarbeitungsvertrag), and when?

By Felix GötzManaging director · qualified IT officer (Informatikkaufmann, IHK)Last updated:
What it is about
A data processing agreement sets out what a service provider may do with your data. The legal basis is Article 28 of the GDPR (DSGVO). The division of roles is decisive here: you are the controller and decide on the purpose and means. The service provider is the processor and acts on your instructions.
The agreement is not a formality but the precondition for the arrangement to be permitted at all. If it is missing, a fine can be imposed under Article 83(4) of the GDPR, on both sides.
When you need one
Whenever a service provider processes personal data for you without deciding the purpose itself. Typical cases in a trade or other small business:
- IT support. Anyone who maintains workstations or servers sees data on employees and customers while doing so. That cannot be avoided: anyone who repairs a mail server sees senders and recipients.
- Cloud services and hosting. From the storage service to the booking calendar on the website.
- External payroll, as long as it is purely a matter of carrying out instructions.
- Newsletter and appointment tools that store contact details.
When you do not need one
This is where most articles go wrong. Tax advisers, solicitors, auditors and banks are not processors. They work on their own responsibility and are subject to their own professional duties. Anyone who hands them an AVV rightly gets it back.
Purely ancillary services such as post, telephone services and third-party copier maintenance also fall outside the requirement if the provider is not expected to access the data. The same applies to work that involves no personal data.
What belongs in it
Art. 28(3) GDPR requires a fixed set of details: subject matter and duration, nature and purpose of the processing, the type of data, the categories of people affected, and the obligations and rights of the controller. On top of that come eight mandatory clauses, including binding instructions, confidentiality, technical measures, the handling of sub-processors and deletion once the contract ends.
We see two mistakes particularly often. The first: an annex that is still empty when the agreement is signed. A contract that says “by arrangement” where systems and types of data should be listed does not meet the requirement. The second: a list of measures that has been ticked off without the measures existing. If something goes wrong, it is exactly this list that will be used.
Who provides it
As the client, you are responsible for making sure there is an agreement. The service provider usually drafts it because it knows its own processes and safeguards best. You review the draft and can raise objections.
We bring our agreement to the first meeting and fill in the annex with you before anyone signs. The Business IT page explains what to expect at the meeting.