What you hold on a guest, how long you keep it and who may ask for it.
FIG. 02
Guest data and privacy
A booking from two years ago still holds a name, a phone number and an allergy note. Data kept longer than it is needed is exposure the restaurant chose to keep.
FIG. 03
Guest data and privacy
A message on Instagram asks for everything you hold on her. Nobody on the floor recognises it as a request, and days of the statutory month are already lost.
FIG. 04
Guest data and privacy
An exposed guest record can leave a restaurant unsure what happened, who is affected and whether the ICO reporting threshold is met.
FIG. 05
Guest data and privacy
A restaurant can add one booking embed or advertising pixel and start non-essential tracking before a guest has chosen, leaving banner and behaviour out of step.
FIG. 06
Guest data and privacy
A booking email can confirm a table without authorising promotions. Mix the two, and a routine guest record can become a PECR compliance risk.
FIG. 07
Guest data and privacy
Booking, dietary and marketing complaints can expose scattered guest records and missed deadlines before a restaurant establishes what went wrong.
FIG. 08
Guest data and privacy
A booking form that collects too much or explains privacy too late can leave restaurants with uncontrolled guest records, confused customers and complaints.
FIG. 09
Guest data and privacy
An unchecked restaurant guest-list export risks unreadable columns, altered values and unmanaged personal data during a staff handover.