Friday, 5:40 pm. A systems administrator notices that someone has downloaded a month-old export of the customer database from a test server. By Monday the team is still working out whether the file held real data, and on Monday morning the data protection officer asks one question: at what time did the company know enough to treat this as a personal data breach. The answer decides whether the notification reaches the supervisory authority on time or with an explanation for the delay.
GDPR breach notification is a controller’s obligation under Article 33, but in practice it starts in the IT department and in the team responsible for cybersecurity, because that is where the first information about an incident appears. The Article 33 deadline is only short for a company that works out during the incident who assesses the risk, who fills in the form and who signs the notification. In Poland the notification goes to UODO, the Polish supervisory authority; authorities in other EU Member States publish their own forms and channels.
What is a personal data breach that you have to notify?
A personal data breach is, under Article 4(12) GDPR, a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. The definition therefore covers not only a leak, but also loss of access to data, for example after a server is encrypted, and unauthorised changes to data.
A breach must be notified if it is likely to result in a risk to the rights and freedoms of natural persons.
The UODO guide on personal data breaches (in Polish), published in February 2025, stresses an important distinction: a personal data breach does not in itself mean that the GDPR has been infringed. The guide’s example is a hospital that implemented appropriate safeguards and was still hit by an attack exploiting a previously unknown vulnerability. A personal data breach occurred, even though the controller did not break the law. The definition of the phenomenon and its causes are covered in our article on what a data leak is and where to report it.
Legal position as of 13 October 2026. Articles 4, 33 and 34 GDPR have not been changed by any amending act since the regulation was adopted in 2016.
When do the 72 hours for breach notification start?
The deadline starts when the controller becomes aware of the breach, not when the breach happened. Article 33(1) GDPR requires notification without undue delay and, where feasible, not later than 72 hours after having become aware of it.
UODO defines becoming aware (in the Polish text, “stwierdzenie”) as the moment when the controller gains sufficient knowledge of an incident to treat it as a personal data breach. According to the guide, this happens when the controller knows that the event is a security incident, concerns personal data it processes and may lead to the consequences described in Article 4(12).
The EDPB Guidelines 9/2022, version 2.0 of 28 March 2023, refer to a “reasonable degree of certainty” that a security incident has occurred that has led to personal data being compromised. They allow a short period of investigation during which the controller is not yet regarded as aware, but expect it to begin as soon as possible. A more detailed investigation can then follow.
There is no formal act of becoming aware, but UODO recommends recording its time precisely, because it is needed in the notification and in the documentation. In the Friday scenario, that moment is when the team confirmed that the export contained real customer data. The time entered in the notification should come from the incident log, not from the participants’ memory.
Key points:
- The clock in Article 33(1) GDPR starts when the controller becomes aware of the breach, not at the time of the attack or the end of the investigation.
- The deadline also runs at weekends and on public holidays.
- The time of becoming aware must be recorded, because it goes into the notification and the breach documentation.
When do you not need to notify the supervisory authority?
You do not need to notify a breach that is unlikely to result in a risk to the rights and freedoms of natural persons. This is the only exception in Article 33(1) GDPR, and UODO points out that it covers exceptional situations in which the controller must be able to demonstrate the absence of risk.
The risk assessment has three possible outcomes: no risk, a risk that requires notifying the President of UODO, or a high risk, which also requires communicating the breach to the individuals concerned. The guide lists the circumstances to assess: the type of breach, the nature and scope of the data, how easily individuals can be identified, the severity of consequences, special characteristics of the individuals and of the controller, and the number of people affected.
You assess the consequences for people, not for the company. UODO reminds controllers that what the organisation itself would suffer does not matter in this assessment, and that the risk is assessed, not the harm actually caused. The argument that “nobody has reported any misuse yet” does not release you from the obligation.
An example from the guide is instructive: servers holding an insurance company’s backups burned down at a processor. The controller established that it held its own complete copy of the data and, according to UODO, rightly did not conclude that a personal data breach had occurred. Well-designed backups work here as a legal argument, not just a technical one.
What must a breach notification contain under Article 33(3)?
The notification must contain at least the four elements listed in Article 33(3)(a)–(d) GDPR:
- A description of the nature of the breach, including where possible the categories and approximate number of data subjects and the categories and approximate number of personal data records concerned.
- The name and contact details of the data protection officer or other contact point.
- A description of the likely consequences of the breach.
- A description of the measures taken or proposed to address the breach, including measures to mitigate its possible adverse effects.
UODO recommends providing more than the minimum: details of the controller and other parties involved in the incident, the date and time when the breach occurred, when the controller became aware of it and when it ended, how it was detected and its cause, the justification for the risk assessment, remedial actions with declared dates, and information on communicating the breach to individuals or the reasons for not doing so.
The guide also warns against excess. A notification with incomplete or excessive information slows down verification and delays the response. In practice, this means raw logs stay in the company’s documentation and an accurate summary of them goes into the notification.
How do you notify UODO, and what if you lack some facts?
In Poland, the notification is submitted on the form provided by UODO, through one of four channels listed in the guide: the dedicated electronic form on the biznes.gov.pl platform, the form sent to UODO’s electronic inbox on ePUAP (/UODO/SkrytkaESP), a general letter via biznes.gov.pl or ePUAP, or traditional post to the authority’s address.
If the electronic notification systems fail, UODO allows the notification to be sent temporarily by email to kancelaria@uodo.gov.pl. Once the failure is over, the notification must be confirmed using one of the standard methods.
It is worth deciding in advance who submits the notification on the company’s behalf through biznes.gov.pl or ePUAP, and who stands in for them. UODO does not accept the holiday of the responsible person without a substitute, or management not having time to approve the notification, as justification for a delay.
If facts are missing, you notify what you already know and supplement the rest. Article 33(4) GDPR allows the information to be provided in phases without undue further delay where it cannot all be provided at the same time.
UODO distinguishes three types of notification: initial, which provides basic information on time with an obligation to supplement it later; supplementary, which updates the information about the incident; and complete, containing everything in the first notification. An initial notification is safer than waiting for the full picture.
If the notification is made after 72 hours, the second sentence of Article 33(1) requires it to be accompanied by reasons for the delay. The guide lists excuses UODO will not accept, including waiting for an internal investigation or risk assessment to finish, and the need to gather all information, given that an initial notification is possible.
What roles do the processor and the data protection officer play?
The processor notifies the controller without undue delay after becoming aware of a personal data breach (Article 33(2) GDPR), and the controller decides whether to notify the authority. In Guidelines 9/2022 the EDPB points out that the processor does not need to assess the risk first and, in principle, considers the controller “aware” once the processor has informed it.
For data processing agreements this has a concrete consequence: the controller’s clock starts when the supplier informs it, so every hour of delay on the supplier’s side shortens the controller’s time. According to the EDPB, the processor should inform the controller promptly and provide further information in phases as more details become available.
UODO adds that a processor may notify the authority only with the controller’s written permission, set out in the contract. Such an arrangement does not release the controller from ultimate responsibility for the notification, and joint controllers should agree in advance how this obligation is divided.
The data protection officer appears in the notification itself: Article 33(3)(b) requires the contact details of the DPO or another contact point. The officer’s tasks and the conditions for appointing one are covered in a separate article on who a data protection officer is.
When do you also have to inform the individuals concerned?
You must communicate the breach to the individuals concerned without undue delay if it is likely to result in a high risk to their rights and freedoms (Article 34(1) GDPR). The threshold is therefore higher than for notifying the authority, which requires only a risk.
Article 34(3) removes the obligation in three situations: when the data were protected by measures that render them unintelligible to unauthorised persons, such as encryption; when the controller has taken subsequent measures ensuring that the high risk is no longer likely to materialise; and when communication would involve disproportionate effort. In the last case, a public communication is needed instead of individual messages.
Encrypting laptop disks therefore does not remove the obligation to assess the incident, but it may decide that individuals do not need to be informed. Where there is no high risk, UODO does not recommend informing individuals, because excessive messages cause unnecessary stress.
How does a GDPR breach notification differ from a NIS2 incident report?
A GDPR notification concerns personal data and the protection of individuals’ rights, while a NIS2 report concerns significant incidents in the services of essential and important entities. The NIS2 Directive defines an incident in Article 6(6) as an event compromising the availability, authenticity, integrity or confidentiality of data or of the services offered by network and information systems.
The deadlines differ as well: NIS2 provides for an early warning within 24 hours at the latest of becoming aware of a significant incident and an incident notification within 72 hours (Article 23(4)(a) and (b)). The recipient is the CSIRT or the competent authority, not the data protection authority.
The directive does not, however, apply directly to companies. In Poland it is transposed by the Act on the National Cybersecurity System, as amended by the act of 23 January 2026 (Journal of Laws 2026, item 252), in force since 3 April 2026. It is the amended Act that sets the obligations of a specific entity.
One event can trigger both regimes at once: a ransomware attack at an essential entity that encrypted the customer database may be a significant incident and is also a breach of personal data availability. Your incident response procedure should therefore run two clocks and two notifications, each with its own owner.
How should you document breaches you do not notify?
Every breach must be documented, including those not notified: Article 33(5) GDPR requires a record of the facts, their effects and the remedial action taken, and the documentation must enable the authority to verify compliance with Article 33.
UODO goes further and recommends documenting incidents the controller classified as events that are not breaches, together with the reasons for that decision. In the example of the servers burning down at a supplier, such a record proves that the company assessed the event rather than overlooked it.
According to UODO, a separate internal breach register is not mandatory, but it helps, provided the information is clearly marked and available for inspection. In practice, an incident register kept by the IT department can serve this purpose if it has fields for the risk assessment for individuals and the notification decision. When an entry identifies the system the data leaked from, it is easier to consult the record of processing activities and establish the categories of individuals and data.
How do you prepare your company for the first 72 hours after a breach?
You prepare your company for the Article 33 deadline before an incident, by assigning every decision to a person and to a trace in the documentation. Failure to comply with Article 33 falls under Article 83(4)(a) GDPR, which provides for fines of up to EUR 10,000,000 or up to 2% of a company’s total worldwide annual turnover (Article 83 GDPR), and the way such fines are calculated in decisions of the Polish authority is described in our article on GDPR fines.
The first three days are organised around the decisions that have to be made, not around technical activities.
| Stage | Decision | Who decides | Trace in the documentation |
|---|---|---|---|
| Detection of the event | is it a security incident and does it concern personal data | IT on-call or incident response team, informing the DPO | incident log entry with the time of detection |
| Becoming aware of the breach | is the knowledge sufficient to treat the event as a personal data breach | controller, with the DPO | time of becoming aware and the basis for that assessment |
| Risk assessment | no risk, risk or high risk for individuals | DPO or a person designated by the controller | justification of the assessment against UODO criteria |
| Notification to UODO | initial or complete notification | authorised signatory and their deputy | copy of the notification and proof of submission |
| Communication to individuals | does the high risk require communication and does an Article 34(3) exception apply | controller | text of the communication or reasons for not communicating |
| NIS2 report | is the event a significant incident | owner of the NIS2 procedure | early warning and notification with times |
| Follow-up | what findings must be sent later | DPO with the incident response team | supplementary notifications and remedial action plan |
The technical team wants a complete set of findings while the clock is already running, so the risk assessment starts in parallel with the detailed investigation, not after it ends.
How can nFlo help you handle a personal data breach?
nFlo helps with both parts of breach handling: the organisational and compliance side and the technical side. The Data Protection Officer (DPO) Outsourcing service in the “Governance, risk and compliance” area covers the DPO function, compliance oversight, employee training and contact with UODO, and in the event of a breach, coordination of the notification within the Article 33 deadline, help with the risk assessment and preparation of communications to the individuals concerned.
The Incident Response service covers threat containment, forensic analysis with evidence preservation, eradication and system recovery, and the team prepares technical information and the attack timeline for the notification. Formally, the data controller submits the notification, and nFlo does not provide legal advice. If you want to check whether your procedure fits within 72 hours, contact us. Wider background on the controller’s obligations can be found in our GDPR guide, in the GDPR glossary entry and in our GDPR knowledge base.
What else should you know about notifying breaches to UODO?
Are the 72 hours for breach notification counted in working days?
No. The deadline in Article 33(1) GDPR runs regardless of days off, and UODO does not accept a weekend or the holiday of the responsible person as justification for a delay.
Can you notify a breach without having all the facts?
Yes. Article 33(4) GDPR allows information to be provided in phases. UODO calls this an initial notification, followed by supplementary notifications.
Can a processor notify the supervisory authority itself?
As a rule, the controller notifies. According to UODO, a supplier may notify the authority only with the written permission of the controller, which remains responsible for the notification.
Does notifying a breach mean the company has broken the GDPR?
No. According to UODO, a notification is not evidence of fault, does not determine that the law has been infringed and does not automatically open proceedings.
Do you have to document breaches you do not notify?
Yes. Article 33(5) GDPR covers any personal data breaches, and UODO recommends documenting incidents classified as non-breaches as well, with the reasons for that decision.
