Last updated: July 8, 2026
This policy explains how TableStack handles personal data for two groups: restaurant staff who use the platform, and diners whose details a restaurant stores when they book or visit. For diner data, the restaurant is the data controller and we are its processor — the restaurant decides what is collected and why.
Staff accounts: name, email, password (hashed), role, and an activity log of actions taken in the app. Diners: the details given when booking or joining a waitlist — name, phone, email, party size, occasion — plus what the restaurant records in its guest book: visit history, seating preferences, allergies, notes, and marketing opt-ins. Allergy data exists to keep guests safe and is shown to staff during service.
To run reservations end to end: confirmations, 24-hour and 2-hour reminders, table-ready alerts (email and, where a phone number was provided, SMS), floor management, and the restaurant's own guest analytics. Marketing messages are only sent by restaurants to guests who opted in. We do not sell personal data, and we do not use guest data to train AI models.
Where a restaurant enables them, AI features summarize a guest's own history for hosts, estimate no-show risk, and suggest tables. Requests are processed by our AI provider under contract, scoped to the requesting restaurant's data, and the output is advisory — never an automated decision with legal effect.
Subprocessors that make the service work: our hosting provider, Stripe (billing), our email delivery provider, an SMS provider (Twilio or Vonage) for text alerts, Meilisearch (guest search, self-hosted), and our AI provider for the features above. Each is bound by a data-processing agreement. Within the platform, guest records are shared only across venues of the same restaurant group — never with other organizations.
Diners can ask a restaurant for a copy of their data or for erasure; the platform gives restaurants one-click export and anonymization tools to answer those requests. Anonymization removes everything identifying (name, contact details, notes, allergies) while keeping anonymous visit counts so the restaurant's statistics stay truthful. Staff can request their account data via their organization's owner.
Data is kept while the restaurant's account is active, then deleted or anonymized within 30 days of closure. Everything is encrypted in transit; passwords are hashed; access inside a restaurant is role-based per venue and every sensitive action is written to an audit trail.
We use only the cookies the app needs to work: a session cookie and a CSRF token. The public booking page works without an account and sets no tracking cookies. Booking-management links are signed URLs sent to your email or phone.
Privacy questions about a specific restaurant's guest book should go to that restaurant. For questions about the platform itself, contact the TableStack team through your account owner's support channel.