Artifact GuideUK72-hour Breach Reporting

UK GDPR 72-Hour Breach Reporting

A must notify the ICO without undue delay and, where feasible, within 72 hours after becoming aware of a unless it is unlikely to create a risk to people's rights and freedoms.

The must separately decide whether a likely high risk means affected people must be told without undue delay. Every must be documented, including those not reported.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

Start the incident record as soon as a possible is escalated. Confirm when the became aware, assess the likely risk to people, notify the ICO if the Article 33 threshold is met, and do not wait for a complete investigation if a phased report is needed. Security incidents that do not affect personal data are outside Articles 33 and 34, but they may trigger other legal, contractual, or sector duties.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

When must a controller report a breach to the ICO?

A is a security breach leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data. It covers confidentiality, integrity, and availability failures, not only theft or disclosure.

The must notify the ICO unless the breach is unlikely to result in a risk to people's rights and freedoms. If notification is required, it must be made without undue delay and, where feasible, within 72 hours after the controller becomes aware. A must notify its controller without undue delay after becoming aware; Article 33 does not give processors their own 72-hour ICO deadline, although the contract may set a shorter escalation period.

  • Record the 's time and the facts that made the breach reasonably certain.
  • Assess the type of harm, affected people, sensitivity and volume of data, ease of identification, likely consequences, and measures already protecting the data.
  • Notify the ICO unless the breach is unlikely to result in risk to people's rights and freedoms; retain the reasoning for a decision not to notify.
  • Do not confuse the lower ICO-notification risk threshold with the high-risk threshold for telling affected people.
Question 2

What must the ICO report and incident record contain?

The Article 33 report must describe the nature of the breach, including, where possible, the categories and approximate numbers of affected people and personal-data records; give the data protection officer's or other contact's details; describe likely consequences; and describe measures taken or proposed to address the breach and mitigate harm.

If all information is not available at once, provide it in phases without undue further delay. A report made after 72 hours must include reasons for the delay. Keep the submission, receipt, later updates, and decision trail with the incident record.

  • Timeline: discovery, escalation, , containment, risk decisions, ICO report, updates, and individual communications.
  • Scope: systems, data categories, affected people and records, jurisdictions, processors, and recipients.
  • Assessment: likely consequences, likelihood and severity of harm, protective measures, residual risk, and decision-maker.
  • Response: containment, recovery, credential resets, communications, further investigation, lessons learned, and control changes.
Question 3

When must affected people be told?

Article 34 requires the to communicate the breach to affected people without undue delay when it is likely to result in a high risk to their rights and freedoms. The communication must use clear, plain language and include the contact point, likely consequences, and measures taken or proposed, including mitigation.

Direct communication is not required if appropriate measures made the data unintelligible to unauthorised people, later measures ensure the high risk is no longer likely to materialise, or direct contact would involve disproportionate effort. In the last case, the must use a public communication or similarly effective measure. These exceptions must be assessed against the actual breach; encryption helps only if the keys and implementation remained secure.

  • Tell people what happened and what information was affected.
  • Explain the likely effects without speculation or minimising the risk.
  • State what the organisation has done and what the person can do to protect themselves.
  • Keep the high-risk assessment and any Article 34 exception rationale with the breach record.
Question 4

Questions and answers

Does the 72-hour clock wait for a completed investigation?

No. If the breach is notifiable, report without undue delay and, where feasible, within 72 hours after . Article 33 allows information to be supplied in phases when it cannot be provided at the same time. Explain any delay beyond 72 hours and provide missing information without undue further delay.

Must we record a breach that is not reported?

Yes. Article 33(5) requires the to document every , the facts, effects, and remedial action. The record should also show why the breach was unlikely to result in risk when the controller decided not to notify the ICO.

Does a have 72 hours to tell the ?

Article 33 requires a to notify the without undue delay after becoming aware of a . It does not give the processor a separate 72-hour period. The controller's 72-hour clock and the contract's incident-notice terms make prompt processor escalation essential.

Primary sources

References and citations

ico.org.uk3 citations
Referenced sections
  • Current ICO operational guidance for recognising, assessing, reporting, communicating, and documenting personal data breaches.
  • Explains breach recognition, awareness, risk assessment, controller and processor roles, ICO reporting, individual communication, and documentation.
  • Explains the separate tests for ICO notification and communication to affected people.
legislation.gov.uk2 citations
Referenced sections
  • Binding source for the controller's risk threshold and 72-hour duty, the processor's notice duty, phased reporting, required report content, and breach records.
  • Specifies the minimum notification content, phased provision of information, reasons for delay, and the duty to document every breach and remedial action.
ico.org.uk
Referenced sections
  • Provides the current ICO reporting route and operational information organisations need before submitting a report.
legislation.gov.uk
Referenced sections
  • Binding UK GDPR text for supervisory-authority notification, processor escalation, records, and communication to affected people.
Show all related guides (40)

UK GDPR DPIA: When It Is Required and What to Record

Screen for likely high-risk processing, complete the Article 35 assessment before processing, and consult the ICO if high residual risk remains.

UK GDPR DPO: When Appointment Is Mandatory

Apply the three UK GDPR DPO triggers and document expertise, independence, reporting line, resources, tasks, contacts, and conflict controls.

UK IDTA, Addendum, and Transfer Risk Assessment Guide

Decide when to use the UK IDTA or Addendum, complete the Article 46 data protection test, add supplementary measures, and keep the transfer under review.

When do PECR cookie rules require consent?

