Breach notices
Data breach and incident notification in the United Kingdom
Short answer
- UK GDPR deadline
- 72 hours after awareness, where feasible 1
- PECR deadline
- 72 hours where feasible, added on 20 August 2025 3
- NIS incidents
- No later than 72 hours after awareness 4
- Fine cap for notice failures
- £8,700,000 or 2% of worldwide turnover 2
- Regulator name in PECR
- Information Commission, substituted from 30 September 2026 3
Four separate reporting regimes
The ICO's reporting page lists four kinds of report 7. Each has its own legal basis and its own recipient group 7.
| Regime | Who reports | Deadline | Law |
|---|---|---|---|
| UK GDPR personal data breach | Controllers 1 | 72 hours where feasible 1 | UK GDPR Article 33 1 |
| Communications services breach | Providers of public electronic communications services 3 | 72 hours where feasible 3 | PECR regulation 5A 3 |
| Law enforcement processing | Competent authorities under Part 3 5 | 72 hours where feasible 5 | Data Protection Act 2018 section 67 5 |
| NIS incident | Operators of services designated under the Regulations, known as OES 4 | 72 hours 4 | NIS Regulations 2018 regulation 11 4 |
| Trust service breach | Trust service providers 7 | Not stated on the ICO page 7 | eIDAS rules 7 |
UK GDPR Article 33
A controller must notify a personal data breach without undue delay and, where feasible, not later than 72 hours after becoming aware of it 1. No notice is needed if the breach is unlikely to result in a risk to the rights and freedoms of natural persons 1. A notice made after 72 hours must give reasons for the delay 1.
Processors tell the controller without undue delay 1. Details may be sent in phases 1. Controllers must document every breach, its effects and the remedial action taken 1. The current text names the regulator as the Commission 1.
PECR: telecoms and internet providers
Regulation 5A of the Privacy and Electronic Communications Regulations 2003 was inserted on 26 May 2011 3. It requires a service provider to notify a personal data breach to the regulator without undue delay 3. The words where feasible, not later than 72 hours after having become aware of it were inserted on 20 August 2025 by the Data (Use and Access) Act 2025 3. A new paragraph 3A requires reasons for any delay past 72 hours 3.
If a breach is likely to adversely affect a subscriber's or user's personal data or privacy, the provider must notify that person without undue delay 3. That notice is not needed where the provider has shown the regulator that the data was made unintelligible by technological protection 3. Providers must keep an inventory of breaches with the facts, effects and remedial action 3.
NIS Regulations 2018
An OES, the term the Regulations use for a designated service operator, must notify its designated competent authority in writing of any incident with a significant impact on the continuity of the service it provides 4. The notice is due without undue delay and in any event no later than 72 hours after the operator is aware of the incident 4. Factors include the number of users affected, the duration and the geographical area 4.
The competent authority shares the information with the CSIRT and may inform the public where it considers public awareness necessary 4. Each competent authority sends an annual report on the number and nature of notified incidents 4.
Penalties
UK GDPR Article 83(4) sets fines up to £8,700,000, or 2% of total worldwide annual turnover for an undertaking, whichever is higher, for breaches of Articles 25 to 39 2. The notice duties in Articles 33 and 34 sit in that range 2. Section 157 of the Data Protection Act 2018 sets the higher maximum at £17,500,000 or 4% of turnover and the standard maximum at £8,700,000 or 2% 6. Failing to comply with an information notice, assessment notice or enforcement notice attracts the higher maximum 6.
Common questions
How long do UK organisations have to report a personal data breach?
Without undue delay and, where feasible, within 72 hours of becoming aware of it 1.
Did PECR breach reporting change in 2025?
Yes. A 72 hour limit and a duty to give reasons for delay were inserted into regulation 5A on 20 August 2025 3.
What is the maximum fine for failing to notify a breach in the UK?
Up to £8,700,000 or 2% of worldwide annual turnover, whichever is higher, under UK GDPR Article 83(4) 2.
Who receives NIS incident reports?
The operator's designated competent authority, which shares them with the CSIRT 4.
Where do UK organisations file a breach report?
Through the ICO's Report a breach page, which separates UK GDPR, PECR, eIDAS and NIS reports 7.
Rules and charges change. Check the official source linked on this page before you pay or travel. Spotted an error? Email hello@noticeofrecord.com.
Sources
- legislation.gov.uk: United Kingdom General Data Protection Regulation, Article 33
- legislation.gov.uk: United Kingdom General Data Protection Regulation, Article 83
- legislation.gov.uk: The Privacy and Electronic Communications (EC Directive) Regulations 2003, Regulation 5A
- legislation.gov.uk: The Network and Information Systems Regulations 2018, Regulation 11
- legislation.gov.uk: Data Protection Act 2018, section 67
- legislation.gov.uk: Data Protection Act 2018, section 157
- ICO: Report a breach
Related
- Data breach and incident notification in the European Union
EU breach and incident reporting rules side by side: GDPR 72 hours, NIS2 24 hours, telecoms 24 hours and DORA reports for financial firms.
- Data breach notification laws compared
How breach notice rules differ in the EU, UK, US, Australia, Canada and India: who must notify, the deadline and who receives the notice.
- How to check whether a notice was given
Where to look up official notices: state breach lists, the HHS breach portal, SEC EDGAR, FDA warning letters, FCA notices, WARN reports and recall lists.
- What a formal notice is
What makes a notice formal: who gives it, who receives it, the deadline and the form. Breach, recall, regulatory, layoff and court notices compared.