Security & data protection
Your guest book is some of the most sensitive data a restaurant holds — names, contact details, allergies, visit history. Here is exactly how TableStack protects it.
Tenant isolation by design
Every record belongs to one organization, and every query is scoped to it at the framework level. One restaurant group can never read another's guests, reservations, or reports — the isolation is enforced in code and covered by automated tests on every release.
Encrypted in transit
All traffic — the app, the booking pages, the API, and real-time updates — runs over HTTPS/TLS. Guest-facing manage-booking links are cryptographically signed and expire, so a link can't be guessed or reused indefinitely.
Passwords and API access
Staff passwords are stored only as one-way bcrypt hashes. API access uses per-user tokens with scoped abilities, so an integration gets exactly the permissions it needs and nothing more.
Two-factor auth and passkeys
Every account can add two-factor authentication with an authenticator app and one-time recovery codes, or sign in with a passkey — Face ID, Touch ID or a hardware key — with no password to phish. Sensitive settings ask again before they open.
Data hosted in Canada
Your guest book, reservations and floor plans live on servers in Beauharnois, Québec (OVHcloud Canada) — they never leave the country. Guest-facing pages and emails run in English and French.
Role-based access, per venue
Permissions are granted per venue. A host at one location doesn't see another location's floor; managers control who can view guest profiles, change settings, or issue refunds. Owner access is explicit, not the default.
A full audit trail
Every state change — a seated table, a cancelled booking, an edited guest record, a settings change — is written to an activity log with who did it and when. Nothing important happens silently.
Guest privacy rights built in
Guests can request an export of their data or ask to be forgotten. Anonymization removes personal details while preserving the venue's anonymous visit analytics — you stay compliant without losing your numbers.
Card data never touches us
Billing and large-party deposits run on Stripe. Card numbers are entered on Stripe's PCI-compliant infrastructure and never pass through or get stored on TableStack servers.
AI features stay inside your walls
Optional AI features (guest briefings, no-show risk, table suggestions) are advisory only, run asynchronously, and only ever see data belonging to your own organization. They never act on their own.
Found a vulnerability, or have a security question before rolling TableStack out to your group? We want to hear it.