Apply the current UK PECR rules to cookies and similar technologies, including consent, five exceptions, UK GDPR overlap, and evidence.

UK GDPR 72-hour Breach Reporting Guide

Decide whether a UK personal data breach must be reported to the ICO, when the 72-hour clock starts, what the report must contain, and when individuals must be told.

UK GDPR Adequacy Guide

Use UK transfer approval regulations by checking the destination, recipient, data, sector, effective status, scope limits, and review evidence.

UK GDPR AI and Automated Decisions Guide

Current UK GDPR rules for significant solely automated decisions, meaningful human involvement, Article 22B restrictions, and Article 22C safeguards.

UK GDPR Applicability Test Guide

Apply the UK GDPR material and territorial scope tests to one processing activity, including exclusions, non-UK organisations, roles, and evidence.

UK GDPR Article 30 Records Guide

Build UK GDPR Article 30 records for controller and processor activities, apply the narrow under-250 exception, and keep the records current and available to the ICO.

UK GDPR Breach Notification Guide

Decide whether a personal data breach must be reported to the ICO or communicated to individuals, with deadlines, exceptions, content, and evidence.

UK GDPR Breach Workflow Guide

Run a UK GDPR personal data breach workflow from containment and awareness through risk assessment, ICO reporting, individual notice, and the breach record.

UK GDPR Children and Age Appropriate Design Guide

Apply UK GDPR children's protections and the Age Appropriate Design Code to online services likely to be accessed by children.

UK GDPR Children's Code Guide

A practical guide to Children's Code scope, its 15 standards, age 13 consent, evidence, exceptions, and product implementation.

UK GDPR Compliance Checklist

A verifiable UK GDPR checklist for scope, lawful processing, transparency, rights, governance, security, breaches, DPIAs, children, and transfers.

UK GDPR Compliance FAQ: Duties, Rights, and Decisions

Answer common UK GDPR questions on scope, lawful basis, records, DPIAs, DPOs, rights, breaches, children, automated decisions, and international transfers.

UK GDPR Compliance Guide

Build a UK GDPR compliance programme around processing records, lawful decisions, rights operations, security, incidents, DPIAs, suppliers, and transfers.

UK GDPR Controller and Processor Status Guide

Decide whether each party is a controller, joint controller, or processor under the UK GDPR, then record the role-specific duties, contract terms, and evidence.

UK GDPR Data Subject Rights Guide

Operate UK GDPR access, rectification, erasure, restriction, portability, objection, and automated-decision rights under the amended Article 12 timing rules.

UK GDPR Deadlines and Compliance Calendar Guide

Track UK GDPR deadlines for rights requests, privacy information, breach notification, DPIAs, and ICO prior consultation, with triggers and exceptions.

UK GDPR DPIA Workflow Guide

Screen UK GDPR processing for likely high risk, complete the required DPIA analysis before processing, reduce risk, and consult the ICO when high residual risk remains.

UK GDPR DPIAs and DPOs Guide

Decide when the UK GDPR requires a DPIA or DPO, what each must cover, when to consult the ICO, and what evidence to retain.

UK GDPR DSAR Workflow Guide

Run a UK subject-access workflow using the current Article 12A clock, reasonable identity and clarification steps, proportionate searches, exemptions, redactions, and response evidence.

UK GDPR IDTA Addendum and Transfer Risk Assessment Guide

Choose the UK IDTA or Addendum, complete the current Article 46 data protection test, add needed measures, and maintain evidence for restricted transfers.

UK GDPR Lawful Bases Guide

Choose among the six familiar Article 6 bases and the UK's recognised legitimate interests basis, then document any Article 9 or 10 condition.

UK GDPR PECR Cookies Guide

UK GDPR and PECR cookie guidance with practical consent, exemption, evidence, and cited implementation decisions.

UK GDPR Penalties and Fines: Maximums and ICO Factors

Understand the UK GDPR £8.7 million or 2% and £17.5 million or 4% fine ceilings, which infringements fall into each band, and how the ICO sets a fine.

UK GDPR Requirements Guide

Map UK GDPR requirements by processing activity, role, lawful basis, data type, risk, rights, suppliers, automated decisions, and transfers.

UK GDPR Transfer Workflow Guide

Apply the UK GDPR restricted-transfer sequence: map the transfer, check Article 45A approval, choose an Article 46 safeguard and assessment, or justify a specific Article 49 derogation.

UK GDPR Transfers, IDTA, and UK Addendum Guide

Decide whether a UK restricted transfer exists, whether adequacy applies, how to use the IDTA or UK Addendum, and how to document the data protection test.

UK GDPR vs Data Protection Act 2018: How They Work Together

See when to use the UK GDPR, when the Data Protection Act 2018 adds a condition or exemption, and which regime covers law enforcement or intelligence processing.

UK GDPR vs EU GDPR: Scope, Regulators and Transfers

Determine whether UK GDPR, EU GDPR, or both apply, then separate representatives, regulators, transfer routes, national law, and post-Brexit UK amendments.

UK IDTA vs EU SCCs: Which Transfer Contract to Use

Choose between the UK IDTA and EU SCCs with the UK Addendum, complete the right documents, and record the separate UK and EU transfer assessments.

UK vs EU GDPR Differences After the 2025 UK Reforms

Compare current UK and EU rules for recognised legitimate interests, rights requests, access searches, automated decisions, and international transfers.

UK vs EU GDPR Operations: Regulators, Breaches and Transfers

Configure separate UK and EU privacy operations for representatives, regulator contacts, rights requests, breach reporting, transfer tools, and evidence.