---
title: "UODO Explains When a Personal Data Breach Need Not Be Reported"
url: "https://grc.plus/updates/uodo-when-breach-need-not-be-reported/"
type: "Update"
updated: "2026-11-15"
publisher: "GRC+"
---

# UODO Explains When a Personal Data Breach Need Not Be Reported

## What happened

On 5 October 2026 the Polish data protection authority (UODO) published [guidance](https://uodo.gov.pl/pl/138/4596) that not every personal data breach 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 GDPR, a controller 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 controller must carry out and document a risk assessment and record its reasons in the internal breach register.

## Who is affected

Every controller 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.

Principal Consultant

## [Ahmet Ucar](https://grc.plus/consultant/ahmet-ucar/)

Helps clients comply with their regulatory requirements with a plan their board can approve.

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)
