End of contract: why a DPA alone does not protect you
In 2025 Germany’s Federal Court of Justice made clear: if you engage a processor, you must actively ensure deletion at contract end. A contract is not enough.
In short
The German Federal Court of Justice (BGH) ruled on 11 November 2025 (VI ZR 396/24): a controller may not simply oblige the processor by contract to delete. It must contribute what the individual case requires so the data actually disappears at contract end. If it stays and ends up on the darknet, that is non-material damage under Article 82 GDPR.
Auf Deutsch lesen: deutsche Fassung
At the end of the contract your service provider sends you an email: tomorrow we will delete everything. You tick it off. The contract has ended, the data processing agreement (DPA) was in place, the matter is closed. Three years later your customers’ data is for sale on the darknet. And the question that is then asked is not what the service provider did wrong. It is: what did you do to make sure? That is exactly what the German Federal Court of Justice (Bundesgerichtshof, BGH) ruled on, on 11 November 2025.
What the BGH decided, and what it expressly did not
Honesty first, because a lot of half-truths are currently doing the rounds on the networks. The judgment has the case number VI ZR 396/24, it dates from 11 November 2025, and the lower courts were the Dresden Higher Regional Court and the Dresden Regional Court. But the BGH did not impose anything on the defendant. On the claimant’s appeal on points of law it set aside the appeal judgment in part and referred the case back to the Higher Regional Court. There is no final judgment and no sum awarded.
Anyone who writes that a company was ordered to pay has not read the judgment. What you can take away are the two official headnotes, and they are strong enough. They set the standard by which the Higher Regional Court now has to reassess the case, and by which every controller has to be measured.
However, the controller may not, as a rule, content itself with concluding a contract with the processor that imposes on the processor the contractual obligation to delete the data and to provide evidence of the deletion when the contract ends.
That is the sentence. It is in the reasons for the decision, and it clears away an error I constantly encounter in conversations: the DPA is in place, so the matter is settled. It is not. The contract is the obligation. The check is also the obligation.
The case in five lines
The court anonymises the parties itself, and I do the same. It concerns an online music streaming service based in France and its external processor.
- 1 December 2019: the contract ends.
- 30 November 2019: the processor emails that it will delete the website and all data on the website the following day.
- November 2022: data records of users of the service turn up on the darknet, as at 2019.
- 22 February 2023: the processor confirms for the first time that deletion has actually taken place.
- The reason for the gap: employees of the service provider had not deleted the data, but transferred it from the production environment to a test environment.
Why the announcement was not enough
This is where it becomes interesting in practice, and this is where the lesson for every company lies. What was announced was the deletion of the website and of all data on the website. What was owed was something else, namely the complete deletion of all copies of the data as well. The copy was not on the website. It was in a test environment, and that is exactly what caused the damage three years later.
I know this from every workshop and every server room. The main data set is cleared away cleanly, and then the copy is still lying somewhere: in the test system, in the backup, in the export file on a drive, in the project manager’s mailbox. Anyone who only asks whether deletion took place gets a yes. Anyone who asks what was deleted and where it was held gets a list.
Then there is a second point, which I like even better because it is measurable. Under the contract, deletion was owed within 21 days after the end of the contract, together with a written confirmation that it had been carried out in full. That never came. A follow-up enquiry was made only in 2023, more than three years after the end of the contract and only after the hacking incident had become known. The BGH calls that evidently too late. So there was a deadline, there was an omission, and both are in your own contract.
| What the DPA governs | What the controller must do in addition |
|---|---|
| The processor undertakes to delete at the end of the contract. | Follow up that the deletion actually takes place, and within the agreed period. |
| The processor owes a deletion confirmation. | Demand the confirmation when it fails to arrive, and not years later. |
| The contract names the extent: all data and all copies. | Check whether the activity promised corresponds to this extent at all. |
| Art. 28 provides for evidence and audits. | Make use of this right, yourself or through a mandated auditor. |
Art. 28 names the auditor explicitly
The court relies on Article 28(3), second sentence, of the General Data Protection Regulation, point (g) and point (h). Point (g) governs deletion or return after the end of the processing. Point (h) is the one hardly anyone cites: the processor makes available to the controller all information necessary to demonstrate compliance and allows for and contributes to audits conducted by the controller or another auditor mandated by the controller.
Read that part of the sentence again. An auditor mandated by the controller. That is not an invention of a consulting industry, it has been in the text of the regulation since 2016 and has applied since 2018. It is the description of a second-party audit, and it is the reason I offer this format at all. The entitlement to audit the service provider is already there. It is just rarely used.
If you work to ISO 27001, you already have the procedure
The judgment sounds like data protection law, but it describes a management task for which a standard has long existed. ISO/IEC 27001 carries supplier relationships as a block of its own: information security in supplier relationships, addressing it within the agreements, managing the entire chain including subcontractors, and the ongoing monitoring and review of the services. Added to that is the return of assets at the end of a contractual relationship.
Anyone who has seriously implemented these controls has exactly the procedure the BGH demands. It just has a different name. In the standard it is called monitoring and review of supplier services, in the judgment it is called what is necessary in the circumstances of the individual case. The meaning is the same: you look, and you record that you looked.
The practical benefit lies in the sequence. A management system treats the end of a contract as a process step with an owner and a date, not as a reminder. That is exactly where the case failed: there was a deadline, but nobody it belonged to.
And now AI: the same obligation, only easier to overlook
I have laid this judgment over three AI projects I have dealt with in recent months. In all three the situation is identical, only less clear.
- HR AI in the application process: CVs go to a service that pre-sorts them. At the end of the contract it is not enough to switch off the access. The uploaded documents, the features derived from them and the logs have to go as well.
- Vision inspection in manufacturing: images from the line train a model. After the contract the images sit in the provider’s training data set, often in several versions. The actual model is not even the problem here, the raw images are.
- ERP AI in order processing: customer data runs as a prompt to a language model. What afterwards sits in logs, caches and a vector database, nobody knows from the contract. You have to ask.
With classic processing on behalf there is one data set and one backup. With AI services there are inputs, outputs, logs, embeddings, intermediate states and, depending on the model, fine-tuning data as well. Anyone who asks here whether deletion took place without saying what gets an answer that is worth nothing to a court.
What I want to see in black and white at the end of a contract
This is not legal advice, but the list I take into a supplier audit. It is short enough to be put into practice.
- A deletion confirmation with date, signature and named role. Not an announcement, but a confirmation of something that has happened.
- A list of what was deleted: production data, test environments, backups, exports, logs. Anyone who names only the production data is telling you something about the rest.
- The deadline from your own contract in the calendar, not in your head. If nothing arrives, you follow up, and that is noted.
- The same chain for subcontractors. The test environment that causes you the damage does not have to be at your direct contracting partner.
- For AI services in addition: prompts and outputs, logs, embeddings and vector stores, fine-tuning data, expressly named.
- A note of what you checked and when. Evidence of your own diligence only arises if you keep it.
The most expensive sentence in this case is not a legal one. It is: we relied on it. Relying is not a measure. One phone call in December 2019 would have been enough.
If you want to know whether your service providers can withstand this, I audit them for you. That is exactly the auditor Art. 28 provides for.
View supplier auditsFinally, the caveat that belongs here: I am an auditor, not a lawyer. This text puts a judgment into context and does not replace legal advice. And because the proceedings have been referred back, the last word in this specific case has not yet been spoken. The standard stands all the same, and it applies with immediate effect to everyone who hands data over.
Primary sources
Closing out the end of a contract with a service provider properly
Take the deadline from your own contract
Check in the DPA which deadline has been agreed for deletion and the deletion confirmation, and enter the date in the calendar. In the case decided it was 21 days, and exactly this deadline passed unnoticed.
Define the extent of deletion in writing
Before the end of the contract, name what is to be deleted: production data, test environments, backups, exports and logs. For AI services, in addition prompts, outputs, embeddings and fine-tuning data.
Do not book an announcement as completion
An email saying that deletion will take place tomorrow is not a confirmation that deletion has taken place. Also check whether the announced activity corresponds to the extent owed at all.
Demand the confirmation when it fails to arrive
If the deadline expires, follow up and record it. An enquiry years later, triggered by an incident, helps neither the data subject nor you.
Include subcontractors
Ask to whom your service provider has passed data on, and demand the deletion confirmation along the whole chain. The copy that becomes dangerous for you is rarely with your direct contracting partner.
Have it audited if in doubt
Article 28(3), second sentence, point (h) gives you the right to audits by yourself or a mandated auditor. A second-party audit turns your diligence into evidence.
Document your own process
Record what you checked and when, and what answer you received. Without this note your diligence exists, but it cannot be evidenced.
Frequently asked questions
Is a signed DPA enough to meet the obligations under Article 28 GDPR?+
According to the BGH judgment of 11 November 2025 (VI ZR 396/24), no. The court holds that the controller may not, as a rule, content itself with contractually obliging the processor to delete and to provide evidence. At the end of the contract it must contribute what is necessary in the circumstances of the individual case so that the deletion actually takes place. This is an assessment, not legal advice.
Was the company ordered to pay damages in these proceedings?+
No. On the claimant’s appeal on points of law, the BGH set aside the judgment of the Dresden Higher Regional Court in part and referred the case back to the appeal court for a new hearing. So far there is no final judgment and no sum awarded in these proceedings. What is binding are the two official headnotes, not an amount.
What counts as non-material damage under Article 82 GDPR?+
The second headnote says: if personal data remains with the processor after the end of the contract, is accessed there without authorisation and is offered for sale on the darknet, that constitutes non-material damage within the meaning of Article 82(1) GDPR. It is not excluded merely because the data had already been unlawfully accessed before.
Where does it say that I may audit my service provider?+
In Article 28(3), second sentence, point (h) GDPR. Under it, the processor makes available all information necessary to demonstrate compliance and allows for and contributes to audits conducted by the controller or another auditor mandated by the controller. That is exactly what a second-party audit is.
What is different with AI service providers?+
The data is more widely distributed. Besides the actual data set there are prompts, outputs, logs, embeddings in vector stores and, depending on the model, fine-tuning data. A deletion confirmation that names only the main data set does not cover these stores. They have to be named individually at the end of the contract.
Author & expert review: Lars Zimmermann · ISO/IEC 42001 Senior Lead Auditor & Senior Lead Implementer · ISO/IEC 27001 Lead Auditor & Lead Implementer (PECB)
Last updated: 10 November 2026. Researched and reviewed to the best of our knowledge; not a substitute for individual legal advice.
Questions about your own case?
In a free 15-minute intro call we assess where you stand on ISO 42001, ISO 27001 and the EU AI Act, honestly and without a sales pitch.