Guest data and GDPR

Restaurant allergies: from the booking to the plate, without losing anything on the way

Handling allergies well means one thing: the allergy a guest mentions when booking reaches the kitchen, then the plate, without getting lost on the way. That takes a short chain of habits, from the booking form to the moment the dish is set down. This guide walks through that chain, link by link. It also sums up the rules in the European Union and in France, as one example of a legal framework; if you run a restaurant elsewhere, such as in the UK or the US, check the rules of your local food authority. It does not replace professional advice for a specific case.

The gonnabook.it team6 min read

The legal backdrop: the EU and France

Fourteen allergens under EU law

Under EU law, Regulation (EU) No 1169/2011 on food information to consumers lists in its Annex II the substances causing allergies or intolerances that must be declared. Its Article 44 extends allergen information to non-prepacked food, which covers dishes served in restaurants and cafés.

The 14 allergens of Annex II of Regulation (EU) No 1169/2011
AllergenWhere it often hides
Cereals containing glutenwheat, rye, barley, oats: pastry, breadcrumbs, thickened sauces
Crustaceansprawns, shrimp, langoustines, stock
Eggsmayonnaise, egg wash, mousse
Fishanchovies in a dressing, fish stock
Peanutsoil, satay, some pralines
Soybeanssoy sauce, lecithin
Milkbutter, cream, lactose
Nutsalmonds, hazelnuts, walnuts, pistachios, pesto
Celerystock, celery salt
Mustarddressings, marinades
Sesame seedsbread, oil, tahini
Sulphur dioxide and sulphiteswine, vinegar, dried fruit (above 10 mg/kg or 10 mg/litre)
Lupinflour in some baked goods
Molluscsmussels, squid, oyster sauce

What France adds

In France, decree No 2015-447 of 17 April 2015 set the national rules for non-prepacked food; they now sit in Articles R412-12 to R412-16 of the French Consumer Code. A restaurant must make written allergen information about its dishes available to guests: on the menu, on a board, in a binder at the front desk, any medium guests can consult directly and freely. A server’s spoken answer complements that written information; it does not replace it.

Ask when they book

The best time to learn about an allergy is before service: the kitchen has time to check a recipe or plan an alternative. At the table, at 8:30 pm on a Saturday, it is often too late to do it well.

So ask with every booking, online and on the phone. An open question works better than an “allergy: yes / no” box: guests also mention a diet, a child who won’t eat fish, a lactose intolerance. On the phone, one line does it: “Any allergies or special requests we should know about?”

In your confirmation, say you have noted it and invite the guest to mention it again on arrival. Ready-to-adapt wording is in our restaurant booking message templates.

Record it with care: it is health data

Under the GDPR, which applies in the EU, an allergy or a diet linked to an illness is health data, one of the so-called special categories. Article 9 of the regulation prohibits processing it in principle, with exceptions, including the person’s explicit consent.

In practice, for today’s booking, write down what the guest tells you, in their words, and nothing more. Do not infer (“gluten-free” does not mean “coeliac”), and share it only with the team who needs it. To keep it from one visit to the next, ask first: “Would you like us to keep this on file for your next visits?” And delete it if they ask. The wider rules are in our guide GDPR and your guest list; outside the EU, check your local data protection rules.

Make it visible during service

An allergy written in a closed book protects no one. It has to show up where the team looks during service: the day’s booking list, the table’s card.

That is what gonnabook.it does: the booking form asks “A request, an allergy?”, and the guest’s answer shows on the booking card the team sees during service.

At the pre-shift briefing, go through the day’s allergies table by table: who, what, and how serious if the guest said so. It takes half a minute, and whoever greets that table will have heard it. Our article on the pre-shift briefing sets out the whole routine.

Drawing of a booking card marked with a crossed-out wheat ear, next to a plate with a flag stuck in the dish.
From booking to plate: the allergy follows the table, all the way to the flag in the dish.

Flag the ticket, confirm at the table

When taking the order, the server confirms the allergy with the guest, even if it is on the booking: it may concern someone else at the table, or one diner may have been forgotten. Then it goes on the order ticket where no one can miss it: its own line, at the top, with the seat number.

In the kitchen, the dish leaves with an agreed marker (a pick, a different plate) and, where possible, the same person carries it to the table: “Your dish, without nuts.”

Think about cross-contact

Taking the walnuts off a salad is not enough if it was made on the board used for the pesto. Cross-contact comes from utensils, worktops, shared fryer oil and hands. A few habits:

  • a cleaned worktop and clean utensils before preparing an allergen-free dish;
  • separate fryer oil if you offer gluten-free fries or chips;
  • up-to-date recipe sheets listing the allergens of every dish, including stocks, sauces and bought-in products;
  • honesty: if you cannot rule out traces, tell the guest, and let them decide.

Every change of supplier or recipe must reach the allergen information. That is where written information most often stops being accurate.

Keep it for the next visit, with consent

A returning guest appreciates not having to explain everything again. If you keep their allergy on file, do so with their explicit consent, and check it with them on the next visit: allergies and diets change.

Otherwise, your guest list’s retention rule applies: a record that no longer serves is deleted, and the allergy with it. More in the Guest data and GDPR category.

Frequently asked questions

Which allergens must a restaurant declare in the EU?

Under EU law, the 14 listed in Annex II of Regulation (EU) No 1169/2011: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphites above set levels, lupin and molluscs. Article 44 extends this information to non-prepacked food, restaurants included. Outside the EU, such as in the UK or the US, check the rules of your local food authority.

Can I keep a guest’s allergy on file?

Under the GDPR, an allergy is health data, a special category under Article 9. Record it for the booked meal, from what the guest tells you, and keep it for future visits only with their explicit consent. Limit access to the team members who need it and delete it on request. Outside the EU, check your local data protection rules before keeping it.

What if the kitchen cannot rule out traces?

Tell the guest clearly, before they order. Explain what you can do, for example preparing a dish separately, and what you cannot, such as a shared fryer or flour used throughout the kitchen. The guest can then decide with full information. A dish they decline is better than a promise your team cannot keep, especially on a busy night.

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