Legal & CompliancePublished on · 8 min read· Author: WSV Redaktion· Reviewed on

Who Is Liable for Data Loss in a Business?

Who bears responsibility when company data is lost - the business, the IT service provider, or an employee? An overview of liability, the GDPR notification duty and compensation, and of how to protect yourself technically and contractually.

Cover image: Who Is Liable for Data Loss in a Business?

Note: This guide does not constitute legal advice. It gives a general overview from the perspective of an IT service company (as of November 2026) and does not replace a review by a lawyer. Whether someone is liable in a specific case, and to what extent, can only be assessed by a lawyer based on the facts.

When a business loses data, the first question is rarely technical - it's legal: who is responsible? The answer depends on the cause, the contractual arrangements, the protective measures in place, and the type of data affected.

Three things are often lumped together, though they need to be looked at separately:

  • Data protection responsibility: Anyone who processes personal data must comply with the GDPR, even if a service provider helps on the technical side.
  • Contractual liability: Anyone who breaches a contractual duty and thereby causes damage must compensate for it if they are at fault.
  • Operational responsibility in practice: Whoever actually runs backups, updates and monitoring decides, day to day, whether data loss happens at all.

In the same incident, these three can point at different people.

Who pays for what? A first overview

Situation Possible consequence
No backup was ordered or set up The loss generally stays with the business, unless a service provider breached a duty.
A provider fails to run an agreed backup Damages under § 280 BGB (German Civil Code) are possible if the breach caused the loss and the provider is at fault.
Employees accidentally delete data Depends on the degree of fault. With minor fault, employees generally aren't liable; with gross negligence, full liability can apply.
Both sides breach their duties Shared responsibility in proportion to each side's share in causing the damage (§ 254 BGB).
Personal data is lost Check the additional GDPR duties: notification, informing affected people, documentation and possible claims for compensation.

Liability for data loss: the business carries the core responsibility

First and foremost, the business itself is obligated. Anyone processing and storing data must implement appropriate technical and organizational measures - working backups, clear responsibilities, access controls, current security updates, and a documented emergency plan. For personal data, Art. 32 GDPR explicitly requires the ability to restore availability quickly after a physical or technical incident, and a process for regularly testing whether the protective measures actually work.

How far this duty of care extends depends on the size of the business and the sensitivity of the data - a trade business is held to different standards than a medical practice. One point matters most: responsibility can't be fully outsourced. Even if a service provider runs your backups, the business remains the responsible party.

Data loss: when is the IT service provider liable?

An external IT service provider is liable when they breach contractually agreed obligations or clearly deviate from recognized security standards - for example, if promised backups didn't actually run or were grossly misconfigured. What counts is proof of a specific breach of duty that actually caused the damage: not every technical fault automatically triggers liability.

Contractual damages rest on § 280(1) BGB. The customer has to prove the breach of duty, the damage and the link between them. The provider's fault, however, is presumed: the provider has to show that it isn't at fault (§ 280(1) sentence 2 BGB). Fault means intent or negligence (§ 276 BGB).

The contract defines what was owed. That's why it pays to review the service description before anything goes wrong:

  • What is backed up? All servers, only certain shares, databases and mailboxes too?
  • How often and for how long? Backup interval and retention period.
  • Who monitors? Who checks that each backup succeeded, and who is notified about failures?
  • Is recovery tested? And who documents the result?
  • Where is liability capped? Liability caps and exclusions are common in IT contracts and should be agreed deliberately.

Limits of liability caps

Many IT contracts cap liability at a maximum amount or exclude certain types of damage. Such clauses have limits:

  • Intent cannot be excluded in advance (§ 276(3) BGB).
  • Essential contractual duties: A clause in standard terms that restricts essential duties so far that the purpose of the contract is endangered is void (§ 307(2) no. 2 BGB). Between businesses, the stricter list of banned clauses in § 309 BGB doesn't apply directly (§ 310(1) BGB), but the content review under § 307 BGB still does.

Whether a specific clause holds up in an individual case is a question for a lawyer. If both sides contributed to the damage, compensation is split according to the share with which the damage was predominantly caused by one side (§ 254(1) BGB). For example: the provider doesn't check the backup, and the business ignores an error message that pointed to the problem.

