Key takeaways
- UK GDPR requires you to give people key information at the time you collect their data, including who you are, why you use it, the lawful basis and who receives it[1].
- Write one clear guest notice covering bookings, orders, Wi-Fi, CCTV and marketing, and a separate notice for staff.
- Put it where guests make decisions: booking pages, order checkouts and the Wi-Fi sign-in. 44% of consumers who know the hygiene scheme had seen ratings on a business's own website[2].
- Marketing needs consent unless the soft opt-in applies, so say which you rely on[3][4].
What the law requires
When you collect personal data directly from someone, UK GDPR requires you to tell them certain things at the time you collect it[1]. That information is your privacy notice. For a restaurant, the collection moments are easy to list: a guest books a table, orders a takeaway, signs in to the Wi-Fi, joins the mailing list, walks past a camera, or applies for a job.
Article 13 sets out what to include. The essentials are your identity and contact details, the purposes and lawful basis for each use, any legitimate interests you rely on, who receives the data, whether it leaves the UK, how long you keep it, and the rights people have, including the right to complain[1]. You also need to say whether giving the data is required to provide the service, such as a phone number for a booking, and what happens if they do not provide it.
The notice does not need to be long or legalistic. It needs to be accurate, specific to what you actually do, and easy to find at the moment it matters.
The sections every venue notice needs
| Heading | What to cover | Example wording |
|---|---|---|
| Who we are | Legal entity, trading names, address, contact for privacy questions | The Old Forge is run by Forge Kitchens Ltd. Contact privacy@ with any questions. |
| Bookings | Details collected, why, lawful basis, booking platform used | We use your name, phone and email to hold your table and contact you about your booking. |
| Allergies and dietary needs | Health data, used only to prepare food safely, how long kept | If you tell us about an allergy, we use it only for your visit and delete it afterwards unless you ask us to remember it. |
| Takeaway and delivery | Address, order history, delivery partners | Orders through delivery apps are also covered by that app's own privacy notice. |
| Payments and deposits | Payment provider, what you see, records kept for tax | Card payments are processed by our payment provider; we do not store full card numbers. |
| Wi-Fi | What the sign-in collects, purpose, provider | Signing in to our Wi-Fi does not sign you up to marketing unless you tick the box. |
| CCTV | Purpose, areas covered, retention, how to request footage | We use CCTV for safety and to prevent crime. Footage is overwritten after a short period unless needed for an incident. |
| Marketing | Consent or soft opt-in, how to unsubscribe | We email news only if you ask us to, or if you have bought from us and did not opt out. |
| Sharing | Processors and anyone else who receives data | Our booking, email, Wi-Fi and payment providers, and the police if required by law. |
| Your rights | Access, correction, erasure, objection, complaints | You can ask for a copy of your data or complain to us, and then to the Information Commission. |
Bookings and booking platforms
Most venues take bookings through a third-party platform. For your own bookings, the platform is usually your processor, acting on your instructions. But many booking and discovery platforms also use diner details for their own purposes, such as recommending other restaurants, which makes them a controller for that use. Read your platform's terms, then describe the arrangement honestly: “We use [platform] to manage reservations. If you book through [platform's] own app or website, they also use your details under their own privacy notice.”
Be specific about notes. If staff record birthdays, seating preferences or a history of no-shows, say so, and explain why. A no-show record is usually justified as a legitimate interest, but guests should not discover it by surprise.
Takeaway, delivery and click-and-collect
Orders through your own website or app are yours to explain: name, address, phone, order history and any delivery notes. Say whether you use your own drivers or a courier service, because the courier receives the address and phone number. Orders placed through a delivery marketplace are different: the marketplace collects the data under its own notice and passes you what you need to prepare the order. A line in your notice that makes this clear saves confusion when a guest asks why they are getting emails from the app rather than from you.
If you keep order history to offer a quick reorder or loyalty reward, say so and say how long you keep it. Delivery notes sometimes contain door codes or health details, so limit who can see them and clear them after the order.
Wi-Fi sign-in pages
Guest Wi-Fi is where many venues collect most of their email addresses, and where many get the rules wrong. The sign-in page should explain, in a sentence, what details are collected, why, and who runs the service. Marketing consent must be a separate choice that is not ticked by default, and guests should be able to use the Wi-Fi without agreeing to it. Marketing emails and texts to individuals need prior consent[3], and a Wi-Fi sign-in is not a sale, so the soft opt-in does not help here.
CCTV
Cameras need signs that are visible before people enter the recorded area, naming who runs the system and how to contact them. The privacy notice then gives the detail: why you use CCTV, which areas are covered, how long footage is kept and how someone can request a copy. Keep cameras out of toilets and staff changing areas, and think hard before recording audio, which is far more intrusive than video.
Private dining, events and gift vouchers
Private dining and events add data that ordinary bookings do not: guest lists, dietary requirements for a whole party, company invoicing details and sometimes accessibility needs. The organiser usually gives you other people's details, so the notice should explain how you use guest lists, that you use them only for the event, and when you delete them. Gift vouchers collect the buyer's details and sometimes the recipient's name; cover both.
For long notices, a layered approach works well. Give a short summary at the top, with the five or six things guests most want to know, then the full detail below under clear headings. Guests who only want reassurance can stop after the summary, and the detail is there for anyone who needs it.
Marketing and the soft opt-in
Say plainly which basis you use for each marketing list. Under PECR, marketing emails and texts need consent[3], except under the soft opt-in, which lets you market your own similar products to people whose details you obtained during a sale or negotiations for a sale, provided they had a simple way to refuse at the time and in every message[4]. If you rely on the soft opt-in for takeaway customers, your checkout should show an opt-out box and the notice should say so.
Where to put it
A notice nobody can find does not do its job. Guests look for information online, but finding it is not always easy: in the Food Standards Agency's 2025 research, 56% of consumers found hygiene ratings easy to find when eating out in person, but only 29% when ordering online[5]. The same lesson applies to privacy information. Among people who know the hygiene scheme, 44% had come across ratings on a business's own website and 26% on an ordering or delivery app[2], which shows those are the places guests look.
Source: Food Standards Agency, 2025[2]
Show the data
| Item | Value |
|---|---|
| A food business's own website | 44% |
| A food ordering or delivery app | 26% |
- A link in the footer of every page of your website, labelled Privacy.
- A short line and a link next to the submit button on booking, ordering and enquiry forms.
- A link in booking confirmation emails and on the Wi-Fi sign-in page.
- CCTV signs at entrances, with a contact and a pointer to the full notice.
- A separate staff privacy notice in the staff handbook or HR system, covering recruitment, payroll, rotas, right-to-work checks and monitoring.
Writing and reviewing the notice
List every collection point
Bookings, orders, Wi-Fi, CCTV, enquiries, gift vouchers, events, loyalty and job applications.
For each, write four facts
What you collect, why, the lawful basis, and who else receives it. This becomes the body of the notice.
Check retention
Write down how long you keep each type of data and make sure your systems actually delete it then.
Write it in plain English
Short sentences and headings that match the guest's journey. Avoid copying a template full of activities you do not carry out.
Link it everywhere
Add links at every collection point, and put the date of the last update at the top.
Review it when anything changes
A new booking platform, cameras in the garden or a loyalty app means updating the notice the same week.
Example: a fictional pub adds cameras to its beer garden and switches Wi-Fi provider in the same month. The manager updates the CCTV and Wi-Fi sections, changes the provider name, moves the date at the top of the notice and checks that the new sign-in page links to it.
Common gaps
- A generic template that mentions activities you do not carry out and misses ones you do, such as CCTV.
- No mention of allergy notes, which are health data and deserve their own line, as explained in UK GDPR for restaurants.
- Marketing consent bundled into the booking terms, so guests cannot book without agreeing.
- No contact for privacy questions, which makes it harder to handle subject access requests quickly.
- Nothing about what you would do if something goes wrong. You do not need to describe your breach plan in the notice, but you do need one.
Frequently asked questions
Do we need a separate privacy notice for staff?
Yes. Staff data covers recruitment, payroll, right-to-work checks, rotas and sometimes monitoring, which guests do not need to read about. Keep a separate staff notice in your handbook or HR system.
Can we just link to our booking platform's privacy notice?
Not instead of your own. The platform's notice covers its own use of the data; yours must explain what your venue does with guest details.
How long should a restaurant privacy notice be?
As long as it needs to be to cover what you actually do, and no longer. Clear headings for bookings, orders, Wi-Fi, CCTV and marketing make even a full notice easy to scan.
Do we need to mention the regulator?
Yes. Tell people they can complain to you first and then to the Information Commission, the UK's data protection regulator, which succeeded the ICO in September 2026.
References
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 13: Information to be provided where personal data are collected from the data subject (opens in a new tab) ↑
Food Standards Agency (2025). Food Hygiene Rating Scheme (FHRS) Food and You 2 report: wave 11 (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) ↑
Food Standards Agency (2025). Food Hygiene Rating Scheme (FHRS) Food and You 2 report: wave 11 (opens in a new tab) ↑