Key takeaways
- Map the personal data you hold once: bookings, orders, Wi-Fi, CCTV, marketing lists, staff records and supplier contacts.
- Allergy and dietary notes are data concerning health, which UK GDPR treats as special category data with extra conditions[1]; 23% of adults report a food hypersensitivity[2].
- Marketing emails and texts need consent unless the soft opt-in applies[3][4].
- Since 30 September 2026 the regulator is the Information Commission; its role, responsibilities and powers are unchanged[5].
Why this matters for a restaurant
A busy restaurant processes personal data all day without thinking of it that way. A booking is a name, a phone number and often a note about a birthday or an allergy. A takeaway order adds an address. The Wi-Fi page collects email addresses, the cameras record everyone who walks in, and the back office holds staff bank details, right-to-work checks and sickness records. UK GDPR and the Data Protection Act 2018 apply to all of it.
The good news is that the law is built around common sense: collect what you need, tell people what you do with it, keep it safe, and do not keep it for ever. Most venues can get the essentials in place in an afternoon and keep them up to date with a short annual review.
Step one: know what you hold
Start with a simple record of your data. The table below covers the data most venues hold, a typical lawful basis for each, and a sensible approach to retention. Adjust it to your own systems and write down your reasons, because being able to explain your choices is part of compliance.
| Data | Where it lives | Typical lawful basis | Retention approach |
|---|---|---|---|
| Booking name, phone, email | Booking system, diary | Contract (taking the booking) | Delete or anonymise after a set period unless needed for a dispute |
| Allergy and dietary notes | Booking notes, tickets | Contract plus an Article 9 condition such as explicit consent | Keep only for the visit unless the guest asks you to remember |
| Deposits and card payments | Payment provider, EPOS | Contract; legal obligation for financial records | As long as tax and accounting rules require |
| Marketing list | Email platform | Consent, or soft opt-in under PECR | Until the person unsubscribes; prune inactive contacts |
| Wi-Fi sign-ins | Wi-Fi provider | Legitimate interests for running the service | Short; separate any marketing consent |
| CCTV footage | Recorder or cloud | Legitimate interests (safety, crime prevention) | Overwrite on a short cycle unless an incident is flagged |
| Staff records | Payroll, HR files, rota app | Contract and legal obligation | Set by employment, tax and pension rules |
Lawful bases in plain English
Every use of personal data needs a lawful basis. Four cover almost everything a restaurant does.
- Contract: you need the data to do what the guest asked, such as hold a table or deliver an order. You do not need consent for this.
- Legal obligation: you must keep it by law, such as payroll and VAT records or right-to-work checks.
- Legitimate interests: a reasonable business purpose that people would expect and that does not override their rights, such as CCTV for safety or keeping a no-show list. Write a short balancing note for each.
- Consent: a clear, freely given yes, needed for most marketing and often for sensitive extras. It must be as easy to withdraw as to give.
A common mistake is relying on consent for everything. If you need the data to provide the service, consent is the wrong basis, because the guest cannot really refuse it. Keep consent for things that are genuinely optional.
Allergy and dietary notes are health data
Allergies are a routine part of hospitality, and they are common: 23% of adults in England, Wales and Northern Ireland reported a food hypersensitivity in 2025[2]. When a guest tells you about a nut allergy or coeliac disease and you record it against their booking, you are processing data concerning health. UK GDPR prohibits processing health data unless one of a list of conditions applies, such as the person's explicit consent for a specified purpose[1].
- Reported a food hypersensitivity 23%
Source: Food Standards Agency, 2025[2]
Show the data
| Item | Value |
|---|---|
| Reported a food hypersensitivity | 23% |
- Ask for the information only when you need it to serve the guest safely, and record it in the booking note rather than in a general guest profile.
- Use clear wording on booking forms: “Tell us about any allergies so the kitchen can prepare your meal safely. We'll use this for your visit only.”
- Delete the note after the visit unless the guest asks you to remember it for next time, and record that choice.
- Restrict who can see guest notes, and never put health details in marketing tags or segments.
Marketing: the PECR rules
Email and text marketing sits under the Privacy and Electronic Communications Regulations as well as UK GDPR. Marketing emails and texts to individuals need their prior consent[3]. The soft opt-in is the main exception: you can market your own similar products to people whose details you obtained during a sale or negotiations for a sale, as long as you gave them a chance to refuse at the time and in every message[4].
In practice, add an unticked marketing box to booking and ordering forms, keep a record of where and when each person signed up, and include an unsubscribe link in every message. Booking confirmations and reminders are service messages, not marketing, as long as they do not carry promotions. Our guide to privacy notices for booking and guest data shows how to explain all this to guests.
Retention: decide it and automate it
UK GDPR does not give fixed retention periods for most guest data. It requires you to keep data no longer than necessary and to be able to justify your choice. Set a period for each category, write it in your record, and switch on automatic deletion or anonymisation in your booking system where it exists. Guest histories that go back years are rarely needed and become a liability if the system is ever breached.
Guest and staff rights
- Right of access: anyone can ask for a copy of their data. Most requests at venues come from staff or former staff, often during a dispute. See our guide to subject access requests.
- Right to object to marketing: this is absolute. Stop as soon as someone asks.
- Right to erasure: delete data on request unless you must keep it, for example for accounts.
- Right to rectification: correct inaccurate data promptly.
- Right to complain: people can complain to you first and then to the regulator, so give them a clear contact point.
Suppliers who handle your data
Most of the guest data you hold actually sits in someone else's system: the booking platform, the EPOS provider, the email tool, the Wi-Fi company and the payroll bureau. Where they process data on your instructions, they are your processors, and you need a written contract with them that covers security, confidentiality and what happens to the data at the end. Most reputable suppliers include these terms in their standard agreement; find them, read them once, and keep a copy.
Some platforms, particularly booking and delivery marketplaces, also use diner data for their own purposes, such as marketing other venues to the same guest. In that case they are a controller in their own right for that use. Check what your platform's terms say, and make sure your own privacy notice tells guests who else receives their details when they book.
Security and breaches
Keeping data safe is a legal duty, not just good practice. In 2025, 30% of food or hospitality businesses identified a cyber breach or attack in the previous 12 months[6]. Use strong, unique passwords and two-factor authentication on your booking, EPOS and email accounts, keep paper booking diaries out of public view, and limit who can export guest lists. If something goes wrong, you may need to report it to the regulator within 72 hours, as explained in our guide to data breaches.
The regulator changed its name, not the rules
On 30 September 2026, the Information Commission succeeded the Information Commissioner's Office as the UK's data protection regulator. The government has said the transition does not change the regulator's role, responsibilities or powers for individuals and organisations[5]. Your duties, including paying the data protection fee where it applies, carry on as before. Many guides, templates and people will still refer to the ICO for some time, and that is fine.
An afternoon compliance checklist
Map your data
Fill in the table above for your venue, including every system and paper record.
Check your lawful bases
Make sure you are not relying on consent where contract or legal obligation fits better, and write short notes for legitimate interests.
Fix allergy notes
Update booking form wording, limit access and set deletion after the visit.
Tidy marketing
Add unticked consent boxes, record sources and remove anyone you cannot show consent or a soft opt-in for.
Update your privacy notice
Cover bookings, orders, Wi-Fi, CCTV, marketing and staff, and link it from every form.
Lock down access
Turn on two-factor authentication, remove old users and move logins to business email addresses.
Diarise a review
Repeat the check once a year or whenever you add a new system.
Frequently asked questions
Is a booking name and phone number personal data?
Yes. Anything that identifies a living person, including a name with a phone number or an email address, is personal data under UK GDPR.
Do restaurants need a data protection officer?
Most do not. A DPO is required for public authorities and for organisations whose core activities involve large-scale monitoring or large-scale processing of special category data, which rarely applies to a single venue. You still need someone responsible for data protection.
Do we need consent to store allergy information?
You need a lawful basis and an extra condition because it is health data. Explicit consent at the point the guest gives the information, used only for their visit, is the simplest approach for most venues.
How long should we keep booking records?
There is no fixed period. Choose one you can justify, often months rather than years for basic bookings, and automate deletion where your system allows.
References
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑
Food Standards Agency (2025). Food and You 2: wave 11 key findings (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑
GOV.UK (2026). Information Commission succeeds the ICO as UK's data protection regulator (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