If the provider processes personal data on your behalf, Art. 28 GDPR also requires a data processing agreement. For GDPR compensation, a processor is only liable if it breached its own obligations under the regulation or acted against lawful instructions (Art. 82(2) GDPR). What to look for when choosing a partner is covered in our guide to selecting an IT service provider.

Employee liability

Employees are subject to their own liability rules. In its decision of 27 September 1994 (GS 1/89 (A)), the Grand Senate of Germany's Federal Labour Court (BAG) recognized the principles of limited employee liability for all work that is caused by the business. The gradation by degree of fault is judge-made law and isn't set out in the statute. In simplified form:

  • Minor fault (slightest negligence): Employees generally aren't liable. The loss stays with the business as an operational risk.
  • Medium negligence: The loss is split between the business and the employee, depending on the circumstances of the case.
  • Gross negligence: Employees are generally liable in full. After an overall weighing of all circumstances, that liability can be reduced.
  • Intent: Full liability.

Accidentally deleting a folder is typically a case of minor fault. Gross negligence - for example, ignoring an explicit instruction about data backups - can lead to a much higher share, in extreme cases full liability. The business has to prove the fault.

That's an argument for securing responsibility structurally: appropriate permissions, a four-eyes principle for critical actions, and backups that a single wrong click can't render useless.

Two key figures that belong in the contract

A working backup alone isn't enough. What matters is how much data loss and downtime your business can accept. Two key figures from emergency planning capture this:

  • RPO (Recovery Point Objective): How much data loss is acceptable, measured in time. A daily backup means up to 24 hours of potential data loss if the failure happens just before the next backup.
  • RTO (Recovery Time Objective): How long recovery may take at most. If it takes two days, operations stay down for two days, even if all the data comes back completely.

Both values follow from how long your business can work without particular systems and how many hours of work it can afford to lose. If nobody has set them, nobody can later check whether the provider meets them. We clarify exactly these questions in the initial consultation. Binding recovery targets always follow from the specific agreement.

Data loss and the GDPR notification duty

If personal data is lost - customer, patient or HR records, for example - additional GDPR obligations apply. Many people underestimate that no cyberattack is needed for this. Art. 4(12) GDPR also counts accidental destruction or loss of data as a personal data breach. The European Data Protection Board (EDPB) makes clear in its Guidelines 9/2022 that a permanent loss exists, for instance, when data has been deleted and can't be restored from a backup copy.

What follows is set out in Art. 33 and 34 GDPR:

  1. Notifying the supervisory authority: without undue delay and, where feasible, within 72 hours of becoming aware of the breach. Notification is only unnecessary if the breach is unlikely to pose a risk to the people affected. An initial notification may be incomplete; details can follow later.
  2. Informing the people affected: additionally and without undue delay if the breach is likely to result in a high risk to them.
  3. Documentation: every breach must be documented internally, including facts, effects and remedial action - even if it doesn't need to be reported.

A temporary loss can also be notifiable if the lack of availability affects people; according to the EDPB, planned system maintenance doesn't count. With ransomware, a successful restore alone is no all-clear if attackers may also have taken data.

These deadlines apply regardless of whether the loss happened internally or at a service provider. A processor must inform you of a breach without undue delay (Art. 33(2) GDPR), but notifying the authority remains your job. The competent authority is the data protection regulator of your German state; in Hesse, for example, the HBDI provides its own notification form. Whether a specific incident must be reported is best clarified with your data protection officer or a legal advisor.

Compensation under Art. 82 GDPR

Affected individuals can claim compensation if they suffered material or non-material damage as a result of a GDPR infringement. In 2023 the Court of Justice of the European Union ruled that the infringement alone isn't enough: the person must prove damage caused by it. However, there is no minimum threshold of seriousness (judgment C-300/21).

Only those who prove they are not in any way responsible for the event causing the damage are exempt from liability (Art. 82(3) GDPR). That's why evidence matters: a backup concept, logs of successful backups, documented restore tests and an emergency plan. Separately from compensation, the supervisory authority can impose fines; their amount depends on many factors in each case.

Practical example: who is responsible?

