Let’s talk
Wondering how this plays out in your organisation? Get in touch — I answer personally.
Short answer
The GDPR does not speak of a register but of documentation. The controller documents any personal data breach, including the facts relating to it, its effects and the remedial action taken (Article 33(5) GDPR). The documentation must enable the supervisory authority to verify compliance with Article 33 as a whole, including whether the decision not to notify was correct. An entry combines the requirements of the Regulation with the scope indicated in the guidance of the President of UODO. It gives the date and time of occurrence, of becoming aware and of closure of the breach and how the breach was detected. It describes the type, cause and course of the breach, the type and scope of the data and the number and categories of data subjects. It contains the effects and possible effects, the reasoning behind the risk assessment and the remedial and preventive action. It also gives the date of notification, any reasons for delay and other relevant information in the notification or the reasons for the decision not to notify. For the communication to data subjects the entry records its date, content and method and the number of people reached or the reasons for the decision not to communicate. The reasons for not communicating show the absence of a high risk (Article 34(1)) or an exception under Article 34(3). The entries that call for the most content are those concerning breaches the controller did not notify. The President of UODO does not recommend putting personal data in the register.
Have an incident right now? Find out in 5 minutes
The “I have an incident – what now?” tool gives a preliminary indication of which deadlines under the GDPR and the Polish KSC Act are already running. At the end, you can download an action plan as a PDF. Free of charge, no account required and no cookies.
Why the question arises at all
A breach register is often kept as a list of cases sent to the supervisory authority. What results is a document that duplicates knowledge the authority already has. It says nothing about the cases resolved internally. Those cases are subject to verification as well, and the decision not to notify is demonstrated through documentation.
The second source of confusion is terminological. Article 33(5) GDPR does not use the word “register” and imposes no form. The President of the Personal Data Protection Office (UODO) states expressly that an internal breach register may help in meeting the obligation. Keeping a separate record is not mandatory, however. What matters is that the information is clearly marked and available for inspection. The obligation is therefore an evidential result, not a table. The position is different for providers of electronic communications services, which Article 405(1) of the Polish Electronic Communications Law requires to keep a register of personal data breaches.
The third source is organisational and becomes visible only over time. An entry is usually created on the day the case is closed. It then contains a summary sufficient for the people who worked on it. A year later the same entry is read by someone else, most often for the purposes of proceedings. That is when it turns out that what is missing is not facts but reasons.
It is also worth separating two documents that are confused because their names are similar. The record of processing activities under Article 30 GDPR describes what the organisation processes day to day and why. The breach documentation under Article 33(5) describes events and decisions. These are two different obligations with different evidential functions.
What to establish before deciding
What the Regulation requires and what it does not
The Regulation requires three things.
- Document any personal data breach.
- Cover the facts relating to the breach, its effects and the remedial action taken.
- Ensure that the documentation enables the supervisory authority to verify compliance with Article 33.
It prescribes no form, no system and no template. Nor does it set a retention period. That latitude is sometimes read as leniency on the part of the Regulation. The opposite is true — it is the controller who answers for whether the chosen form can carry the evidential function.
The second sentence settles the matter. Verification covers the whole article, so it reaches paragraph 1 and the ground for not notifying as well. That ground rests on a finding that the breach is unlikely to result in a risk to the rights and freedoms of natural persons. It is precisely that conclusion which is reviewed.
Remember
An entry without the reasoning behind the decision gives the authority no material to verify and the controller no basis on which to defend itself.
Which events belong in the documentation
The scope is wider than the practice of most organisations suggests. It falls into three circles.
The first circle is breaches the controller has become aware of and notified to the authority. The second is breaches the controller has become aware of and not notified — the documentation obligation covers them in the same way, because the Regulation speaks of any breach. The third circle goes beyond the letter of Article 33(5). The President of UODO recommends documenting also those security incidents which the controller has classified as events that are not personal data breaches. The recommendation covers the reasons for that decision in particular.
That recommendation rests on the accountability principle in Article 5(2) GDPR, not on a separate obligation. It carries practical weight nonetheless. Without it, the organisation cannot show that it considered an event the authority knows about from another source.
What a single entry has to contain
The elements of an entry combine the requirements of the Regulation with the scope indicated in the guidance of the President of UODO. How detailed the record needs to be depends on what a given element is for.
| Element of the entry | Where the requirement comes from | What it is for |
|---|---|---|
| The facts — date and time of occurrence, of becoming aware and of closure; how it was detected; type, cause and course of the breach | Article 33(5) GDPR, UODO guidance | Establishing the moment of becoming aware, from which the notification deadline runs |
| Type and scope of the data, number and categories of data subjects | Article 33(5) GDPR, UODO guidance | The basis for assessing the severity of the potential impact |
| The effects and the possible effects for data subjects | Article 33(5) GDPR, UODO guidance | Telling an effect that materialised from one that is merely possible |
| The reasoning behind the risk assessment | UODO guidance, the accountability principle | The basis for checking the decisions on notification and communication |
| Remedial and preventive action | Article 33(5) GDPR, UODO guidance | Showing the response and its effect on the risk of recurrence |
| Date of notification, any reasons for delay and other relevant information in the notification or the reasons for the decision not to notify | Article 33(1), UODO guidance | Verifying the notification deadline or the ground for not notifying |
| Date, content and method of the communication and the number of data subjects reached or the reasons for the decision not to communicate | Article 34(1) and (3), UODO guidance | Showing the absence of a high risk or an exception under Article 34(3) |
Three elements separate useful documentation from a list of events. They are the reasoning behind the risk assessment and behind the decisions on notification and on communication to data subjects. The other elements describe what happened. The reasoning shows why the organisation acted as it did.
The reasoning behind a risk assessment is worth recording as reasoning, not as a result. The entry “risk low” says nothing about what the controller took into account. What can be checked is a record setting out the categories of data, the safeguards applied and the likelihood of harm that follows from them. Where the authority assesses the case differently, such a record shows what the controller based its decision on.
A justification for a misaddressed message might read as follows.
The breach covered the first name, surname and e-mail address of [number] data subjects. The data reached a single known external recipient as a result of an addressing error. The recipient confirmed deletion of the message; the confirmation has been retained in the case file. No identifiers enabling impersonation and no special categories of personal data were involved. The likelihood of further dissemination was assessed as low — there is one recipient, deletion has been confirmed and the recipient’s reliability is supported by [ongoing cooperation and known security procedures]. The severity of the potential impact is limited by the scope of the data, which is contact data.
That record can be checked. It sets out the scope of the data, the circumstance that limits the risk and the conclusion which follows from them. The formula “low risk, case closed” contains none of those three elements.
How the documentation changes over time
An entry is not closed once and for all. Information about a breach arrives in stages, and each new piece may change the risk assessment and the soundness of the earlier decision. The documentation is meant to mirror that and to keep a trace of the change, not only the final state.
This has a direct procedural consequence. A breach assessed at first as not requiring notification may require it once the full scope of the data is established. If 72 hours have already passed since the controller became aware of the breach, the notification must be accompanied by reasons for the delay (Article 33(1) GDPR). Those reasons then rest on documentation showing when the controller learned of the new circumstance.
How long to keep it and what not to put in it
The GDPR gives no period after which information about breaches may be erased. The President of UODO therefore recommends keeping it for as long as possible. A second, less obvious recommendation follows from the first. An internal register is neither required nor recommended to contain personal data — neither of the people affected by the breach nor of those involved in handling the case.
This is the position broken most often in practice. Registers kept in spreadsheets usually contain the names of the people affected and of the authors of the entries. The result is a set of data kept indefinitely, for which a separate legal basis and retention period have to be established. The answer is to separate the layers. The register works with a case identifier and aggregated data, while material containing personal data sits in the case file with its own retention period.
Where personal data does end up in the record after all, the ordinary processing principles apply to it, including minimisation and storage limitation.
Who keeps the documentation where processing is entrusted
The obligation under Article 33(5) GDPR is addressed to the controller. The processor notifies the controller of a breach without undue delay after becoming aware of it. The data processing agreement or other legal act must provide that the processor assists the controller in meeting the obligations under Articles 32 to 36, documentation included. That assistance takes into account the nature of processing and the information available to the processor (Article 28(3)(f) GDPR).
The practical conclusion concerns the content of the data processing agreement. The controller documents the facts of an event that took place in someone else’s infrastructure. It therefore needs a contractual route to data on the time of detection, the scope and the course of events. A data processing agreement providing for notification alone, with no scope for the information to be passed on, leaves the controller with an entry it cannot justify.
Common mistakes
- A register covering notified breaches only. The obligation covers any breach. Entries on cases that were not notified call for the fullest reasoning. Notified cases are subject to verification too, for example as to the deadline and the decision on communication to data subjects.
- A risk assessment recorded as a result. “Low risk” is not a justification. What can be verified is the line of reasoning, not its conclusion.
- Confusing breach documentation with the record of processing activities. These are two separate obligations with different subject matter — Article 30 describes processing, Article 33(5) describes events and decisions. The EDPB allows breaches to be documented in the record of processing activities, provided the information on them is clearly identifiable and can be extracted upon request (Guidelines 9/2022, paragraph 122, footnote 47).
- Keeping personal data in the register indefinitely. The recommendation to keep things for a long time concerns information about breaches, not data about people. Those two layers have to be separated when the record is designed.
- No trace of events classified as non-breaches. A decision that an event is not a personal data breach calls for a record together with its reason.
- An entry closed after the first assessment. The documentation is meant to be updated. New information may change the risk assessment and require a notification after 72 hours have passed since becoming aware of the breach. Such a notification must be accompanied by reasons for the delay.
Conclusions and next steps
Breach documentation is evidence of a decision-making process, not a record of events. That single premise settles what it contains. An entry has to reconstruct what the organisation knew at a given moment and what conclusion it drew from that. Cases notified to the authority already have part of their justification in the notification. Their entry should still give the date of notification, any reasons for delay and the decision on communication to data subjects.
An order of work that proves itself where a register already exists.
- Check whether the record holds entries on breaches that were not notified. If there are none, either no such breaches occurred or the register has a gap.
- Review the entries for the reasoning behind the risk assessment and complete those that give the result alone.
- Separate the register layer from the case file and remove from the register any personal data that is not needed there.
- Establish where information about breaches at processors comes from and whether the contracts secure it.
- Introduce a rule of updating the entry as information arrives, keeping a trace of the changes.
Documentation in good order also yields material available from no other source, namely the recurrence of mistakes of the same type. That is the right starting point for designing training matched to roles and processes. It points to the processes in which events actually arise.
Related materials
- Does every data breach need to be reported? — the notification threshold and the risk assessment whose outcome the register preserves.
- What to do after detecting an incident? — the sequence of actions that produces the entry.
- Cybersecurity incident vs personal data breach: what is the difference? — classifying the event before the entry is made.
- How do you notify data subjects of a breach and what must the communication contain? — what to record about the communication to data subjects or about the reasons for not sending it.
- How and when must a processor notify a personal data breach to the controller? — where and when the controller receives information about breaches at its processors.
Sources
- Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR), Article 5(2), Article 24(1), Article 28(3)(f), Article 30, Article 33 and Article 34, consolidated text — EUR-Lex: eur-lex.europa.eu
- Act of 12 July 2024 – Electronic Communications Law, Article 405(1), consolidated text (as at 7 July 2026) — Chancellery of the Sejm, ISAP: isap.sejm.gov.pl (in Polish)
- President of the Personal Data Protection Office (UODO), “Guide on personal data breaches”, version of 20 February 2025, chapter 8 — uodo.gov.pl (in Polish)
- European Data Protection Board, Guidelines 9/2022 on personal data breach notification under GDPR, version 2.0 adopted on 28 March 2023, paragraph 122 — edpb.europa.eu
- European Data Protection Board, Guidelines 01/2021 on examples regarding personal data breach notification, version 2.0 adopted on 14 December 2021 — edpb.europa.eu
Check whether your register will defend your decisions
The worth of a register shows only when a decision taken a year ago has to be explained. Putting the assessment of incidents and breaches in order covers a review of the existing entries and settles the scope the organisation is actually able to demonstrate.
This material is general and educational in nature. It is not an individual legal opinion or a recommendation for any specific organisation. The scope of the obligations should be assessed against the situation of the organisation concerned.
Legal status: November 2026.