Data in German insolvency proceedings: what insolvency administrators need to know
Luca Weber-SchäferUpdated 11 min read
Key points
- Company data are in principle realisable estate assets (§ 35 InsO); the business books are expressly included (§ 36(2) no. 1 InsO). They are an additional source of proceeds that is often overlooked.
- On the opening of proceedings, the power of disposal passes to the administrator (§ 80(1) InsO). The administrator thereby becomes responsible for the data under data protection law.
- Anonymised data are outside the scope of the GDPR (Recital 26). Once effectively anonymised, a dataset can be licensed without asking each data subject.
- What is licensed is an anonymised copy. The retention obligations under the HGB and the AO for the originals remain in place.
A company's internal data can have considerable value for the estate. In the bankruptcy of the US airline Spirit Airlines, Google offered US$10 million for around 100 million emails and 500 million Microsoft Teams messages, and a competitor subsequently put forward US$12.5 million.[1] The buyers are AI companies that train their models on real workflows. For insolvency administrators in Germany this raises a practical question: how can this value be realised without breaching data protection law?
Are company data from insolvency proceedings part of the estate?
Yes, in principle. Company data are part of the debtor's assets and therefore realisable estate. They are an additional source of proceeds that is often overlooked in realisations.
The insolvency estate comprises all assets belonging to the debtor at the time proceedings are opened and acquired during the proceedings (§ 35(1) InsO).[2] § 36(2) no. 1 InsO clarifies that the debtor's business books belong to the estate; statutory obligations to retain records remain unaffected.[3] The same applies to other company data: email archives, ERP and CRM data, tickets and documents arose in the course of business, belong to the company's assets and can be realised like machinery, inventory or receivables. Unlike these, however, they rarely appear in realisations, although AI companies now usually pay six-figure sums for them: for 50 to 250 employees buyers quote US$100,000 to US$1 million, and for a company with 100 employees and ten years of operations US$383,000 to US$897,000.[15][16] More in the article What is company data worth? Cancelling servers and licences before the data have been secured gives this value away.
A judgment of the Higher Regional Court of Düsseldorf shows an important limit: an insolvent agency had sent newsletters for a client and stored the client's customer email addresses for this purpose. The court granted the client a claim for surrender, which entitles it to segregation in the insolvency (§ 47 InsO in conjunction with § 667 BGB).[4] Data that the debtor only processed on behalf of someone else are therefore not freely available to the estate. Something similar applies to licensed third-party content such as software or external databases: whether they may be passed on depends on the licence agreement.
- Machinery and equipment
- Inventory
- Receivables
- Real estate
- Brands and IP rights
- Email archives
- ERP and accounting
- CRM and sales
- Tickets and support
- Documents and wikis
- Code and CAD
Who is responsible for the data under data protection law?
From the opening of proceedings, as a rule the insolvency administrator, and solely.
On the opening of proceedings, the right to manage and dispose of the debtor's assets passes to the insolvency administrator (§ 80(1) InsO).[5] Because the administrator thereby decides on the purposes and means of processing, they are the controller within the meaning of Art. 4(7) GDPR. Joint controllership with the debtor under Art. 26 GDPR is ruled out according to the convincing view, because the debtor loses its power of decision.[6] For the administrator this means bearing the obligations of the GDPR, for example on legal basis, purpose limitation and data security, and being liable for infringements (Art. 82 and 83 GDPR).
Debtor-in-possession proceedings are different. There, the debtor manages the estate itself under the supervision of a custodian (§ 270(1) InsO).[7] The company then remains the controller.
May the administrator sell personal data?
Only within narrow limits. If personal data are transferred to a third party as the actual object of a sale, the data protection authorities generally require the consent of the data subjects.
The German Data Protection Conference (DSK) updated its principles on the transfer of customer data in asset deals on 11 September 2024. Where the customer data are the only asset sold, consent is generally required, particularly if buyer and seller operate in different industries. Bank and sensitive data may only be transferred with express consent unless they are necessary to perform a contract.[8] An older case shows that the authorities take this seriously: in 2015, the Bavarian Data Protection Authority fined the seller and buyer of an online shop five-figure sums because customer email addresses had been transferred without consent.[9]
For AI training there is a second problem: the data were collected to perform contracts and for internal communication, not to train AI models. Such a change of purpose is only permitted if it is compatible with the original purpose or a new legal basis exists (Art. 5(1)(b), Art. 6(4) GDPR). Asking thousands of employees, customers and suppliers for consent is practically impossible in an insolvency. The Börsen-Zeitung quotes the data protection lawyer Felix Glocker (CMS) on this: personal data from emails and Teams chats cannot simply be sold to the highest bidder like an ordinary asset.[10]
How can company data still be realised?
Through effective anonymisation before the handover and a licence that governs the use.
The GDPR does not apply to anonymous information, i.e. data where the data subject is not or no longer identifiable (Recital 26 GDPR).[11] Glocker therefore considers effective anonymisation before the resale to be the more realistic route. In the same article, Michael Rozijn (Schultze & Braun) points out that simply removing names may not be enough if the content still allows conclusions about individuals.[10]
Pseudonymisation is different: names are replaced with identifiers, but the mapping is kept in a separate table (Art. 4(5) GDPR). For whoever holds this table, the data remain personal data. On 4 September 2025 the CJEU ruled that pseudonymised data are not automatically personal data for a recipient without additional knowledge; the controller's obligations, however, are assessed from its own perspective at the time of collection (C-413/23 P, EDPS v SRB).[12] In practice this means: the mapping stays with the service provider and is deleted after the handover, and the buyer contractually undertakes not to attempt re-identification.
The anonymisation itself is also processing of personal data and needs a legal basis. The legitimate interest in realising the estate can serve as one (Art. 6(1)(f) GDPR). If a service provider carries out the anonymisation, it does so as a processor under a contract pursuant to Art. 28 GDPR. The balancing of interests and the contract should be documented and agreed with the data protection advisers of the proceedings. How we proceed technically is described on the page Anonymisation.
| Criterion | Selling personal data | Licensing anonymised data |
|---|---|---|
| GDPR applicable | Yes, in full | No, after effective anonymisation (Recital 26) |
| Consent of data subjects | Generally required (DSK 2024) | Not required |
| Possible buyers | Very limited, usually the same industry | AI labs, data vendors, companies with their own models |
| Risk for the administrator | High: fines and damages | Low with verified anonymisation and a documented balancing of interests |
| Usefulness for AI training | Hardly possible legally | High, if cases remain linked across systems |
Which data are particularly sensitive?
Special categories under Art. 9 GDPR, personnel files, professional secrets and bank data. They are usually excluded before the realisation.
The Spirit Airlines case shows how sensitive employee data are: the flight attendants' union AFA-CWA objected to the sale and demanded restrictions on employee data; the court then postponed the hearing.[13]
Exclude before realisation
- Health, religion, trade union membershipSpecial categories, Art. 9 GDPR
- Personnel files and disciplinary mattersHighly sensitive for employees
- Bank details and payment dataAccording to the DSK, transferable only with express consent
Check separately
- Client and patient dataProfessional secrecy, § 203 StGB
- Trade secrets of customers and suppliersConfidentiality clauses, GeschGehG
Which retention obligations remain?
The commercial and tax retention periods continue to apply. What is licensed is an anonymised copy; the originals remain available until the periods expire.
Since the Fourth Bureaucracy Relief Act, the following periods apply under § 257 HGB. They begin at the end of the calendar year in which the record was created (§ 257(5) HGB). Corresponding periods apply for tax purposes under § 147 AO.[14]
| Records | Period | Provision |
|---|---|---|
| Commercial books, inventories, annual financial statements, management reports | 10 years | § 257(1) no. 1 HGB |
| Accounting vouchers | 8 years (credit institutions, insurers, investment firms: 10 years) | § 257(1) no. 4 HGB |
| Business letters received and sent, including business emails | 6 years | § 257(1) nos. 2 and 3 HGB |
How does a realisation work in practice?
In six steps, from an inventory without access to data to the deletion of the mapping.
- Inventory: systems, period and volume are recorded without any data leaving the premises.
- Rights review: membership of the estate, third-party data, licence agreements and sensitive data types.
- Anonymous data sheet and buyer search: buyers see a description without names.
- Data processing agreement and anonymisation as local data processing at the seller, i.e. in the infrastructure of the proceedings.
- Sample under a non-disclosure agreement, then a licence agreement prohibiting re-identification.
- Handover of the anonymised data and deletion of the mapping table.
What a dataset can bring is shown in the article What is company data worth? The buyer side is covered in Selling company data for AI training.
Frequently asked questions
What needs to be considered when realising data in German insolvency proceedings?
Three points: the administrator is responsible for the data under data protection law (§ 80 InsO), personal content is effectively anonymised before the handover, and the originals are kept for the retention periods under the HGB and the AO. Data that the debtor only processed on behalf of third parties may be subject to segregation.
May an insolvency administrator sell email archives?
Not as raw personal data without a legal basis. Emails almost always contain personal data of employees, customers and suppliers. Once effectively anonymised, the dataset is no longer subject to the GDPR and can be licensed as a training dataset.
Does this also apply in debtor-in-possession proceedings?
Yes, with one difference: in debtor-in-possession proceedings the company itself retains the power to manage and dispose (§ 270(1) InsO) and therefore remains responsible under data protection law. The custodian supervises; management decides on the realisation.
Is it enough to replace names with pseudonyms?
For whoever knows the mapping, pseudonymised data remain personal data (Art. 4(5) GDPR). For a recipient without additional knowledge they can be anonymous according to CJEU C-413/23 P. That is why the mapping table never goes to the buyer and is deleted after the handover. Content that allows conclusions about people even without names must also be removed.
What happens to the original data after the realisation?
What is licensed is an anonymised copy. The originals remain subject to the retention obligations under § 257 HGB and § 147 AO and are deleted once the periods have expired.
Who is liable if mistakes happen during anonymisation?
Towards data subjects, the controller, i.e. the insolvency administrator, is liable in the first instance (Art. 82 GDPR). A processor is liable if it breaches its own obligations under the GDPR or disregards instructions (Art. 82(2) GDPR). The data processing agreement should set out review steps and evidence.
Sources
- [1]Fortune (Wen Shao): “Google wants Spirit Airlines' data. Micro1 wants to pay more”, 14 September 2026
- [2]Federal Ministry of Justice (Germany): “§ 35 InsO, definition of the insolvency estate”
- [3]Federal Ministry of Justice (Germany): “§ 36 InsO, assets exempt from attachment”
- [4]GÖRG: “Customer data in insolvency, on OLG Düsseldorf, judgment of 27 September 2012, I-6 U 241/11 (in German)”, 8 August 2013
- [5]Federal Ministry of Justice (Germany): “§ 80 InsO, transfer of the right to manage and dispose”
- [6]Dr. Datenschutz (intersoft consulting): “Insolvency administrators and the GDPR: a difficult relationship (in German)”, 11 October 2019
- [7]Federal Ministry of Justice (Germany): “§ 270 InsO, debtor-in-possession proceedings”
- [8]GÖRG: “New data protection challenges in M&A transactions, on the DSK resolution of 11 September 2024 (in German)”, 24 September 2024
- [9]Heuking Kühn Lüer Wojtek: “Customer data in a company acquisition: a data protection problem (in German)”, 22 December 2015
- [10]Börsen-Zeitung (Sabine Reifenberger): “What applies to buying company data from insolvency (in German)”, 18 August 2026
- [11]EUR-Lex: “Regulation (EU) 2016/679 (General Data Protection Regulation)”
- [12]beck-aktuell: “CJEU, judgment of 4 September 2025, C-413/23 P (EDPS v SRB): pseudonymised data passed to third parties (in German)”, 5 September 2025
- [13]Reuters, via Investing.com: “US court delays hearing on Google's purchase of Spirit Airlines data as union objects”, 18 August 2026
- [14]Federal Ministry of Justice (Germany): “§ 257 HGB, retention of records”
- [15]Replay: “Value my data”, accessed 20 October 2026
- [16]Handshake AI: “Data Partnerships”, accessed 20 October 2026
This article gives an overview of the German legal position on the date stated and is no substitute for legal advice in the individual case. German statutes are cited in their original abbreviation.
Luca Weber-Schäfer
Founder of European Trainingdata
Luca Weber-Schäfer advises on the realisation and licensing of company data from insolvency, restructuring and company sales, from the first estimate to the anonymised handover to AI buyers.
What is your dataset worth?
Nine questions, no data needed, no upfront costs. You receive a first estimate.