Guest data and GDPR

Guests who never turn up: what to record, what to do

When a guest keeps booking and never turns up, recording dated facts on their record and asking for a guarantee next time works better than keeping a blacklist. GDPR governs what you write about your guests, the person can read it, and in France the data protection authority, the CNIL, treats lists that exclude people, especially shared ones, as a separate kind of processing. This article describes the rules as they apply in France, under GDPR and CNIL guidance.

The gonnabook.it team6 min read

Facts, not judgements

Recording that a guest did not come is useful for managing bookings. Everything depends on how you write it.

GDPR requires personal data to be “adequate, relevant and limited to what is necessary” for its purpose (data minimisation), and accurate (Article 5(1)(c) and (d)). For no-shows, that means:

  • yes: “Did not come on 14 March, no notice, table for 4”;
  • yes: “Cancelled on the day, 2 April”;
  • no: “Unreliable”, “Avoid”, or any guess about their private life and reasons.

In its guidance on free-text comment fields, the CNIL says comments must not be inappropriate, subjective or insulting. It recommends limiting free text in favour of objective choices: the status set on a booking does exactly that.

Take extra care with health (Article 9: “absent, in hospital” has no place on a booking record) and with offences (Article 10: do not write that a guest “stole” something; only certain authorities may process that kind of information).

Guests can read what you wrote

This is the rule that should guide every note. Anyone can ask the controller, here your restaurant, to confirm whether data about them is being processed, and obtain a copy of it (Article 15 GDPR). You must reply within one month of receiving the request (Article 12(3)). The CNIL stresses the point: the person concerned can exercise their right of access at any time and read those comments.

Guests can also ask for inaccurate data to be corrected without undue delay (Article 16). A no-show logged by mistake, because the guest did come but sat at another table, must be put right.

The simplest test, already suggested in our article on GDPR and your guest list: write nothing you could not read aloud to the guest concerned.

How long to keep a no-show

Data must not be kept longer than necessary for its purpose (Article 5(1)(e)). The CNIL sets no specific period for a restaurant guest’s no-shows. Its reference framework for managing commercial activities gives a close benchmark: customer data used for marketing may be kept for the length of the commercial relationship, then for three years from its end, for example from the last contact initiated by the customer.

A simple, defensible rule: the no-show history follows the guest record, and disappears with it when the guest has not booked for three years.

Drawing of a guest record card with three lines of text, two date badges and an orange tick, next to a yellow padlock.
A record you could read aloud: dates and facts, kept as long as they are useful, and nothing else.

What to do with the information

A no-show history is there to adapt how you welcome a guest, not to punish them. One absence is just life getting in the way: do nothing. Two or three is a signal. A few proportionate responses:

  • call the day before to confirm, rather than relying on the reminder e-mail alone;
  • ask for a guarantee on the next booking, a deposit or a card hold, announced in writing at the time of booking;
  • switch the booking to a request: you approve it yourself after a quick exchange, as you would for a large group (the choice between instant confirmation and manual approval is covered separately).

These responses target an observed behaviour, not a person you have judged. The general levers against no-shows are in our guide to reducing restaurant no-shows.

With gonnabook.it, a guest’s visit and no-show counts keep themselves up to date from the “Completed” and “No-show” statuses set on their bookings, and appear in the details of each booking.

Blacklists: tread carefully

Turning a guest away

In France, refusing to serve a customer is not a free choice. Asked in the Senate about restaurants turning away customers whose spending they judged too low, the French ministry in charge of trade replied in 2025 that such a practice could amount to a refusal to sell, prohibited by the French Consumer Code and punishable by a fifth-class fine, unless there is a legitimate reason, assessed case by case. Do repeated no-shows count as one? No text says so. Asking for a guarantee is therefore safer than a flat refusal.

A list shared between restaurants

The idea comes up often: pool the names of guests who never show. The CNIL lists “shared processing of observed contractual breaches that may lead to a decision to exclude someone from, or suspend, a contract” among the operations that require a prior data protection impact assessment. And its framework for commercial activities does not cover processing that may exclude people from a service: such lists fall outside the ordinary scope of a customer file.

In practice, a blacklist shared between restaurants, in a messaging group or a common spreadsheet, is not a friendly tip between neighbours: it is heavyweight processing that calls for serious legal work. For an independent restaurant, the sensible answer is to stick to its own factual history, and to guarantees.

Frequently asked questions about repeat no-shows

Can a restaurant keep a blacklist of guests?

In France, recording in your own file that a guest did not turn up is possible, factually and for a limited time. A list designed to exclude guests, let alone one shared between restaurants, is a separate kind of processing: the CNIL requires an impact assessment for shared lists of contractual breaches that may lead to exclusion. Asking for a guarantee is the safer route.

What can I write about a guest who did not show up?

Dated facts: “did not come on 14 March, no notice, table for 4”, or “cancelled on the day”. Never opinions such as “unreliable”, nor guesses about their health or private life. Under GDPR, the guest can ask to see what you recorded about them, and have inaccurate information corrected.

How long can I keep a guest’s no-show history?

No longer than necessary. The French data protection authority sets no specific period for this case; for customer data used in marketing, its framework uses the length of the commercial relationship plus three years from the last contact. Deleting the history together with the record, three years after the last booking, is a simple and consistent rule.

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