Hypothetical example: at a tax advisory firm, the file server fails. The last working backup is three weeks old, because the error messages from the backup job went unnoticed for weeks. The potential data loss is therefore far beyond what the firm would accept. In an emergency, questions come up quickly that only the contract, logs and clear responsibilities can answer:

  • Who was responsible for monitoring the backup: the firm itself or a service provider?
  • Was an error message ignored, and who should have seen it?
  • Was recovery owed under the contract, or only the backup itself?
  • Is this a breach of duty, an employee's mistake, or both - and what damage resulted?
  • Is client data permanently lost? If so, the notification duty under Art. 33 GDPR applies.

Reducing risk in practice

The most effective way to avoid liability is to prevent the incident - and to be prepared in case it happens anyway:

  • Automated, regularly tested backups instead of manual one-off actions. Our guide to backup strategy for SMEs explains how to set this up, including the 3-2-1-1-0 rule and restore tests.
  • Clear roles and access rights, so it's traceable what happened if something goes wrong.
  • Current security updates, to avoid technical causes of data loss in the first place.
  • A documented emergency plan that also covers the reporting process under Art. 33 GDPR. Our guide to the IT emergency plan for businesses shows how to build one.
  • Clearly worded contracts with IT service providers that define scope, monitoring, recovery targets and responsibilities.

Checklist

  • Is the backup demonstrably working - verified through real restore tests?
  • Are responsibilities for backup, monitoring and recovery clearly defined in writing?
  • Are RPO and RTO defined for your most important systems?
  • Are liability caps in the contract specific, and have they been reviewed by a qualified professional?
  • Is a data processing agreement in place wherever a provider processes personal data?
  • Is there a documented process for reporting incidents involving personal data, including the 72-hour deadline?
  • Is an emergency plan in place and known to those responsible?

Frequently asked questions

Who is liable for data loss in a business? First the business itself, because it is responsible for appropriate protective measures. An IT service provider is liable if it breached a contractual duty and thereby caused the damage; its fault is presumed. Employees generally aren't liable for minor mistakes. With gross negligence, full liability can apply, which can be reduced after an overall weighing of all circumstances.

Do I have to report data loss that wasn't caused by an attack? Possibly, yes. Accidental loss of personal data is also a personal data breach. It must be reported unless it is unlikely to pose a risk to the people affected; every case must be documented.

When does the 72-hour deadline start? From the moment you become aware of the breach. According to the EDPB, that is when you have a reasonable degree of certainty that an incident has affected personal data. If a service provider informs you of the incident, the deadline generally starts with that notification.

Is the IT service provider automatically liable if the backup fails? No. It depends on what was contractually agreed and whether a specific breach of duty caused the damage.

Does a working backup protect me from the notification duty? It lowers the risk considerably because the data isn't permanently lost. But if data was stolen or unavailable for a longer period, notification may still be required.

Conclusion

Liability for data loss is rarely a matter of chance - it's a matter of preparation: working backups, clear responsibilities, defined recovery targets, a reporting process and solid contracts reduce the risk, and show in an emergency that you met your duty of care.

On the technical side, our Online Backup provides automatic, nightly, encrypted backups of your server data with monitoring. An IT Emergency Plan documents your business-critical systems as well as backup and recovery, and is suitable as proof for your liability or business interruption insurance. With 20 employees, we look after more than 300 servers and more than 1,500 endpoints.

Do you know exactly who monitors your backups and how long a restore would take? Our Backup Check and Restore Test reviews the scope, frequency, retention and storage locations of your existing backup and tests recovery.

For specific liability questions, this overview doesn't replace legal advice. For the technical side, we're happy to help: Book a free initial consultation.

Sources

Updated on

WhatsAppRequest adviceGet support

Get in touch

Privacy settings

We use cookies and other technologies on our website. Some of them are essential, while others help us improve this website and your experience. Personal data may be processed (e.g. IP addresses), for example for personalized ads and content or ad and content measurement.

There is no obligation to consent to the processing of your data in order to use this offer. You can withdraw or adjust your selection at any time under settings. Please note that due to individual settings, not all functions of the website may be available.

We use technically necessary storage for operating this website. Optional services (statistics, marketing, external media) are only loaded after your consent.

Privacy settings