Direct Answer
Under GDPR Article 33, a company must report a personal data breach to its supervisory authority within 72 hours of becoming aware of it, unless the breach is unlikely to put people’s rights and freedoms at risk. If the risk is high, the affected people must also be told without undue delay, and every breach has to be documented internally, even when it isn’t reported. German companies report to the data protection authority of their federal state, and deeploi, the All-in-One IT Management Platform for SMBs, helps them respond faster with encrypted devices, a live device inventory and remote lock and wipe.
Key Takeaways
Article 33 GDPR gives you 72 hours from becoming aware of a personal data breach to notify your supervisory authority, unless the breach is unlikely to result in a risk to people's rights and freedoms.
The clock starts when you have reasonable certainty that a breach occurred, not when the incident itself happened.
German companies report to the data protection authority of the federal state where their main establishment sits, usually through an online form.
Affected people must be told separately, without undue delay, if the breach is likely to create a high risk for them.
Every breach has to be documented internally, even the ones you decide not to report.
A data breach rarely announces itself politely. It shows up as a laptop left on a train, a password typed into a fake login page, or an email from a software vendor saying their systems were accessed. From the moment you understand what happened, the 72-hour GDPR notification deadline is already running. This guide walks through it for teams without a legal department or a security team on standby.
What counts as a personal data breach under GDPR?
A personal data breach is any security incident that leads to the destruction, loss, alteration, unauthorized disclosure of, or unauthorized access to personal data. That definition is wider than most people expect. It covers loss of confidentiality, loss of availability, and loss of integrity.
In practice, for a company of 20 to 100 people, it looks like this: an email with a client list sent to the wrong recipient, a shared folder accidentally set to public, a ransomware infection that locks your only copy of HR records, or an account taken over after someone clicked a phishing link at work.
Take two versions of the same lost laptop. In the first, the disk is encrypted with BitLocker or FileVault, the key is safe, and the device gets wiped remotely. Nobody can read the data, and as long as it also exists in a backup or in the cloud, the incident is very unlikely to put anyone at risk and generally does not need to be reported. If the laptop held the only copy, the loss of availability can still be a reportable breach. In the second version, the machine has no encryption and a local copy of your customer database. That is a reportable breach, and our guide to lost or stolen company devices covers the first hour in more detail.
One rule has no exceptions: you document every breach internally, including the ones you decide not to notify, together with the reasoning behind that decision.
When does the 72-hour clock actually start?
The clock starts when you become aware of the breach, meaning the point at which you have a reasonable degree of certainty that a security incident compromised personal data. A vague suspicion is not awareness. A short investigation to confirm what happened is allowed, but you cannot stretch it out to delay the deadline.
So if a server was accessed in March and you discover it in June, the 72 hours begin in June. Weekends and public holidays count.
Vendors complicate this. If a SaaS provider processes data on your behalf, they must inform you without undue delay once they detect a breach, and you still own the notification to the authority. In Verizon's 2026 breach dataset, 48% of analyzed breaches involved a third party, including cases involving software vulnerabilities (Verizon). That is a share of analyzed breaches, not a probability for any single company, but it explains why your processor contracts should name a notification channel and a deadline.
How do you report a data breach in Germany?
You report to the supervisory authority of the federal state where your company has its main establishment. Each state has its own authority, and the federal commissioner (BfDI) handles telecommunications providers and federal bodies. Nearly all of them publish an online notification form, and it is worth bookmarking yours now rather than searching for it at 2am.
Your notification needs to describe the nature of the breach, the categories and approximate number of people and records affected, a contact point (your data protection officer, if you have one), the likely consequences, and the measures you have taken or propose to take.
You do not need every answer at once. Article 33(4) allows phased reporting: send what you know within 72 hours and supply the rest as the investigation continues. Reporting volumes are rising, too. The Saxon data protection authority received 1,400 personal data breach notifications by the end of October 2026, compared with 1,058 during the whole of 2025 (Saxon Data Protection and Transparency Commissioner).
If your company falls under NIS2, a second clock runs in parallel: an early warning to the authorities within 24 hours. Our overview of GDPR, NIS2 and BSI requirements explains which rules apply to whom.
When must you also notify affected individuals?
Article 34 adds a second duty: if the breach is likely to result in a high risk to people, you have to tell them directly, in plain language, without undue delay.
High risk in a small company usually means financial data, health or other special category data, login credentials that could be reused elsewhere, or anything that could lead to identity theft, discrimination, or reputational harm. A misdirected newsletter with first names only sits well below that bar. A leaked payroll file does not.
What happens if you miss the 72-hour deadline?
A late notification is still better than no notification, and the regulation expects you to include the reasons for the delay. Authorities generally respond better to an honest, documented account than to silence.
Failures to notify under Articles 33 and 34 fall into the lower fine tier of Article 83(4): up to 10 million euros, or 2% of total worldwide annual turnover, whichever is higher. Missing documentation is treated as its own failure, so a breach you correctly chose not to report can still cost you if nothing was written down. Keeping that audit evidence traceable is the cheapest part of the whole exercise.
{{cta}}
Your hour-by-hour plan for the first 72 hours
Hour 0 to 1: contain and start the log
Lock or wipe the affected device, reset the credentials involved, and sign out active sessions. Open a written log with timestamps and keep adding to it. Bring in your data protection officer now. German law (§38 BDSG) generally requires one once at least 20 people are constantly involved in the automated processing of personal data.
Hour 1 to 24: assess the risk
Work out which data categories were affected, roughly how many people, and what could realistically happen to them. Contact any vendor involved and ask for their incident report in writing. Then decide: reportable, or documented only. Owner: the founder or operations lead, advised by the DPO.
Hour 24 to 72: report and document
File with your state authority, notify affected individuals if the risk is high, and record every decision including the ones you rejected. Close the gap that caused the incident. Owner: the same person who filed, so nothing falls between desks.
Frequently asked questions
Can our managing director be held personally liable for a missed notification?
Usually the company itself is the controller and the addressee of fines and damages. Under German company law (§43 GmbHG), managing directors can be liable to the company if they fail to organize or supervise data protection properly, and setting up a working incident process is a leadership duty. This article is general information, not legal advice, so check your situation with a lawyer.
Do we still need to report if the breached data was encrypted?
If the data was encrypted with a current method and the key was not compromised, the breach is usually unlikely to put anyone at risk. In that case no notification to the authority or to affected people is required. You still document the incident, including proof that encryption was active on that device.
What technical measures reduce breach risk before an incident happens?
Full disk encryption, role-based access with multi-factor authentication, patch management, and a current device inventory form the baseline, as set out in our GDPR IT compliance checklist for SMBs. deeploi, the All-in-One IT Management Platform for SMBs with or without an in-house IT team, shows each device’s encryption status and keeps an up-to-date device inventory alongside central device administration. When a laptop goes missing, you can lock or wipe it remotely and prove it was protected, with IT experts on hand to help contain the incident.
What if we have no IT team at all?
Write the process down anyway. One page naming who contains, who assesses, and who files is enough to start, and pairing it with automated security policies keeps the basics enforced rather than requested.
Preparation beats reaction
The companies that handle the 72-hour GDPR notification deadline calmly are not the ones with the biggest budgets. They are the ones who decided in advance who does what, kept their technical controls documented, and built the habits described in our cybersecurity guide for small businesses. With that in place, a breach becomes a checklist instead of a scramble.
Note: This article is for general information only and does not constitute legal advice. Notification duties under the GDPR and NIS2 depend on your specific situation. For a binding assessment, consult your data protection officer or a qualified lawyer.









