Privacy policy
Tabula is an online table-booking service that restaurants add to their own websites. This policy explains what personal data is handled when you book a table through Tabula, or when you use the Tabula admin panel as restaurant staff, and what your rights are.
Who is responsible for your data
When you book a table, the restaurant you are booking with is the data controller: it decides why your details are collected and is your first point of contact for questions about your booking. Tabula processes that data on the restaurant's behalf as its processor. For the accounts of restaurant staff who use the admin panel, Dynasoft Business Solutions Ltd is the controller.
Tabula is a service of Dynasoft Business Solutions Ltd, a company registered in England and Wales (company number 11830527) whose registered office is at 17 Green Lanes, London, England, N16 9BS. Contact: [email protected].
What we collect when you book
- Booking details: date, time, party size, chosen area, occasion and any requests you type in.
- Contact details: your name, email address and, if you give it, phone number. They are used to verify the booking with a one-time code, to send the confirmation, reminders and any changes, and so the restaurant can contact you about your booking.
- Technical data: the IP address and browser type of the request, kept in short-lived logs to prevent abuse and keep the service working.
- Marketing consent: only if you tick the unticked box offered by some restaurants; the time and place you ticked it are recorded so it can be proven and withdrawn.
We do not take payment card details unless a restaurant has switched on deposits; in that case your card is handled directly by Stripe and Tabula never sees the card number.
Bookings that start on Google. If you reach a restaurant's booking page from Google (for example from its listing on Google Maps or Search), you book on Tabula as usual and we note that the booking came from Google. Where a restaurant takes bookings inside Google itself, Google collects your name and contact details under its own privacy policy and passes them to us, with your marketing choice, to make the booking; from then on we handle them as this policy describes.
Why we are allowed to use it
- Taking and managing your booking: necessary to perform the booking agreement between you and the restaurant.
- Verification codes, fraud and abuse prevention, security logs: our legitimate interest in running a reliable and safe service.
- Marketing messages from the restaurant: your consent, which you can withdraw at any time from any message or by telling the restaurant.
Who else sees it
Tabula uses a small number of service providers to run the service. Each only receives what is needed for its job and is bound by contract to protect it.
| Provider | What for | Where |
|---|---|---|
| Hetzner Online GmbH | The servers and database that run Tabula | Germany (EU) |
| Cloudflare, Inc. | Delivering the booking widget and admin panel, protecting against attacks, encrypted backups | Global network; EU and UK data centres |
| Resend, Inc. | Sending emails (codes, confirmations, reminders) | EU (Ireland) region |
| Twilio Inc. | Sending text messages, only for restaurants that enable SMS codes | EU/US |
| Google LLC | Restaurant address and opening-hours lookup when a restaurant sets up its account; map links in confirmations; for restaurants listed on Google, their booking link and available times, and the bookings guests make there | Global |
| Stripe, Inc. | Card deposits, only for restaurants that enable them | EU/US |
Where a provider is outside the UK or EEA, transfers rely on the UK International Data Transfer Addendum or EU Standard Contractual Clauses. We never sell personal data.
How long we keep it
- Bookings and guest details stay with the restaurant's records so it can manage visits and honour cancellations. A guest's details are anonymised after 24 months without a booking, unless the restaurant has set a different period.
- One-time codes expire after 10 minutes and are stored hashed. Manage-booking links expire 30 days after the visit.
- Security and access logs are kept for up to 30 days; the audit trail of changes to a booking for 2 years.
Your rights
Under UK and EU data-protection law you can ask for a copy of your data, have it corrected or deleted, object to or restrict its use, and withdraw consent to marketing. For data about a booking, contact the restaurant, or email [email protected] and we will pass the request on and help. You can also complain to the Information Commissioner's Office (ico.org.uk) or your local supervisory authority.
Cookies and storage
The booking widget sets no cookies and does no tracking. If you choose "remember this device", a token is stored in your browser so you can skip the code next time; it expires after 90 days and you can clear it by clearing site data. The admin panel uses one strictly necessary session cookie to keep staff signed in.
Restaurant staff accounts
Staff sign in with an email address and password or with a Google, Apple or Microsoft account. We store the name and email the provider shares, the restaurants you belong to, your authenticator setup if you enable it, and a log of sign-ins. Accounts are deleted on request.
Changes
We will update this page when the service changes and show the date at the top.