Reservations and table management

Who owns guest data on booking platforms?

Controller and processor roles on restaurant booking platforms under UK GDPR, what marketing consent covers, and how to export guest data and leave.

Ava research teamPublished 7 min read

On this page
  1. Ownership is the wrong question
  2. When the platform is your processor
  3. When the platform is also a controller
  4. Common set-ups compared
  5. What marketing consent really covers
  6. Getting your data out
  7. Questions to put to your platform
  8. Telling guests who handles their data
  9. Security is your responsibility too
  10. Example: moving platforms with the data intact
  11. A short checklist
  12. Frequently asked questions
  13. References

Key takeaways

  • Under UK GDPR the question is not who owns guest data but who controls it: who decides why and how it is used.
  • For bookings taken for your venue, you are usually the controller and the platform your processor, bound by a contract to follow your instructions.
  • Consumer booking apps may also be controllers in their own right for diners who hold accounts with them, so the same guest can have two relationships.
  • Consent to marketing is specific: consent given to a platform is not consent for you to market, and the reverse is also true.

Ownership is the wrong question

Operators often ask who owns the guest list on their booking platform. Data protection law does not really work in terms of ownership. It asks who controls the data, meaning who decides what it is used for and how, and who merely processes it on someone else's behalf. The answer decides who is responsible for the guest's rights, who can use the data for marketing and what happens to it when you change systems.

UK GDPR defines a controller as the person or body which, alone or jointly with others, determines the purposes and means of processing personal data, and a processor as a person or body which processes personal data on behalf of the controller[1]. Most of what follows comes down to applying those two definitions to the way your bookings actually work.

When the platform is your processor

When a guest books a table at your restaurant through your website widget or your staff enter a phone booking, you decide why the data is collected (to manage the booking) and what happens to it. The platform stores and processes it for you. In that set-up, you are normally the controller and the platform is your processor.

UK GDPR requires processing by a processor to be governed by a contract[2]. That contract must say the processor processes the personal data only on documented instructions from the controller, and that at the controller's choice it deletes or returns all the personal data at the end of the service[2]. In plain terms: the platform should not use your guests' details for its own purposes, and you should be able to take the data with you or have it deleted when you leave.

When the platform is also a controller

Consumer booking apps work differently. A diner who creates an account on a platform's app, saves favourite restaurants and gets recommendations has a relationship with the platform itself. For that account and the platform's own marketing, the platform decides the purposes and means, so it is a controller in its own right. When that diner books your restaurant, the booking details may be shared with you, and you become a controller for your use of them.

The result is that the same guest can appear in two places under two sets of rules. The platform may email them about other restaurants; you may only contact them in line with your own lawful basis and any consent they gave to you. Read the platform's terms to see how it describes its role, and ask if it is unclear.

Common set-ups compared

Typical controller and processor roles for restaurant booking set-ups
Set-upYour rolePlatform's roleCheck
Booking widget on your own websiteControllerProcessorProcessing terms, export, deletion on exit
Phone bookings entered by staffControllerProcessorSame as above; staff access controls
Booking through Google with a connected providerController for your bookingProvider is usually your processorHow the provider handles the booking data
Booking through a consumer app where the diner has an accountController for your useController for its app and marketingWhat is shared with you, and what the platform may do with the diner's data
Group of venues sharing one guest databaseController, possibly jointly with sister companiesProcessorWhich company is named in the privacy notice; whether sharing is explained to guests

This table is a general guide, not legal advice. Contracts vary, and the platform's terms and how it actually behaves both matter. If your set-up is unusual, take advice and write down your conclusions.

Marketing is where the roles bite. Marketing emails and texts to individuals need their prior consent[3], unless the soft opt-in applies: a business may market its own similar products to customers whose details it obtained during a sale or negotiation, provided they were given a simple chance to refuse[4]. Consent itself must be freely given, specific, informed and unambiguous[1].

  • Consent a diner gave to a booking platform to receive its newsletter is not consent for your restaurant to market to them.
  • Consent a guest gave to your restaurant does not automatically extend to your sister brands, unless they were named when consent was given.
  • A guest who booked through a platform and never opted in to your marketing should get booking messages only.
  • Keep a record of when, where and how each guest opted in. Without it, you cannot show the consent was valid.

Getting your data out

  1. Ask what an export contains

    Guest names, contact details, visit history, notes, dietary information, marketing consent with dates, and future bookings.

  2. Check the format

    A CSV or spreadsheet with clear column names is easiest to move. A PDF report is not an export.

  3. Test it now

    Run an export today, open it and check the counts against what the platform shows. Do this again before you give notice.

  4. Agree the exit process

    Ask how long you keep access after notice, whether there is a charge, and when the platform will delete the data.

  5. Handle sensitive notes carefully

    Allergy and health notes need extra care in any export. Limit who receives the file and delete copies you no longer need.

