GDPR-compliant AI: operation in the EU, AVV included
Contents
GDPR-compliant AI is not a property of a product but of processing. The General Data Protection Regulation looks at how personal data is processed, and the controller has to be able to demonstrate compliance (Article 5(2)). If you use AI on incoming documents, seven questions need an answer:
| Question | GDPR | Who answers it |
|---|---|---|
| On which legal basis? | Article 6 | You, as controller |
| For which purpose, with which data? | Article 5(1)(b) and (c) | You; one Vorgang narrows both |
| Who processes on your behalf? | Article 28 | a processor, under an AVV (data processing agreement) |
| How is the data protected? | Article 32 | Controller and processor |
| Does data leave the EU? | Articles 44 onwards | Controller and processor |
| Does a system alone decide about people? | Article 22 | You, with your data protection officer |
| Is a data protection impact assessment needed? | Article 35 | You, assisted by the processor |
The GDPR assesses your processing, not the tool
Software cannot comply with the GDPR on your behalf. Under Article 4(7) GDPR, the controller is whoever determines the purposes and means of processing. Under Article 24, it implements appropriate technical and organisational measures and has to be able to demonstrate that processing complies with the Regulation.
A service provider that processes personal data on your behalf is a processor (Article 4(8)). It has duties of its own, such as security under Article 32, but it does not take purpose and legal basis off your hands. Where an organisation uses an external provider's AI application for its own purposes, Germany's conference of data protection authorities, the Datenschutzkonferenz (in German), often sees a processor relationship under Article 28.
So the question is not whether a tool is GDPR-compliant, but whether your processing is, and what the service provider contributes to it.
One Vorgang fixes purpose and data
Article 5(1) GDPR requires specified, explicit and legitimate purposes (purpose limitation) and data limited to what is necessary (data minimisation). According to the Datenschutzkonferenz, fixing the purpose in advance is essential, because only against it can you check whether processing is necessary.
A Vorgang (one intake, one task, one destination) provides that definition. The AI employee reads an incoming document, recognises metadata such as sender, date and file reference, assigns it to the responsible Fachbereich (department) and creates the task there. It writes into no second system.
You, as controller, set the legal basis under Article 6 that covers the processing. The Datenschutzkonferenz stresses that every processing step with an AI application needs a legal basis. An AVV does not replace it.
The AVV sets out what the processor may do with your data
Where a service provider processes personal data on your behalf, Article 28(3) GDPR requires a contract. It sets out the subject matter, duration, nature and purpose of processing, the type of personal data and the categories of data subjects. Under it, the processor acts only on your documented instructions, ensures that authorised persons are bound by confidentiality, and assists you with data subject rights and the obligations in Articles 32 to 36.
Every Pilotbetrieb, our entry engagement, includes an AVV, the German term for the data processing agreement. Your data protection officer can review it before the start, together with what the process conversation in week 1 defines: documents, classes and target system.
Hosting AI in Germany is not a GDPR requirement; transfers to third countries are the question
A server location in Germany is not a requirement under the GDPR. Article 1(3) GDPR states that the free movement of personal data within the Union shall be neither restricted nor prohibited for data protection reasons. Separate rules apply to transfers to third countries: under Article 44 they are allowed only under the conditions of Chapter V, for example on the basis of an adequacy decision (Article 45) or appropriate safeguards (Article 46).
According to the Datenschutzkonferenz, transfers to third countries are common with open AI systems, such as cloud services for an unlimited circle of users. It considers technically closed systems preferable from a data protection perspective.
Our posture here is fixed: operation entirely within the EU, responsibility from Düsseldorf. Whether your organisation also requires a location in Germany, for instance in an internal instruction, is your call.
The AI employee assigns; it does not decide about people
Article 22(1) GDPR gives data subjects the right not to be subject to a decision based solely on automated processing that produces legal effects concerning them or similarly significantly affects them. According to the Datenschutzkonferenz, the person deciding needs genuine room for a decision; merely formal human involvement is not enough.
The AI employee assigns a document to the responsible department and creates a task there. The department, not the AI employee, decides on the application, complaint or invoice itself. When its certainty falls below the agreed confidence threshold, it hands the case to a person. Every assignment is recorded with timestamp and reasoning in the decision log, its AI audit trail.
Whether Article 22 is engaged for your Vorgang is for your data protection officer to assess. The log gives them every single assignment to work from.
A data protection impact assessment needs a precise description of the Vorgang
Where processing is likely to result in a high risk to the rights and freedoms of natural persons, the controller carries out a data protection impact assessment beforehand (Article 35(1) GDPR). The Datenschutzkonferenz expects this to be the case in many uses of AI applications. It also notes that the controller needs information from the provider on how the system works.
Under Article 28(3)(f), the processor assists the controller with the obligations in Articles 32 to 36, which include a data protection impact assessment. For one Vorgang, the description is manageable: which documents come in, which classes exist, which target system receives the task and when a person takes over.
Four sentences describe what our operation contributes
We describe what our operation contributes to your processing in four fixed sentences:
- Operation entirely within the EU, responsibility from Düsseldorf.
- GDPR-compliant processing with an AVV (data processing agreement) included.
- A complete decision log available as evidence for EU AI Act audits.
- A defined human intervention path, documented and triggerable at any time.
The legal bases are Article 28 of the GDPR for the AVV and the EU AI Act, Regulation (EU) 2024/1689. Under its Article 2(7), the AI Act does not affect the GDPR, without prejudice to Articles 4a and 59; both apply side by side.
What you set as controller stays with you: legal basis, information duties, data protection impact assessment. How monitoring, correction and accountability in operation add up to AI agent governance is covered in a separate article. What your staff should know about the AI employee is in the article on EU AI Act Article 4. The other AI Act duties are covered under EU AI Act obligations for companies and EU AI Act compliance for a classification agent.
Frequently asked questions
Is an Agentivo AI employee GDPR-compliant?
GDPR compliance belongs to processing, not to a product, and the controller has to demonstrate it (Articles 5(2) and 24 GDPR). Our contribution is clearly defined: operation entirely within the EU, an AVV with every Pilotbetrieb, a complete decision log and a documented human intervention path. Legal basis, information duties and any data protection impact assessment stay with you; as processor, we assist you under Article 28(3).
Is a server in Germany enough for GDPR-compliant AI?
Location alone is not enough. The GDPR treats data flows within the Union alike (Article 1(3)); separate rules apply to transfers to third countries under Articles 44 onwards. Equally important are a defined purpose, a legal basis, a contract with the processor and appropriate security under Article 32. So also ask whether any further processor handles data outside the EU (Article 28(2) and (4)).
Do we need a data protection impact assessment?
You assess that as controller under Article 35 GDPR: an assessment is needed beforehand where processing is likely to result in a high risk to the rights and freedoms of natural persons. The Datenschutzkonferenz expects that in many uses of AI. Seek the advice of your data protection officer, where one is designated, as Article 35(2) provides. As processor, we assist you under Article 28(3)(f).
Which data does the AI employee process?
The documents of the one Vorgang it is built for, such as the incoming letter post of a mailroom or the delivery notes arriving at goods receipt. It recognises metadata such as sender, date and file reference, assigns the document and creates the task in exactly one target system. A Vorgang has no second intake channel and no second target system; that would be a separate Vorgang.
Does the EU AI Act replace the GDPR?
No. Under Article 2(7) of the AI Act, Union data protection law applies to personal data processed in connection with the AI Act, and the GDPR is not affected, without prejudice to the specific rules in Articles 4a and 59. An AI employee is therefore subject to both: the GDPR for personal data, and the AI Act for duties such as AI literacy under Article 4.
The next step
A Pilotbetrieb covers one Vorgang, meaning one intake, one task and one destination, together with the AVV, the decision log and a documented human intervention path. Fixed price, agreed before we start. Seven weeks, four of them productive operation on your real documents.