Guest data and GDPR

GDPR and your guest list: what your restaurant is allowed to do

Your guest list is a treasure: it tells you who comes, what they like, what they cannot eat. It is also a file of personal data, governed by the General Data Protection Regulation (GDPR). Nothing insurmountable for a restaurant: a few common-sense principles, and you are compliant. This guide goes through them; it does not replace legal advice for a specific case.

The gonnabook.it team5 min read

Who is responsible for what

Under the GDPR, your restaurant is the controller of its guest list: you decide why you collect data and what you do with it. Your booking software is a processor: it handles that data on your behalf, following your instructions.

This split has a practical consequence: a contract must govern the relationship between you and your processor (Article 28 of the GDPR sets out its content). With most publishers, it is a data processing agreement attached to the terms. Check that it exists, and where the data is hosted.

What you may record

The key principle is called data minimisation: only collect what serves the service. For a booking, that comes down to very little: name, party size, date and time, a way to get in touch (phone or e-mail).

Over the visits, you may enrich the record with what improves hospitality:

  • preferences (“likes the table by the window”, “sparkling water”);
  • occasions the guest shared with you (a birthday, if they told you so you could celebrate it);
  • the history of visits, cancellations and no-shows.

Factual notes, never judgements

Your guest may ask to see what you have written about them. So write facts (“no-show without notice on 12 March”), never opinions (“difficult guest”). A good rule: write nothing you could not read out to them.

The case of allergies

An allergy or a diet linked to an illness is health data, one of the so-called sensitive categories of the GDPR. Processing it is forbidden in principle, with exceptions, including the person’s explicit consent.

For a restaurant, it comes down to this: record an allergy only if it serves the meal, when the guest tells you about it and agrees that you keep it for future visits. Do not infer it, do not share it beyond the team that needs it, and delete it if the guest asks. The whole chain is described in allergies, from the booking to the plate.

Drawing of a guest record protected by a shield, with a padlock.
A record that serves the service: preferences, allergies the guest reported, history. Nothing more.

Writing to your guests

Booking-related messages (confirmation, reminder, change) are part of the service: you may send them without any particular consent, since the guest booked.

A newsletter or a promotional offer is something else: it is marketing. To send it by e-mail or text message to an individual, you generally need their consent, collected with an unticked checkbox, and every message must offer a way to unsubscribe. Never add your guests to a mailing list without their agreement. To bring them back without a newsletter, see how to build regulars without a loyalty card. The same consent principle applies to the trackers on your website: see what the CNIL asks of restaurant website cookies.

How long to keep data

Data is not kept forever. It is up to you to set a duration, according to its usefulness. For a guest list used for marketing, the French data protection authority (CNIL) takes three years after the last contact with the guest as a benchmark.

For a restaurant, a simple rule works well: a record whose guest has not booked for three years is deleted or anonymised. Allergies and notes that no longer serve disappear with it.

What your guests can ask you

Your guests have rights over their data, and it is up to you, as controller, to respond, generally within one month.

  • Access: knowing what you have recorded about them, and receiving a copy.
  • Rectification: correcting wrong information.
  • Erasure: having their record deleted, unless you are legally required to keep some data.
  • Objection: refusing your marketing messages.

Your booking tool should let you find a record, correct it, export it and erase it. If a feature is missing, your processor must help you respond. Protecting access to the list matters just as much: we cover logins, passwords and staff leaving.

Choosing a tool that makes it easy

Three questions to ask your booking software: where is the data hosted? Is there a data processing agreement? Does it write to your guests on its own behalf? gonnabook.it, for instance, acts as a processor, hosts the data in Paris and only writes to your guests about their booking.

Frequently asked questions

Does a restaurant need consent to record a booking?

No: the data needed for the booking serves to deliver what the guest asked for. Consent is needed for marketing and for keeping health data such as allergies.

Can I note that a guest did not show up?

Yes, factually (“no-show without notice on 12 March”). It is useful for managing bookings, and the guest can see it if they ask.

Can I use my guest list to send a newsletter?

Only to guests who agreed to it, with an unsubscribe link in every mailing.

Sources

· All articles

Read next
Your guests, your data

A guest list that stays yours.

gonnabook.it only writes to your guests about their booking, and your data is hosted in Paris. Try it free for 30 days.

Free 30-day trial

No credit card · no commitment · €69 excl. VAT per month afterwards