Insights / Charity
Charity17 Nov 2026 · 5 min read

After the Beacon CRM incident: what to check about the supporter data your website collects

In August the Charity Commission issued guidance to charities affected by a cyber security incident at Beacon, the CRM many charities use for supporter records. Several charities filed serious incident reports. Three months on, the lesson for everyone else is about knowing where supporter data travels, starting with the website.

Volunteers in gloves packing food parcels into bags at a community food bank

The Charity Commission said it was aware of a cyber security incident involving Beacon's CRM service, was monitoring the situation and was working with the Information Commissioner's Office. It reminded trustees to report serious incidents that result in, or risk, significant harm, loss or damage to the charity, and to consider their duties to the ICO and to the people whose data was held on Beacon on the charity's behalf.

Your supplier's incident is still your incident

Many of the charities affected had done nothing wrong. Their data sat with a reputable supplier. But under data protection law the charity is still responsible for that data, and it is the charity's supporters who need to be told. That makes every system holding supporter data part of the trustees' risk, including the ones you rent.

Most supporter data starts on the website

Donation forms, event sign-ups, newsletter boxes, volunteer applications and Gift Aid declarations are usually where a supporter record begins. On many charity sites, each form was added at a different time by a different supplier. Data may pass through a form plugin, a payment provider and an integration tool before it reaches the CRM, and copies are often left at each step.

Map every form on your site
  • What it collects, and whether you need all of it
  • Every system it passes through on the way to the CRM, including plugins and integration tools
  • Whether copies stay in the website database or form plugin, and for how long
  • Who can log in to each of those systems, and whether they use multi-factor authentication
  • Which supplier you'd call first, and who would contact supporters, if any of them had an incident

If you can't draw where a donor's details go in five minutes, you can't tell the Commission or your supporters either.

Fewer copies, fewer risks

The safest supporter record is the one that exists in one place. When we rebuild a charity site or its integrations, forms post straight to the system of record, the website keeps only what it needs, and old copies are deleted on a schedule. It's less to secure, and much less to explain if something goes wrong.

If your website itself needs looking after while you review this, our sister company WebsiteSupport.io now offers free website support to registered charities with an income over £1 million, with hosting the only cost.

This summarises the Charity Commission's published guidance of 7 August 2026 and is not legal advice. For your own reporting duties, see the Commission's serious incident reporting guidance and the ICO's guidance for organisations.