Guides

Insolvency administrator liability for data loss

Under what conditions a data loss can raise liability issues under § 60 InsO and the GDPR, and how preservation records and hash values reduce the risk.

Two years after the opening of proceedings, the tax office (Finanzamt) announces a tax audit. The auditor requests access to the accounting for the last few financial years. However, the debtor’s server was sold with the rest of the office equipment shortly after business closure, and the cloud account has been deleted for months. What follows are estimates, queries and the uncomfortable question of whether the data loss was avoidable. This guide sets out under what conditions insolvency administrator liability for data loss may come into consideration and how the risk can be reduced in practice.

The standard of liability under § 60 InsO

Under § 60 InsO (German Insolvency Code), the insolvency administrator is liable to all parties for damages if he culpably breaches the duties incumbent on him under the Insolvency Code. He must exercise the care of a prudent and conscientious insolvency administrator. The provision is linked to insolvency-specific duties, i.e. duties that arise specifically from the office.

According to the general view, liability requires several elements: an insolvency-specific duty, its breach, fault, damage suffered by a party and a causal link. Whether these requirements are met depends heavily on the circumstances of the individual case. A data loss therefore does not automatically lead to liability. It may, however, be a reason to examine the question.

This guide describes areas of risk, not fixed liability consequences. Whether liability comes into consideration in a specific case must always be examined legally on an individual basis.

Which duties relate to data

Taking possession under § 148 InsO

After the opening, the administrator must immediately take possession and control of all assets belonging to the insolvency estate. Under § 36(2) no. 1 InsO, business books belong to the insolvency estate. If they are kept electronically, taking possession is widely understood to include the data and access to it. For data, taking possession means above all: establishing control over systems and access rights and protecting the data holdings from alteration and loss.

Bookkeeping and accounting duties under § 155 InsO

§ 155 InsO leaves the bookkeeping and accounting duties under commercial and tax law unaffected and transfers their performance in relation to the insolvency estate to the administrator. These include retaining the records and, where bookkeeping is electronic, enabling data access by the tax authorities. Details of the periods can be found in the guide on retention obligations for digital records.

Securing and realising the insolvency estate

The administrator must secure the insolvency estate and realise it as well as possible. Data has a dual function here: it is the working basis for debt collection and avoidance, and it can itself be an asset, such as customer data or software. An avoidable loss can therefore also impair realisation.

Responsibility under data protection law

Alongside the Insolvency Code, the GDPR (DSGVO) applies. According to the prevailing view, the insolvency administrator acts as controller with regard to the debtor’s data that he processes. This gives rise to separate duties:

  • Art. 5 GDPR: Principles of processing, including integrity and confidentiality as well as accountability. The controller must be able to demonstrate compliance.
  • Art. 32 GDPR: Appropriate technical and organisational measures to ensure security of processing, such as encryption, access restrictions and the ability to restore the availability of data.
  • Art. 82 GDPR: Right of data subjects to compensation in the event of infringements, for both material and non-material damage.

Data loss is only one side of this. Uncontrolled disclosure, for example through the sale of hard disks that have not been wiped, and unauthorised access are equally relevant. How storage media are verifiably erased before realisation is described on the data erasure and hardware remarketing page.

Typical risk scenarios from practice

Certain constellations come up again and again. They show where a data loss can raise questions about the performance of duties:

  1. Terminated cloud services: A contract for email, file storage or industry software is ended or suspended because of payment arrears. After the grace period expires, the provider deletes the data.
  2. Computers sold or disposed of: Hardware is realised in the course of the business closure before the data has been preserved. If storage media are not erased, a data protection problem is added.
  3. Missing vouchers in the tax audit: If records are missing, the tax authorities can estimate the tax bases. This can lead to liabilities of the insolvency estate that would not have arisen with complete data.
  4. Failed avoidance for lack of evidence: The administrator generally bears the burden of presentation and proof for the requirements of an avoidance claim. If proof of payment or correspondence is missing, a claim that in itself exists may under certain circumstances not be enforceable.
  5. Lost access: The debtor’s administrators can no longer be reached, passwords and authentication means are missing. The data still exists but is in practice inaccessible.

