Log in
Sign up
Social
Back to Knowledge Base
Forms & Leads

GDPR on Your Restaurant Website: Handling Data from Forms, WhatsApp and Email Correctly

Every day your restaurant website collects more personal data than you might realise: a phone number through a contact form, a CV through a job application, an email address for the newsletter, a name and party size through your booking system. As a restaurant, you’re responsible for that data under GDPR. Fortunately, that doesn’t have to be a weeks-long legal project once you have a few basics in place.

Where does data actually come in?

On an average restaurant website, personal information arrives through more channels than you’d expect:

  • Contact and request forms: name, email address and phone number.
  • Job application forms: a CV, a motivation letter and sometimes a date of birth.
  • Newsletter sign-ups: an email address, synced to your email platform.
  • WhatsApp: a phone number and message content.
  • Bookings: a name, contact details, and sometimes allergies or dietary preferences.
  • Analytics and cookies: visitor behaviour, usually managed through a cookie banner.

Legal basis and consent

The same principle applies to every channel: don’t collect more than you need, and ask for consent where required. For a contact and request form, the legal basis is usually straightforward, the guest is asking a question themselves. A newsletter sign-up is different: that’s always opt-in, never a pre-ticked box. For WhatsApp as a contact channel, a phone number already counts as personal data, even if the conversation itself is never logged anywhere else.

Retention periods: how long can you keep it?

One of the most common mistakes is letting data sit around for years without anyone checking it. A few rules of thumb:

  • Handled contact requests: delete or archive them after a few months.
  • Job applications: keep a rejected application for a maximum of four weeks, unless the candidate agrees to longer.
  • WhatsApp conversations: clear out handled chats periodically, just like a regular inbox.
  • Newsletter addresses: remove them as soon as someone unsubscribes, not at the next clean-up round.

A privacy policy that actually holds up

Every restaurant website with forms, cookies or a newsletter needs a privacy policy. At minimum, it should cover: what data you collect, why, how long you keep it, and who guests can contact with questions or a complaint. Place the link in your footer so it’s reachable from every page.

Data processing agreements with your tools

The moment you share data with an external platform, you’re entering into a data processing agreement with them: think of your booking system, your approach to email marketing, and a cookie banner for analytics. Most larger providers offer this agreement by default through their dashboard, just ask if you can’t find it right away.

Getting GDPR in order: a step-by-step plan

  1. Map out which forms, channels and integrations collect data.
  2. Set a retention period per channel, and actually stick to it.
  3. Put together an up-to-date privacy policy, linkable from your footer.
  4. Request data processing agreements from the tools that process data on your behalf.
  5. Launch a cookie banner that only tracks after consent.
  6. Assign someone on your team to handle privacy questions and complaints.

If something does go wrong

If a list of email addresses or job application data accidentally ends up in the wrong hands, that’s a data breach. Serious breaches need to be reported to your national data protection authority, typically within 72 hours. Document smaller incidents internally too, even if you don’t report them, it shows you take privacy seriously if you’re ever audited.

Want to make sure your forms, cookies and data are properly in order? Try Sitebite for free and build your website with privacy as a starting point, not an afterthought.