Why it is your business
Your guest list holds names, phone numbers, emails, sometimes allergies and habits. That is personal data, and you are responsible for it, even when a provider stores it.
Article 32 of the GDPR requires the controller to put in place appropriate technical and organisational measures to ensure a level of security suited to the risk. For a restaurant, most risks do not come from sophisticated hackers but from everyday habits: a password written on the back of the till, a former employee who kept access, a tablet left open on the counter.
Our guide to GDPR and your restaurant guest list covers the wider rules: informing guests, retention, rights.
One login per person, never a shared password
The single “house” password, known to the whole team, is the most common weak spot. It gets passed around, never changes, and makes it impossible to know who did what.
One login per person solves three problems at once:
- traceability: you know who changed a booking or looked at a guest record;
- leavers: you cut one person’s access without changing everyone else’s;
- responsibility: each person protects their own password.
The French data protection authority (CNIL) recommends individual accounts and strong passwords, or stronger authentication. A long password, such as a phrase of several words, beats a short complicated one that ends up on a sticky note.
Roles: everyone sees only what they need
Not everyone needs everything. A server takes bookings and seats guests; they do not need to export the guest list or change settings. A manager handles schedules and settings. The owner keeps payments and the team.
The CNIL calls this managing access rights: define access profiles, give each person only the rights their job needs, and review them regularly. For a restaurant, three levels are often enough: staff, manager, owner.
With gonnabook.it, you invite each team member by email with a role, Staff, Manager or Owner: everyone has their own login, the Team page shows each person’s last sign-in, and you remove a member in one step.
Staff leaving: the same day
The day someone leaves the team, seasonal staff included, cut their access. Not next week: that day. Keep a list of the access to close, and keep it current:
- the booking system;
- the restaurant’s email, if they had access;
- social media and your Google profile;
- the till, if it has named accounts;
- alarm or door codes, if they knew them.
If a shared password existed anyway, change it that day. For temps, plan the end of access when they arrive: our article on training a temporary host recommends a personal login, which means closing it too.
The tablet and the computer
The host stand tablet often stays open, within guests’ reach, all evening. A few simple settings: Where it sits matters too: our guide to choosing a host stand tablet and where to put it helps keep it out of guests’ reach.
- auto-lock after a few minutes, with a code;
- updates to the system and apps, installed without delay;
- no personal browsing or unnecessary apps on the work device;
- sign out of your system when the device is shared or leaves the restaurant.
Exports: put away or deleted
A spreadsheet export of your guest list, on a desktop or a USB stick, escapes every protection your system offers. Export only when needed, store the file somewhere protected, and delete it when it is no longer useful. Never email a full guest list unprotected.
If you use a provider for newsletters, check where the data goes: our article on newsletters, texts and GDPR covers the sending rules.
If data leaks: 72 hours
A personal data breach means losing the confidentiality, integrity or availability of personal data: a stolen laptop with the list on it, a hacked account, an export sent to the wrong person.
What the GDPR provides:
- notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to put people at risk (article 33); if you go past 72 hours, explain the delay;
- inform the people affected if the risk to them is high (article 34);
- document every breach internally, including those not notified.
In France, the CNIL offers an online notification service and advises filing a police report after a cyberattack. In the moment, start by limiting the damage: change the passwords involved, cut the access concerned, alert your provider.
| Habit | What to do | When |
|---|---|---|
| Logins | One per person, never a shared password | At every arrival |
| Roles | Only the rights needed | At invitation, then every quarter |
| Leavers | Cut every access on the list | The day they leave |
| Devices | Auto-lock, updates | Ongoing |
| Exports | Stored safely, deleted after use | At every export |
| Breach | Limit, document, notify if there is a risk | Within 72 hours where feasible |
Frequently asked questions about guest data security
Can restaurant staff share a password?
It is a bad idea. A shared password gets passed around, rarely changes and makes it impossible to know who did what; it also has to be changed for everyone whenever someone leaves. Data protection authorities such as the CNIL recommend individual accounts, with rights suited to each role and strong passwords.
What should I do when an employee leaves?
Cut all their access the same day: booking system, email, social media, Google profile, till and any codes. Keep a list of these accesses so none is forgotten. If a shared password existed anyway, change it on the day they leave, seasonal staff and temps included.
What should I do if my guest list leaks?
First limit the damage: change the passwords involved and cut the access concerned. Under the GDPR, if the breach puts people at risk, notify your data protection authority without undue delay, where feasible within 72 hours, and tell the guests affected if the risk is high. Document every incident, even when you do not notify it.
Sources
- CNIL (French data protection authority), Notifier une violation de données personnelles, 72-hour deadline, two-step notification, online service, in French.
- CNIL, Règlement européen sur la protection des données, chapitre IV, GDPR articles 32 (security), 33 (notification to the authority) and 34 (communication to data subjects), in French.
- CNIL, Guide de la sécurité des données personnelles, “Authenticating users”, “Managing access rights” and “Securing workstations” sheets, in French.