Guides
GDPR: insolvency administrators as data controllers
Why the insolvency administrator becomes the controller under data protection law, which legal bases they can rely on, and how to organise access requests, data processing and safeguards.
When proceedings are opened, the administration takes over not only accounts, contracts and inventories but also the debtor’s data holdings: customer databases, personnel files, supplier correspondence, email mailboxes and logs. This raises a question that in practice often only surfaces when a former customer requests access or a service provider asks for a data processing agreement: which obligations does the GDPR impose on insolvency administrators, and how can they be met with reasonable effort? This article explains why the administration becomes the controller under data protection law, on which legal bases it can base processing, how access requests are answered properly and which organisational measures make sense in the first weeks.
GDPR: insolvency administrators as controllers under Art. 4(7)
Under Art. 4(7) GDPR, the controller is the body which, alone or jointly with others, determines the purposes and means of the processing of personal data. Before the proceedings, this is indisputably the debtor, acting through its management. With the opening, under § 80(1) InsO (German Insolvency Code) the right to administer and dispose of the assets belonging to the insolvency estate passes to the insolvency administrator. Under § 36(2) no. 1 InsO, the estate expressly includes the business books, and in practice the administration covers all of the company’s data holdings.
According to the prevailing view, the insolvency administrator thereby becomes the controller in their own right for the processing of the data they use in administering the estate. They decide which systems continue to run and which data are preserved, analysed, transferred or erased. It is precisely these decisions on purposes and means that form the criterion of Art. 4(7) GDPR. Some argue that the debtor formally remains the controller and the administrator acts merely as its organ. In practice, the difference is small: whoever actually administers the data must fulfil the obligations of the GDPR.
Preliminary administration and debtor-in-possession proceedings
In the preliminary proceedings, the role depends on the court’s orders. A “strong” preliminary administrator with power of disposal under § 22(1) InsO is largely equivalent to the final administrator. With a “weak” preliminary administrator whose consent is required for dispositions, the debtor as a rule remains the controller, but the administrator processes data in their own right insofar as they review, copy and analyse records. In debtor-in-possession proceedings (Eigenverwaltung), the debtor remains the controller. The (custodian) Sachwalter processes data only within the scope of their supervisory task.
Two roles in one law firm
In addition, there is the law firm itself. For its own files, its correspondence and its client management it is in any case the controller. It is advisable to separate both spheres clearly: the debtor’s data holdings belong in a separate, proceedings-specific repository and not in the law firm’s general document management.
Legal bases for processing by the administrator
Every processing of personal data requires a legal basis under Art. 6(1) GDPR. For the typical activities in the proceedings, three in particular come into consideration.
- Legal obligation, Art. 6(1)(c) GDPR: the InsO obliges the administrator to take possession of the insolvency estate (§ 148 InsO), to draw up a list of the estate’s assets and a list of creditors (§§ 151, 152 InsO), to examine claims and to report. In addition, there are obligations under commercial and tax law that continue under § 155 InsO, as well as retention obligations under § 257 HGB (German Commercial Code) and § 147 AO (German Fiscal Code).
- Legitimate interests, Art. 6(1)(f) GDPR: realising the insolvency estate, examining avoidance claims, asserting claims and defending against unjustified claims are in the interest of the body of creditors as a whole. Each of these requires a balancing against the interests of the data subjects.
- Performance of a contract, Art. 6(1)(b) GDPR: if the administrator continues the business or elects performance of a contract under § 103 InsO, they process customer and supplier data to perform these contracts.
Special categories and employee data
Health data in personnel files, data on trade union membership in payroll records or patient data at medical practices and care services are subject to Art. 9 GDPR. Their processing is permissible only under the conditions set out there, for example to fulfil obligations under employment and social security law pursuant to Art. 9(2)(b) GDPR. For employee data, § 26 BDSG (German Federal Data Protection Act) contains a special rule. Its scope has been disputed since a ruling of the Court of Justice of the European Union on a comparable state law provision, which is why many commentators additionally rely on Art. 6(1)(b), (c) and (f) GDPR. How personnel files and payroll data are preserved in concrete terms is covered in the article Personnel files and payroll data in insolvency.
Purpose limitation
Under Art. 5(1)(b) GDPR, data may be processed only for specified purposes. Further processing for the purposes of the insolvency proceedings is as a rule compatible with the original purpose of collection under Art. 6(4) GDPR, because it builds on the existing business relationship and is laid down by statute. The limits become apparent with entirely new purposes. The sale of customer data is a topic of its own with its own requirements and is deliberately not explored further here.
Inventory: which data are held where?
Data protection can only be organised once it is known which data exist. In the first days after appointment, a pragmatic overview that is refined later is sufficient. The following sequence has proven effective:
- Request the debtor’s record of processing activities under Art. 30 GDPR. If it is missing or outdated, record the core processes yourself: personnel, accounting, sales, customer service, production.
- List systems and storage locations: servers, cloud services, specialist applications, mailboxes, network drives, mobile devices and paper archives.
- Flag particularly sensitive holdings: health data, bank data, copies of ID documents, application documents, video recordings.
- Record service providers that process data on the company’s behalf: payroll, hosting, maintenance, newsletters, telephony.
- Contact the debtor’s data protection officer, if one has been appointed, and clarify whether the mandate continues.
This overview is at the same time the basis for the technical preservation. A complete insolvency data preservation at the outset ensures that data are not lost through expiring contracts or servers being switched off, and it is itself a technical safeguard within the meaning of Art. 32 GDPR.
A backup does not replace the data protection assessment, but it is what makes it possible in the first place. Anyone who does not know which data exist can neither provide access nor erase with legal certainty.
Answering access requests under Art. 15 GDPR
Access requests reach administrators more often than one might expect. Typical senders are former employees examining claims, customers with warranty questions and occasionally opponents in avoidance actions looking for information for their defence. The obligations under Art. 15 GDPR apply regardless of the requesting person’s motivation.
Deadlines and form
Under Art. 12(3) GDPR, access must be provided without undue delay and at the latest within one month. The period may be extended by a further two months where necessary, taking into account the complexity and number of the requests. The data subject must be informed of the extension and the reasons for it within the first month. Particularly in the initial phase of proceedings, when systems have not yet been opened up, this option is important. It does not, however, release you from responding in good time.
The process in practice
- Document receipt: record the date, sender, channel and exact content of the request.
- Verify identity: where there are reasonable doubts, additional information may be requested under Art. 12(6) GDPR. No more than is necessary for identification should be requested.
- Search the data holdings: master data, accounting, specialist applications, mailboxes and archives. With decommissioned systems this is often hardly possible without a working environment; virtualisation of legacy systems helps here.
- Redact third-party data: under Art. 15(4) GDPR, the copy must not adversely affect the rights of other persons.
- Compile the response: categories, purposes, recipients, storage period, source and data subject rights under Art. 15(1) GDPR, and a copy of the data under Art. 15(3) GDPR.
- Dispatch and filing: transmit the response securely and document the entire process.
Limits of the right of access
Manifestly unfounded or excessive requests may be refused or made subject to a reasonable fee under Art. 12(5) GDPR. The burden of proof lies with the controller, and the threshold is high. Further exceptions are contained in § 34 BDSG, among others for data that may not be erased solely because of statutory retention provisions, insofar as providing access would require disproportionate effort. Whether one of these exceptions applies must be carefully justified in the individual case. A blanket reference to the insolvency does not suffice.
Data processing on behalf: existing and new agreements
Hardly any company processes all data itself. Payroll, hosting, email, cloud storage, maintenance and records destruction are handled by service providers. For each of these relationships, Art. 28 GDPR requires an agreement governing subject matter, duration, type of data and the obligations of the processor.
The debtor’s agreements
Existing data processing agreements are generally linked to a main contract. If the administrator elects performance of that contract under § 103 InsO or actually continues the service, they should check whether the existing agreement meets the requirements and whether it reflects the new controllership. A short supplementary agreement naming the administrator as the body entitled to issue instructions creates clarity. If there is no agreement at all, one must be concluded.
If the main contract ends, Art. 28(3)(g) GDPR must be observed: after the end of the provision of services, the processor must return or delete all personal data at the choice of the controller. Before any termination, it should therefore be established which data are to be exported first. How to deal with service providers that withhold data because of unpaid invoices is covered in a separate article.
New service providers engaged by the administrator
If the administrator engages service providers themselves, for example for preservation, archiving or erasure, they are the controller instructing a processor within the meaning of Art. 28 GDPR. They should choose only providers offering sufficient guarantees of appropriate technical and organisational measures, and conclude the data processing agreement before work begins. The same applies to sub-processors such as data centres used by the service provider.
Technical and organisational measures under Art. 32 GDPR
For data security, the GDPR does not prescribe a rigid programme for insolvency administrators. Art. 32 requires a level of protection appropriate to the risk. In insolvency, the risk shifts significantly: staff leave, maintenance contracts end, premises are cleared, hardware is sold. The measures must follow this situation.
Access
- Take over administrator access and change passwords so that persons who have left no longer have access.
- Block rather than delete the accounts of departing employees so that content remains available for access requests and audits.
- Set up read access for law firm staff, tax advisers and experts separately and with logging.
Availability and integrity
- Create a complete backup outside the production systems and document checksums.
- Test restorability on a sample basis.
- Keep decommissioned systems readable in a controlled environment for as long as retention periods are running.
Physical security and realisation
- Lock server rooms and records archives; collect keys and access cards.
- Before selling hardware, erase all data carriers verifiably. Details are described on the page Data erasure and hardware remarketing.
Notification of data breaches
If a personal data breach occurs, it must in principle be notified to the competent supervisory authority within 72 hours of becoming aware of it under Art. 33 GDPR, unless it is unlikely to result in a risk. Where the risk is high, the data subjects must also be notified under Art. 34 GDPR. A prepared notification procedure with clear responsibilities saves valuable hours in such a case.
Erase or retain?
At the end of the proceedings, the question arises of what happens to the data. Art. 17 GDPR requires erasure when data are no longer necessary for their purposes. Art. 17(3)(b) GDPR restricts this insofar as there is a legal obligation to retain them. For accounting vouchers, commercial books and annual financial statements, the periods of § 257 HGB and § 147 AO apply; for other records, there are in part separate rules.
This results in differentiated treatment: records subject to retention obligations are archived and erased only once the period has expired, and all other personal data are erased as soon as they are no longer needed for the proceedings. Application documents, marketing data and video recordings generally belong to the second group. A written erasure policy specifying which holdings are erased when and by whom is important. Which periods apply in detail is explained in the article Retention obligations for digital records in insolvency. For long-term custody, audit-proof archiving is an option.
An example from practice
A medium-sized trade business is closed down after the proceedings are opened. The customer database contains addresses, order histories and payment information from many years, and the HR system contains payroll records and sick notes. The administrator first preserves all systems in full. Then the accounting, payroll accounts and invoices are transferred to an archive as holdings subject to retention obligations. Sick notes, application documents and newsletter distribution lists, for which there is no retention obligation, are erased once the payroll audits are complete. The erasure is logged. In this way, the proceedings are concluded in a manner that is traceable under data protection law, without destroying records that will still be needed later.
Role of the data protection officer and dealing with the supervisory authority
Whether a data protection officer must be appointed for the debtor is governed by Art. 37 GDPR and § 38 BDSG. Under these provisions, an appointment is required, among other cases, where as a rule at least 20 persons are constantly engaged in the automated processing of personal data. In insolvency, the number of employees often falls quickly. Whether the obligation then lapses or continues because of the nature of the processing must be examined in the individual case. Irrespective of the obligation, it can make sense to keep an existing data protection officer involved for a transitional period, as they know the processes.
Openness towards the supervisory authority is advisable, because there are no general relaxations that the GDPR would grant insolvency administrators. Enquiries should be answered on time and comprehensibly. Coherent documentation of the measures taken is the most effective argument should allegations be raised later. Fines under Art. 83 GDPR are imposed on the controller. Whether this also gives rise to personal risks for the administrator depends on the individual case. General liability issues in the event of data loss are covered in the article Liability for data loss in insolvency proceedings.
How Beweisanker supports you
Beweisanker takes care of the technical side: preservation of all systems with checksums and log, preparation of data holdings for access requests and searches, archiving of records subject to retention obligations and logged erasure before hardware is realised. For these activities, we conclude a data processing agreement with the administrator under Art. 28 GDPR.
The legal decisions that the GDPR requires of insolvency administrators remain with you. We supply the overview, the data and the evidence you need for them. An overview of our services for administrators’ law firms can be found on the page for insolvency administrators. If you would like to discuss specific proceedings, please get in contact.
Frequently asked questions
Does the insolvency administrator have to keep their own record of processing activities?
Insofar as they process the debtor’s data as controller, there is much to be said for continuing the debtor’s record and adapting it to the purposes of the proceedings. If there is no record, one must be created with reasonable effort.
May the administrator analyse the email mailboxes of former employees?
Business correspondence forms part of the debtor’s records. If private use was permitted, private content must be given special protection. The analysis should be purpose-bound, documented and limited to what is necessary.
Who answers access requests in debtor-in-possession proceedings?
In debtor-in-possession proceedings, the debtor remains the controller. Management therefore answers requests itself; the Sachwalter is involved only within the scope of their supervisory task.
Must the debtor’s data subjects be informed of the change of controller?
A general obligation to inform all data subjects of the administrator’s appointment is predominantly not assumed, particularly as the opening is publicly announced. For new processing purposes, however, the information obligations under Art. 13 and 14 GDPR must be examined.
Can an access request be refused because of the insolvency?
No, insolvency alone is not a ground for refusal. An extension of the deadline under Art. 12(3) GDPR is possible, as is, within narrow limits, the refusal of excessive requests or an exception under § 34 BDSG.
This article is for general information only and does not replace legal advice in the individual case.
Direct line
Urgent preservation?
Call us. We usually agree the scope and next steps during the first conversation.
- Response usually on the same working day
- Preservation on site or remotely
- Binding quotation in advance
Read more
More guides
Liquidating a GmbH: checklist for IT and data from the dissolution resolution to custody of the records
What managing directors and liquidators should do with accounts, cloud, accounting, servers, website, hardware and paper records in each phase of the liquidation, so that nothing is missing once the GmbH has been deleted.
Read article →Selling customer data in insolvency: value, permissibility, process
How insolvency administrators realise a customer database in an asset deal, which data may be transferred without consent and how the value of a customer base can be estimated reliably.
Read article →Continuation of business operations: keeping IT running in insolvency
How insolvency administrators keep IT stable during the continuation of business operations: critical systems, service providers and estate liabilities, key personnel, data preservation and an emergency plan.
Read article →