In all scenarios, the question arises with hindsight whether the loss would have been avoidable with proper procedure. Whether liability follows from this is a question for the individual case. The mere possibility of this discussion, however, is reason enough to treat data preservation as an integral part of how proceedings are organised.

How documentation and hash values reduce the risk

A central aspect of any liability question is the ability to provide proof. Anyone who can later show when which data was preserved and to what extent is in a much better position than someone relying on memory.

The following elements have proven effective:

  • Preservation record: Date, time, place, person carrying out the work, systems preserved and scope. Deviations and data holdings that could not be preserved are expressly noted.
  • Hash values: For each image, a hash value, for example using SHA-256, is calculated and documented. This makes it possible to prove later that the data holding is unaltered.
  • Inventory of data sources: An overview of all systems, cloud services and storage media with their respective preservation status.
  • Documented decisions: If a deliberate decision is made not to preserve a data holding, for example because it is not relevant, the reasons should be recorded.
  • Erasure certificates: Before hardware is realised, the erasure or destruction of the storage media is documented.

This documentation also serves the accountability obligation under Art. 5(2) GDPR. For the taking of evidence in avoidance litigation, the guide on data preservation, archiving and evidence preservation describes the connections in more detail.

A backup without a record is of only limited reliability in a dispute. Document scope, time and hash values immediately at the time of preservation, not after the fact.

Organisational precautions in the proceedings

Liability risks rarely arise from a single wrong decision, but mostly from missing procedures. It helps to include IT preservation as a standard step in the routine of proceedings:

  • Early enquiry about the debtor’s IT landscape, already in the preliminary proceedings.
  • Clear instruction to the debtor, employees and service providers not to delete any data and not to dispose of any hardware.
  • Review of ongoing contracts involving data before any termination.
  • Approval of hardware remarketing only after documented preservation and erasure.
  • Determination of how long and in what form the data will be retained.

A practical sequence of the first steps is contained in the checklist for IT preservation after the insolvency petition. It also makes sense to clearly assign responsibility for IT matters within the law firm, so that indications of endangered data holdings do not get lost between case handling and accounting.

Professional indemnity insurance

Insolvency administrators generally maintain professional indemnity insurance for financial losses. Whether and to what extent it covers damage in connection with data loss or data protection infringements depends on the respective policy terms. It is advisable to clarify the scope of cover for IT and data protection risks with the insurer. Insurance does not, however, replace proper preservation; at most it absorbs financial consequences.

Support from specialised service providers

Preservation can be entrusted to a specialised service provider who carries out and documents the technical steps. Responsibility for selection and supervision remains with the administrator. Where personal data is involved, a data processing agreement under Art. 28 GDPR is also required.

Beweisanker carries out the insolvency data preservation with a preservation record and hash values and hands over documentation that traceably evidences the preserved state.

Frequently asked questions

Is the insolvency administrator automatically liable if data is lost?

No. Liability under § 60 InsO requires a culpable breach of insolvency-specific duties and damage caused by it. Whether these requirements are met must be examined in the individual case.

Does the duty to preserve data already apply in the preliminary proceedings?

Under § 22 InsO, the preliminary administrator must secure and preserve the assets. Via § 21(2) no. 1 InsO, the liability provisions apply to him accordingly. Early preservation therefore makes sense in this phase as well.

What role does the GDPR play in data loss?

According to the prevailing view, the administrator is the controller for the processing of the debtor’s data. He must take appropriate security measures under Art. 32 GDPR. Data subjects can assert claims under Art. 82 GDPR in the event of infringements.

How do I prove later that I preserved data properly?

Through a contemporaneous preservation record, hash values for each image and documented decisions on data holdings that were not preserved.

This guide is for general information purposes and does not replace legal advice in an 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 →

Every day counts.

Talk to us as soon as proceedings are on the horizon. Together we establish which systems are affected and what needs to be preserved first.

Operating nationwide (Germany) · on site at short notice in Baden-Württemberg and German-speaking Switzerland