Key takeaways
- Collect less and use it well: contact details, visit history, occasions and preferences guests are happy to share.
- Booking details let you run the booking; sending marketing needs separate consent or the soft opt-in.
- Start with four or five segments, such as regulars, lapsed guests and event bookers, rather than dozens.
- Security matters: 30% of food and hospitality businesses identified a cyber breach or attack in the year to 2025.
Why most guest data goes unused
Most restaurants already hold thousands of guest records spread across a booking system, a till, an online ordering platform, a Wi-Fi sign-in page and a spreadsheet of event enquiries. Very few use them. The records are duplicated, half the emails bounce, nobody knows who agreed to marketing, and the one person who understood the system has left. A useful guest database is not bigger. It is cleaner, consented and organised around a few things you will actually do.
Decide those things first. Common uses include recognising regulars when they book, remembering allergies and preferences, inviting lapsed guests back, filling quiet nights and following up event enquiries. If a field does not support one of those uses, you probably do not need it.
What to collect, and why
| Field | Why you need it | Notes |
|---|---|---|
| Name | Booking and recognition | First name and surname as the guest gives them |
| Mobile and email | Confirmations and reminders | Verify at booking; one of each is enough |
| Visit history | Spotting regulars and lapsed guests | Pulled from bookings and the till where linked |
| Occasions | Celebrations and anniversaries | Day and month only; no need for the year |
| Dietary needs and allergies | Safe service | Health information: store carefully, use only for service |
| Preferences | Personal service | Favourite table, usual drink, accessibility needs |
| Marketing consent | Knowing who you may contact | Date, channel and wording shown when given |
| Source | Knowing where guests come from | Website, phone, walk-in, platform, event enquiry |
Leave out what you will not use: dates of birth with the year, home addresses for guests who only dine in, job titles, or notes about appearance. Every extra field is something to keep accurate, secure and justify if a guest asks what you hold. Allergy and other health information needs particular care: record it only to serve the guest safely, limit who can see it and never use it for marketing.
Booking data is not marketing permission
Collecting an email to confirm a booking is part of running the booking. Using it to send promotions is marketing, and different rules apply. Under PECR, marketing emails and texts to individuals need their prior consent[1]. The soft opt-in lets a business market its own similar products by email or text to customers whose details it obtained during a sale or negotiation[2], as long as they were given a simple way to opt out when the details were collected and in every message.
Separate the two at booking
The booking form collects what the booking needs. A separate, unticked option asks whether the guest would like news and offers.
Record the consent
Store the date, the channel and the wording the guest saw, so you can show it later.
Offer an opt-out every time
Every marketing email or text includes a one-click way to stop.
Apply opt-outs everywhere
When a guest objects to marketing, their data must no longer be used for it[3]. Make sure the opt-out reaches every system, not just the email tool.
Bringing the records together
Pick one system as the home for guest profiles, usually the booking system, and connect or import the others into it. Then clean the data once, properly, before you start using it.
- Merge duplicates, matching on email and mobile.
- Remove records with no valid contact details and no recent visits.
- Mark marketing consent clearly, and treat anyone whose consent you cannot show as not consented.
- Standardise names, phone formats and dietary notes.
- Set a rule for each new data source so it lands in the same place in the same format.
Example: a two-site pub group exports 9,400 records from its booking system, ordering platform and Wi-Fi tool. After merging duplicates and removing bounced emails, 5,100 unique guests remain, of whom 2,300 have a recorded marketing consent. That smaller list becomes the only one the group emails.
Watch the side doors: Wi-Fi, platforms and phones
Guest data rarely arrives through one tidy route. Each channel has its own trap, and most database problems start in one of them.
- Wi-Fi sign-in pages: guests often enter throwaway emails and tick whatever gets them online. Treat these as low-quality records and never assume marketing consent unless it was asked for clearly and separately.
- Delivery platforms: the platform usually owns the customer relationship and shares limited details. Check your partner terms before importing anything into your own marketing lists.
- Phone bookings: details are typed in a hurry. Read back the name, number and email, and spell the email if needed, so confirmations reach the guest.
- Event enquiries: these often sit in a separate inbox. Log them in the same system so a party organiser is recognised when they book a table later.
Write a one-page note for staff on how each source should be recorded, and review a sample of new records every month to see whether the rules are being followed.
Segments that are worth the effort
Start with a handful of segments that match things you will actually do, and add more only when you have used the first ones well.
- Regulars: guests with several visits in the past few months. Use for recognition and early access to new menus.
- Lapsed guests: regulars who have not visited for a while. Use for a personal 'we miss you' note, not a heavy discount.
- Occasion guests: guests with a birthday or anniversary on file. Use, with consent, for a short message before the date.
- Event bookers: people who booked groups, parties or private dining. Use for seasonal event invitations.
- Dietary groups: guests who told you about a dietary need. Use to tell them, with consent, about new dishes that suit them, never to advertise unrelated products.
Segments help service as much as marketing. A regulars flag that appears on the booking sheet is worth more than any email campaign, as described in personal service without being creepy.
Keeping the data secure
Guest databases attract attackers because they hold contact details and sometimes card or health information. 30% of UK food or hospitality businesses identified a cyber breach or attack in the 12 months covered by the 2025 survey, compared with 43% of businesses overall[4]. The sector is less well prepared than most: only 12% had a board member responsible for cyber security[5], and 25% had sought external cyber security information or guidance, against 42% of businesses overall[6].
- Food or hospitality
- All businesses
Source: Department for Science, Innovation and Technology, 2025[4]
Show the data
| Item | Food or hospitality | All businesses |
|---|---|---|
| Identified a breach or attack in the last 12 months | 30% | 43% |
| Sought external cyber security guidance | 25% | 42% |
- Give every user their own login and remove leavers on their last day.
- Turn on two-step sign-in for the booking system, email and any marketing tool.
- Limit exports, and never send guest lists by personal email or messaging apps.
- Restrict who can see allergy and health notes to those who need them for service.
- Check that your booking and marketing suppliers protect data and will help if something goes wrong.
- Write down what you would do in the first hour after a breach, including who you would contact.
Guests' rights and retention
Guests can ask what you hold about them, ask you to correct it, and in many cases ask you to delete it. They can object at any time to their data being used for direct marketing, and once they do, it must not be used for that purpose[3]. A lean, well-organised database makes those requests quick to handle.
Set a retention rule and apply it. A common approach is to keep active guests' profiles while they keep visiting, review records with no visits for a long period, and delete or anonymise those you no longer need. Keep consent records for as long as you rely on the consent. Write the rule in your privacy notice so guests know what to expect.
12%
of UK food or hospitality businesses had a board member responsible for cyber security in 2025[5]
Using the database in daily service
The best test of a guest database is whether it changes what happens on a Friday night. At the pre-shift briefing, the manager reads out regulars, occasions and allergies for the evening's bookings. The host greets returning guests by name. The server knows the gluten-free guest at table six before they sit down. None of that needs a marketing campaign; it needs accurate records and a habit of reading them. For birthday touches built on the same data, see making birthdays and anniversaries special, and for the question of whether to add rewards, loyalty schemes: points, perks or nothing.
Frequently asked questions
What guest data should a restaurant collect?
Name, a mobile number and email, visit history, occasions (day and month), dietary needs and allergies, preferences such as a favourite table, the source of the booking and a clear record of marketing consent.
Can I email guests who booked a table?
You can send what the booking needs, such as confirmations. Marketing needs prior consent, or the soft opt-in for your own similar products where you gave a chance to opt out when collecting the details and in every message.
How should a restaurant store allergy information?
Record it only to serve the guest safely, restrict who can see it, keep it accurate and never use it for marketing. Allergy details are health information and need extra care.
How long should I keep guest data?
Only as long as you need it. Keep active guests' records while they visit, review records with no visits for a long period, and delete or anonymise those you no longer need.
References
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) ↑
legislation.gov.uk (2016). UK GDPR, Article 21: right to object (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) ↑