Questions to put to your platform

Ask these in writing and keep the answers with your contract. Clear, quick answers are a good sign; vague ones are a reason to look harder before renewing.

  • For bookings taken for our venue, do you act as our processor? Where are the processing terms?
  • In which cases do you act as a controller yourselves, and what do you do with diners' data in those cases?
  • Which other companies process our guest data for you, and in which countries?
  • Do you use our guests' details to market other venues or your own services?
  • What does a full export contain, and how long do we keep access after giving notice?
  • How and how quickly would you tell us about a breach affecting our guests?

Telling guests who handles their data

When you collect personal data from a guest, UK GDPR requires you to tell them, at the time, who you are, why you are processing the data, on what legal basis and who will receive it[5]. In practice your privacy notice should explain that bookings are managed through a booking provider acting for you, name any other recipients and say how long data is kept. Link it from the booking widget and the confirmation email.

Security is your responsibility too

Using a processor does not hand over your responsibility for keeping guest data safe. In the government's 2025 survey, 30% of food or hospitality businesses had identified a cyber breach or attack in the previous 12 months[6], only 12% had a board member responsible for cyber security[7] and 25% had sought external information or guidance on it[8].

Cyber security in UK food or hospitality businesses, 2025
Cyber security in UK food or hospitality businesses, 2025Bar chart. Identified a breach or attack in the last 12 months: 30%; Sought external cyber security guidance: 25%; Board member responsible for cyber security: 12%.Identified a breach or attack in the last 12 monthsIdentified a breach or attack in the last 12 months: 30%30%Sought external cyber security guidanceSought external cyber security guidance: 25%25%Board member responsible for cyber securityBoard member responsible for cyber security: 12%12%Cyber security in UK food or hospitality businesses, 2025Bar chart. Identified a breach or attack in the last 12 months: 30%; Sought external cyber security guidance: 25%; Board member responsible for cyber security: 12%.Identified a breach or attack in thelast 12 monthsIdentified a breach or attack in the last 12 months: 30%30%Sought external cyber security guidanceSought external cyber security guidance: 25%25%Board member responsible for cybersecurityBoard member responsible for cyber security: 12%12%

Source: Department for Science, Innovation and Technology, 2025[6]

Show the data
ItemValue
Identified a breach or attack in the last 12 months30%
Sought external cyber security guidance25%
Board member responsible for cyber security12%
  • Give every user their own login, remove leavers immediately and limit exports to managers.
  • Turn on two-step sign-in for the booking platform and the email account linked to it.
  • Ask the platform how it would tell you about a breach affecting your guests, and how quickly.

Example: moving platforms with the data intact

Example: a fictional two-site restaurant group decided to change booking platforms. Before giving notice, the operations manager exported guest records, booking history and consent records, and found that consent dates were missing for guests who had opted in on the old paper forms. Those guests were moved across as booking contacts only, not marketing contacts.

Example: diners who had booked through a consumer app had been shared with the group with booking details but no marketing consent, so they too were kept out of the newsletter. The group imported future bookings into the new system, confirmed with the old platform in writing that its copy would be deleted after the notice period, and updated the privacy notice to name the new provider's role. The marketing list was smaller than before, but every name on it could be defended.

A short checklist

  1. Find the data processing terms in your booking platform's contract and read the parts on instructions, sub-processors and exit.
  2. Work out where the platform is your processor and where it acts as a controller in its own right.
  3. Check that marketing consent is recorded per guest, with a date and source.
  4. Run a test export and keep it securely.
  5. Update your privacy notice to describe the booking provider's role.
  6. Diarise a yearly check, and repeat it before any change of platform.

These questions belong in any platform choice; see how to choose a restaurant booking system and free versus paid booking software. If you take bookings through Google, our guide to Reserve with Google covers the set-up.

Frequently asked questions

Does the booking platform own my guest list?

Usually not in the way people mean. For bookings taken for your venue, you are normally the controller and the platform your processor, which must follow your instructions and return or delete the data when the contract ends. Consumer apps may also hold their own data on diners with accounts.

Can I email guests who booked through a consumer app?

You can send messages about their booking. For marketing, you need their consent to hear from you, or a valid soft opt-in. Consent they gave to the app is not consent for your venue.

What should a guest data export include?

Names, contact details, visit history, notes, marketing consent with dates and sources, and future bookings, in a standard format such as CSV.

Do we need to mention the booking platform in our privacy notice?

Your privacy notice should explain who receives guest data, so describe the booking provider's role and any other recipients, and link the notice from your booking pages and confirmations.

References

  1. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 4: Definitions (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 28: Processor (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑

  4. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22(3) soft opt-in (opens in a new tab) ↑

  5. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 13: Information to be provided where personal data are collected from the data subject (opens in a new tab) ↑

  6. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  7. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (board responsibility) (opens in a new tab) ↑

  8. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (sources of guidance) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo