Articles / Privacy Law

  • uk-law
  • uk-gdpr
  • data-protection-act-2018
  • data-breach
  • ico
  • privacy

Is a Misdirected Email a Personal Data Breach? Yes, Probably

Most people hear "data breach" and picture an attacker exfiltrating a database. The legal definition is much wider, and it catches things nobody would call a hack: an email sent to the wrong person, a laptop left on a train, a ransomware infection that never copied anything. If you run systems that hold personal data, it pays to know where the line actually sits.

The definition is about security, not attackers

Article 4(12) of the UK GDPR defines a personal data breach as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. The data can be transmitted, stored or otherwise processed. That is legislation, not guidance, and you can read it on legislation.gov.uk.

Read it as a list of outcomes. Nothing in it requires malice, or even a person acting on purpose:

  • destruction: the data no longer exists (a wiped disk with no backup)
  • loss: you no longer have it, or cannot find it
  • alteration: it was changed without authority
  • unauthorised disclosure: someone who should not have it got it
  • unauthorised access: someone could read it, whether or not they copied it

The ICO groups these as confidentiality, integrity and availability breaches. That is the old security triad, applied to personal data. It is guidance rather than law, but it is a sensible way to sort incidents.

Availability counts, which surprises people

A ransomware attack that encrypts your customer records is a breach even if the attacker never exfiltrated a byte. You have lost access to the data, and that is "loss" in the Article 4(12) sense. The ICO's guidance goes further and says a temporary loss of availability can qualify, depending on the effect on people. A short planned outage does not; a hospital system down for days probably does.

Quick detour, because this bit is genuinely odd: the definition says "breach of security", so a plain mistake in your own business logic is not automatically one. Sending the wrong customer's invoice to another customer is a breach, because it is an unauthorised disclosure. Charging someone the wrong amount is a data accuracy problem, not a security one. Same data, different regime.

Everyday examples that count

  • an email with a customer list attached, sent to the wrong recipient
  • an unencrypted laptop or USB stick lost or stolen
  • a misconfigured storage bucket left open, even if no one is shown to have looked
  • a developer pasting production rows into a public issue tracker
  • an employee reading records they have no work reason to see
  • the only copy of a dataset deleted by a failed migration

The open bucket is the awkward one. "Unauthorised access" covers the possibility of access as well as proven access, and logs that cannot show who looked make the assessment harder, not easier.

Being a breach is not the same as having to report it

Every incident that meets the definition must be recorded. Article 33(5) requires you to document the facts, the effects and what you did, whether or not you tell anyone. The ICO can ask to see that record. A tidy internal log of "near misses" and minor breaches is not paperwork for its own sake; it is how you show you made a considered decision.

Reporting to the ICO is a separate test. Under Article 33(1) you notify unless the breach is unlikely to result in a risk to people's rights and freedoms. A lost encrypted laptop with a safely held key probably clears that bar. A misdirected spreadsheet of names and health details probably does not.

Telling the individuals themselves (Article 34) has a higher threshold: a likely high risk. So the ladder is:

  1. Is it a breach under Article 4(12)? If yes, record it.
  2. Is it unlikely to risk people? If not, tell the ICO.
  3. Is the risk likely to be high? If so, tell the people affected as well, without undue delay.

When the 72 hours starts

The ICO must be told without undue delay and, where feasible, within 72 hours of you becoming aware of the breach. The clock runs through weekends. The ICO's position is that you are "aware" when you have a reasonable degree of certainty that a security incident has compromised personal data. That is not the moment someone first notices something odd, and it is not licence to sit on an alert while you "investigate".

If you cannot supply everything in time, Article 33(4) allows information to be provided in phases. Report what you know and follow up. Processors have their own duty under Article 33(2) to tell the controller without undue delay, which means your supplier's contract needs a realistic notification window.

Where the DPA 2018 and PECR fit in

The Data Protection Act 2018 does not replace this. Part 3 covers law enforcement processing by competent authorities and has its own breach rules: a definition in section 33 and notification duties in sections 67 and 68, again with a 72-hour window for the Commissioner. Most readers will never touch Part 3, but if you build systems for police or similar bodies, it is the regime that applies, not the UK GDPR.

Separately, providers of public electronic communications services (telcos and ISPs, broadly) have a stricter rule under regulation 5A of PECR: notify the ICO within 24 hours of detection where feasible. Check whether that applies to you before assuming 72 hours is your deadline.

What failing to report can cost

Failing to notify when you should have is a breach of the Article 33 obligation itself, carrying the lower fine tier (up to £8.7 million or 2% of worldwide turnover). The underlying security failure, under Articles 5(1)(f) and 32, sits in the higher tier (up to £17.5 million or 4%). In practice the ICO weighs how you responded, which is why a prompt, honest report tends to help you.

Whether a particular incident is reportable depends on the data, the people and the safeguards in place, so treat the examples above as illustrations of the test, not verdicts. The ICO publishes a self-assessment tool and detailed guidance at ico.org.uk, and it is worth bookmarking before you need it at 4pm on a Friday.