Reporting a personal data breach to the ICO: when you must and how
Report a personal data breach to the ICO within 72 hours of finding it, but only when it is likely to put people at risk. Every breach goes in your own log, reported or not, and when the risk to people is high you must tell them as well, without undue delay.

UK: the duty comes from the UK GDPR and is enforced by the ICO.
If you find a personal data breach, start a written log straight away and work out whether it is likely to put anyone at risk. If it is, the ICO must hear about it without undue delay and within 72 hours of you discovering it. If it isn't, you don't report it, but you still record what happened and why you decided not to. The ICO says plainly that not every breach reported to it leads to formal action, and that its main aim is to help organisations stop it happening again.
The ICO notes that its breach guidance is under review after the Data (Use and Access) Act 2025, so check its pages if you are reading this some months on. The duties below are the ones its guidance sets out today.
What counts as a breach
The ICO's guide to personal data breaches defines one as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. Accidents count as much as attacks. Its examples include:
- an email or letter with personal data sent to the wrong person;
- a laptop or phone holding personal data lost or stolen;
- someone getting into data they shouldn't, from outside or inside the business;
- personal data changed without permission;
- personal data becoming unavailable, for example files lost in a flood.
That last one surprises people. A breach is about confidentiality, integrity or availability, so data you can no longer reach can be a breach even if nobody else has seen it, where losing access has a significant negative effect on the people concerned.
It has to be personal data, meaning anything that could identify a person: names and addresses, photographs, comments people made, records about them. The ICO's guidance on assessing risk gives an example. A bulk email that shows every recipient's address might be a personal data breach if your customers' private addresses were visible, but if only the business addresses of limited companies were showing, it may not be one, because business information is not personal information.
When the 72 hours start
The clock starts when you discover the breach, not when it happened. The ICO's 72-hour guide for small organisations is explicit on that. A phishing email opened three weeks ago that you only find today gives you 72 hours from today.
You will rarely know everything within three days, and the law allows for that. The ICO says you can give the information in phases, as long as each part follows without undue further delay. Its advice is to report early and update later: tell it what you know, say what you are still investigating and when you expect to know more. If you do report after 72 hours, you must give your reasons for the delay.
Deciding whether to report
This is the judgement the whole process turns on. The ICO's breach reporting page says you must assess the likely risk to people's rights and freedoms, and notify the ICO if a risk is likely. Its guide adds the other half: if a risk is unlikely, you don't have to report it, but you need to be able to justify that decision.
The risk is to the people whose data it is, not to the business. The ICO suggests putting yourself in their shoes, and its risk guidance lists questions to ask:
- What personal data is involved? Financial details that could lead to identity fraud, or sensitive information about vulnerable people, are likely to be high risk.
- Who might have it now? An email sent to the wrong department inside the business is lower risk than the same email sent to an unknown person outside it.
- How many people are affected?
- Are they children or vulnerable adults, could the breach put anyone in an unsafe situation, and could anyone lose money, a job or a home?
The ICO's own examples show where the line falls. A hair appointment reminder emailed to the wrong customer, who has deleted it, is unlikely to need reporting. Losing or wrongly changing a staff telephone list would not normally need reporting either. The theft of a customer database that could be used for identity fraud would need to be reported. In one of its case studies, a sensitive file emailed to a colleague in another department, who deleted it at once and told the sender, needed only an entry in the internal log. In another, a lost briefcase looked low risk until it turned out the laptop in it was not encrypted and the paper files with it had not been redacted, and then it had to be reported to the ICO and to the people affected. The internal log is what let that business explain why its report came after 72 hours.
If you are unsure, the ICO has a self-assessment that it says takes about five minutes, and a personal data breach advice line on 0303 123 1113.
The first three days, step by step
The ICO's guide for small organisations sets out an order. In short:
- Start the log. Write down what happened, who is involved and what you are doing about it, even if you may not need to report. The ICO publishes a template log you can use.
- Pull the facts together. What happened and why, how many people are involved, a timeline, and what you have done so far.
- Contain it. Recover the data if you can. If it went to the wrong person, ask them to delete it, send it back securely or keep it for you to collect. If a laptop was stolen and you have the systems set up to do it, wipe it remotely. For a cyber incident, the ICO suggests changing passwords and having staff do the same.
- Assess the risk, as in the section above.
- Protect the people affected, if the risk calls for it (below).
- Report it, if it is reportable.
Keep adding to the log as you go. If what you learn changes the risk, as it did with the lost briefcase, the log shows when you found out and why your decision changed.
Telling the people affected
The bar for telling people is higher than for telling the ICO. If a breach is likely to result in a high risk to them, you must tell them directly and without undue delay. If the risk is not high, you don't have to, though nothing stops you. The ICO warns that telling people about minor breaches can cause needless worry. It can also make you tell people if it considers the risk high.
When you do tell them, the ICO's guide says to describe the breach in clear, plain language and include at least:
- a contact point, such as your data protection officer if you have one, where they can get more information;
- the likely consequences of the breach;
- what you have done or will do about it, and how you are limiting any harm.
Give them practical advice too. Depending on what was exposed, the ICO suggests forcing a password reset, telling them to use strong, unique passwords and asking them to watch for phishing emails or fraudulent activity on their accounts.
Sending the report
You report online. The ICO says the form takes about 30 minutes and cannot be saved and finished later, so have your log open before you start. It will ask:
- what has happened;
- when and how you found out;
- who has been or may be affected;
- what you are doing as a result;
- who it should contact for more information, and who else you have told.
The ICO sends you a copy of what you submitted. It uses the report to decide what happens next, to understand the cause and the controls you had in place, and, depending on the impact, it may use its investigation or enforcement powers. It may also share what you send with law enforcement or other regulators, such as the Financial Conduct Authority.
Who else to tell
Reporting to the ICO doesn't cover anyone else. Its reporting page says it is your responsibility to notify all the organisations that need to know, and suggests considering:
- your insurer;
- law enforcement, including Report Fraud, the UK's national fraud and cybercrime reporting centre, if you think there was criminal intent (in Scotland, the ICO says to report to Police Scotland instead);
- the NCSC, if the breach was caused by an attacker.
If the breach happened at a supplier that handles personal data for you, such as an IT provider storing your customer records, the ICO's guide says it must tell you without undue delay once it knows. The decision to report to the ICO is then yours. Your contract with that supplier should set out how it will tell you about breaches.
Keep the record either way
The UK GDPR requires you to record every personal data breach, reported or not: the facts, the effects and what you did about it. If you decide a breach doesn't need reporting, write down why. The ICO says that is how you justify the decision if it ever asks.
The stakes are real. The ICO's guide says that failing to report a breach when you were required to can lead to a fine of up to £8.7 million or 2 per cent of global turnover.
The ICO also suggests looking back at every breach for lessons: whether it came from one person's mistake or from the way things are done, and whether training, a "check twice, send once" habit or tighter access to systems would stop a repeat. For a small firm, the controls in Cyber Essentials are a sensible place to start on the security side.
Common questions
- Do we have to report an email sent to the wrong person?
- Only if it is likely to put someone at risk. The ICO's examples show that a routine message to the wrong customer, since deleted, usually needs only an entry in your own log, while sensitive or financial details sent to someone outside the business are more likely to need reporting. Record your reasoning either way.
- What if we miss the 72 hours?
- Report anyway, as soon as you can, and give your reasons for the delay. The ICO's guide says a late report must explain why. A log written as events happened is the best evidence of when you found out and what you did.
- Our IT provider had the breach, not us. Who reports it?
- If the provider handles personal data on your behalf, it must tell you without undue delay, and you then decide whether the breach is reportable and report it to the ICO if so.
Sources
Every requirement, price and figure in this guide comes from these pages, read on 21 November 2026. Schemes, prices and products change: check the source before you rely on one.
- UK GDPR data breach reporting (DPA 2018) (ICO)
- Personal data breaches: a guide (ICO)
- 72 hours - how to respond to a personal data breach (ICO)
- Understanding and assessing risk in personal data breaches (ICO)
- Personal data breach examples (ICO)
- Self-assessment for data breaches (ICO)
Spotted something wrong or out of date? Tell us and we will correct it.
Keep reading
More small business guides
All small business guides
Security and Cyber EssentialsCyber Essentials explained: what it covers, what it costs and how to get certified
19 Nov 2026 8 minRead
Phone systemsThe analogue phone switch-off: what a small business needs to check before January 2027
21 Nov 2026 6 min