UODO Explains When a Personal Data Breach Need Not Be Reported
Poland's UODO says a breach of data already public in the CEIDG register may not need reporting, while PESEL numbers, health and financial data usually mean a risk and a report. Every breach still needs a documented risk assessment in the breach register.
What happened
On 5 October 2026 the Polish data protection authorityAn independent public body that supervises compliance with data protection law. Under the GDPR, such authorities monitor and enforce its application, handle complaints and exercise investigative and corrective powers. (UODO) published guidance that not every personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms. has to be reported to its President. It follows recent incidents of unauthorised access to contractor databases and invoicing systems.
What it changes
Under art. 33(1) of the GDPRGeneral Data Protection Regulation, a controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it. reports a breach without undue delay unless the breach is unlikely to result in a risk to people. UODO says a report may not be needed when the exposed data is already public in the CEIDG business register, such as a name, business name, tax number and business address. A risk is likely when the breach involves a PESEL number, health or other special category data, or financial information. In every case the controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it. must carry out and document a risk assessment and record its reasons in the internal breach register.
Who is affected
Every controllerThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it. subject to UODO, in particular those whose suppliers’ invoicing or customer systems were breached.
What to do now
- Check your breach procedure against the UODO examples.
- Make sure every breach, reported or not, has a documented risk assessment in the breach register.
- Treat breaches involving PESEL, health or financial data as reportable unless your assessment shows otherwise.
Incident Reporting Desk
We would review your breach procedure against the UODO examples and help you assess, document and, where needed, report each breach on time.
