Key takeaways
- Report a personal data breach to the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people[1].
- Tell the people affected without undue delay when the breach is likely to result in a high risk to them[2].
- Document every breach, reported or not: the facts, the effects and what you did[1].
- 30% of food or hospitality businesses identified a cyber breach or attack in the past year[3], and many more breaches are simple human mistakes.
What counts as a personal data breach
A personal data breach is any security incident that leads to personal data being lost, destroyed, changed, disclosed or accessed without authority, whether by accident or on purpose. It is not only hacking. In a restaurant, the most common breaches are ordinary mistakes made on a busy day.
- A booking list or private dining guest list emailed to the wrong customer.
- A marketing email sent with every recipient's address visible in the To field.
- A manager's laptop or phone with access to the booking system left on a train.
- A staff member's login to the booking or EPOS back office used by someone else after a phishing email.
- A paper reservations book or accident book left on the bar overnight and taken.
- CCTV stills of a guest shared in a staff WhatsApp group or on social media.
- Payroll details sent to a fraudster pretending to be an employee asking to change their bank account.
- A supplier, such as your booking platform, telling you its systems have been compromised.
How common breaches are
In the government's 2025 Cyber Security Breaches Survey, 30% of food or hospitality businesses identified a cyber breach or attack in the previous 12 months, compared with 43% of businesses overall[3]. A lower figure is not necessarily good news. Only 12% of food or hospitality businesses had a board member responsible for cyber security, among the lowest of any sector[4], and only 25% had sought external cyber security guidance, against 42% of businesses overall[5]. Businesses that look less often tend to find less.
Source: Department for Science, Innovation and Technology, 2025[3]
Show the data
| Item | Value |
|---|---|
| Food or hospitality businesses | 30% |
| All businesses | 43% |
Most breaches at venues will never make the news, but each one can hurt a guest or an employee, and each one has to be handled properly. A plan written in advance turns a panicked evening into a checklist.
The first hour
Contain it
Recall the email if your system allows, ask the wrong recipient to delete it and confirm in writing, change passwords, sign out of all sessions, or disable the compromised account.
Preserve evidence
Do not delete emails, logs or messages about the incident. Take screenshots of what happened and when.
Tell the right person
Every manager should know who owns breaches, usually the owner or general manager, and how to reach them out of hours.
Start the record
Write down when you found out, what data and how many people are involved, and what you have done so far. The 72-hour clock starts from when you became aware.
Call in help if needed
Your IT provider, booking platform or EPOS supplier for technical incidents; your bank immediately if money or payment data is involved.
Do you need to report it?
You must notify the regulator without undue delay and, where feasible, not later than 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms. If you report after 72 hours, you must give reasons for the delay[1]. You can report in stages if you do not yet have all the facts. Your booking platform, EPOS supplier or other processors must tell you without undue delay after they become aware of a breach affecting your data[1].
| Scenario | Likely risk | Report to the regulator? | Tell those affected? |
|---|---|---|---|
| Booking confirmation sent to the wrong guest, name and time only, deleted on request | Low | Usually not; record it | Usually not |
| Private dining list with names, phone numbers and dietary needs sent to another customer | Medium to high: health data | Likely yes | Likely yes |
| Marketing email with all addresses visible to every recipient | Medium | Often yes, depending on the list size and content | Consider an apology and explanation |
| Booking system account taken over after phishing, guest data exported | High | Yes | Yes |
| Payroll file with bank details and National Insurance numbers lost | High | Yes | Yes, with advice on fraud |
| Encrypted laptop lost, strong password, no sign of access | Low | Usually not; record it | Usually not |
What a report needs to say
A report to the regulator must at least describe the nature of the breach, including where possible the categories and approximate number of people and records involved; give the name and contact details of the person dealing with it; describe the likely consequences; and set out what you have done or plan to do, including steps to reduce any harm[1]. If you do not have everything within 72 hours, send what you have and follow up.
- Who was affected: guests, staff, or both, and roughly how many.
- What data: names and contact details, dietary or health notes, bank details, booking history, images.
- How it happened, in a sentence or two, without guessing at causes you have not confirmed.
- What you have done: containment, recovery, password resets, contact with the recipient.
- What happens next: who is contacting the people affected, and what you are changing.
Telling guests or staff
When a breach is likely to result in a high risk to people, you must tell them without undue delay, in clear and plain language, describing what happened, the likely consequences, what you have done and what they can do to protect themselves[2]. You do not have to tell them if the data was protected so that nobody unauthorised can read it, such as by encryption, if you have taken steps that mean the high risk is no longer likely, or if contacting everyone individually would involve disproportionate effort, in which case a public notice can be used instead[2].
Example message to guests: “On 12 May, a list of guests booked for a private party at The Granary was sent to the wrong email address in error. It included your name, phone number and any dietary requirements you gave us. The recipient has confirmed they deleted it. We are sorry. You do not need to do anything, but please be cautious of unexpected calls or messages mentioning your booking. If you have questions, contact our manager on the number below.”
Keep the message factual, apologise once, and avoid speculating. Make sure staff who answer the phone know what has been said, so guests who call get the same answer.
Keep a breach log
You must document every personal data breach, including the facts, its effects and the remedial action taken, whether or not you report it, so the regulator can check you have complied[1]. A spreadsheet with one row per incident is enough. Review it every few months: repeat incidents, such as misdirected emails, point to a fix, like turning on a delay before emails send or using blind copy for group messages.
Write the plan before you need it
A breach plan for a single venue fits on one page and should live somewhere every manager can find it at eleven at night. It does not need legal language. It needs names, phone numbers and the order of steps.
- Who owns breaches, with a deputy, and their out-of-hours contact details.
- Contacts for your booking platform, EPOS supplier, email provider, IT support and bank, including their security or fraud lines.
- The first-hour steps above, as a checklist.
- Where to find the breach log and the regulator's reporting route.
- A short template message for guests and one for staff, ready to adapt.
Walk through the plan with managers once a year using a made-up scenario, such as a guest list sent to the wrong address on a Saturday night. Ten minutes of practice is usually enough to show where the gaps are.
Preventing the common ones
- Use blind copy or your email platform for any message to more than one guest.
- Turn on two-factor authentication for booking, EPOS, email and payroll accounts, and remove leavers' access on their last day. Our guide to cyber security for small hospitality businesses covers the basics.
- Never change a supplier's or employee's bank details on the strength of an email alone; call back on a known number. See scams and phishing aimed at restaurants.
- Keep paper records with personal data out of public areas and lock them away at close.
- Agree a rule that CCTV images are never shared in chat groups or on social media.
- Limit who can export guest lists from the booking system.
After the incident
Once the immediate risk is handled, hold a short review. What happened, why, and what single change would stop it happening again? Update your process, your training and, if needed, your privacy notice. If someone affected asks what data you hold about them, treat it as a subject access request. Since 30 September 2026, reports go to the Information Commission, which took over from the ICO with the same role and powers.
Frequently asked questions
Is a misdirected email a data breach?
Yes, if it contains personal data and goes to someone who should not have it. Whether you need to report it depends on the risk: a booking time sent to the wrong guest is very different from a guest list with dietary needs.
Do we still need to report if we got the data back?
Quick recovery and deletion reduce the risk and may mean reporting is not required, but record the breach and your reasoning either way.
What if our booking platform has the breach?
The platform must tell you without undue delay. You remain responsible for deciding whether to report and whether to tell your guests, so ask the platform for the facts you need quickly.
Who do we report a breach to now the ICO has changed?
To the Information Commission, the UK's data protection regulator since 30 September 2026. It uses the same reporting routes and you may still see the ICO name.
References
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 33: Notification of a personal data breach (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 34: Communication of a personal data breach to the data subject (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