From the public record · UK · 2019–2023

A thousand breaches from one email field

The ICO reported nearly 1,000 data breaches since 2019 caused by bulk emails that exposed recipients. Education, health and local government were the most affected sectors.

An email window with a long list of addresses in the To field and an empty Bcc field. Four recipients each see every other recipient's address. The ICO reported nearly 1,000 such breaches.

What happened

On 30 August 2023 the Information Commissioner’s Office reported nearly 1,000 data breaches since 2019 caused by bulk emails where recipients could see each other’s addresses, usually because an address list went into the “To” or “CC” field instead of “BCC”. Education, health and local government were the three most affected sectors.

The ICO’s guidance was direct: blind carbon copy on its own is not enough to protect people’s information. It recommended bulk email services, mail merge or secure transfer instead.

The pattern

A task that is sensitive, repetitive and done by hand in a general-purpose tool will eventually go wrong, however careful the people doing it. The cause is not carelessness. It is a process where one wrong click is enough.

The ICO’s figures show the same mistake repeating across sectors and years. Training and reminders help, but they ask people to be perfect every time, under time pressure, in a tool that lets them type any address anywhere.

What a proportionate fix looks like

Diagram: a contact list and a message template written by staff feed a merge step that sends one separate email per recipient, each showing only that recipient's address.
Sending from the system that holds the list removes the address field from the process.

Group messages should be sent from the system that already holds the list, as one message per recipient, with no address field for anyone to fill in by hand. The people keep writing the message; the risky step disappears.

Where a team regularly emails service users, parents, patients or residents as a group, that is usually the first process worth looking at.

It also leaves a record of who was sent what and when, which helps if a complaint or a subject access request arrives later.

Questions worth asking

  • Which teams send the same kind of message to a group more than once a month?
  • Where does the list of recipients come from, and is it copied by hand into an email?
  • Would a mistake expose health, education, care or financial information?
  • Could the message be sent from the system that already holds the contact details?

Fairlead Systems was not involved in the events described here. The account above is drawn only from the sources listed, which were last checked on 1 October 2026. If you spot an error, write to us and we will correct it.

Insights

More from the public record

Recognise this pattern?

Tell us what the process looks like today. We will say whether it needs fixing, and how small the fix can be.