We are the controller of the personal data described here. That means we decide why and how it is used, and we are responsible for it.
Write to us about anything in this notice at hello@tablestial.com. A person reads every message.
We have not appointed a data protection officer. Our contact address above handles every privacy question.
This notice covers:
- this website and its forms;
- the interactive demos on it;
- the emails we send to restaurant companies about our service;
- our records of restaurants, their contacts and our clients;
- the website and booking service we provide to client restaurants.
If you booked a table at a restaurant that uses our booking service, the restaurant decides how your booking details are used. We handle them only on the restaurant's instructions, under a data processing agreement (we are its processor). Please read that restaurant's own privacy notice, and send any request about your booking to the restaurant.
The demos on this site run on made-up data. A booking made in the demo never reaches a restaurant. Anything you type into the demo booking room or the demo back office can be seen by other visitors until the demo is reset, which happens from time to time. Please use made-up details there.
Each row is one thing we do. Where a row relies on legitimate interests (Article 6(1)(f) of the GDPR), the row names the interest. For people in the United Kingdom the same articles of the UK GDPR apply.
| What we do | Why | Legal basis | What data | Where it comes from | How long we keep it | Who receives it |
|---|---|---|---|---|---|---|
| Walkthrough and contact requests, and a breakdown you ask for at the end of a calculator | To arrange the walkthrough you asked for, send the calculator breakdown you asked for, answer you, and follow up about it | Steps you asked for before a possible contract (Art. 6(1)(b)). After that, legitimate interests (Art. 6(1)(f)): following up on a request you made, and keeping a record of what we discussed | Restaurant name, your name and email. If you add them: phone, postcode or city, covers on a busy night, your message. If you ask for a breakdown at the end of a calculator: the figures you typed into the calculator, the plan you picked and which calculator it was, sent with your request. The calculator itself runs in your browser, and nothing you type into it reaches us unless you send that last step. Also the site language, the page you sent the form from (without the rest of its web address), any campaign label in that address, and the version of the form notice you saw | You | 24 months from our last contact with you. If you become a client, the client row below applies instead | Our team. Our hosting and database providers. Our team alert service, which gets only the restaurant name, the city and a link (see "Who receives it") |
| Newsletter | To send you the newsletter you signed up for | Your consent (Art. 6(1)(a)). You can withdraw it at any time | Your email address, when and where you signed up, the wording you agreed to, and when you unsubscribed | You | Until you unsubscribe. After that the address stays on our do-not-contact list, and we keep the record of your sign-up and unsubscribe for 24 months to show what you agreed to | Our team. Our hosting, database and email providers. Our team alert service, which gets no email address (see "Who receives it") |
| Client account and booking service | To set up and run your restaurant website and booking service, give support, send invoices and keep the contract | The contract with you (Art. 6(1)(b)). Accounting law for invoices and accounting records (Art. 6(1)(c)). Legitimate interests (Art. 6(1)(f)) for the staff you name to us: running the service with the people you chose | Names, work email and phone of your contacts. Back office user accounts: name, email, role, a scrambled password (never the password itself), sign-in times. Plan, fees, contract dates, billing status, invoices, your website address, support messages, and the date the data processing agreement was signed | You and your staff | For the contract. Then invoices and similar documents for at least 5 years, and accounting registers for 10 years, as accounting law requires. Other client records for up to 3 years after the contract ends, the time limit for contract claims. Back office accounts are closed when the contract ends | Our team. Our hosting, database and email providers. Professional advisers such as an accountant. Authorities where the law requires it |
| Records of restaurants and contacts | To keep track of the restaurants we have spoken to or may contact, what was said, and who must not be contacted again | Legitimate interests (Art. 6(1)(f)): running our sales in an orderly way, and making sure a "no" is always respected. For clients, the contract (Art. 6(1)(b)) | Restaurant and company name, company number, legal form, website, business phone, business address and city, type of cuisine, rough number of seats, current booking system. For contacts: name, job title, business email, business phone, and a link to a public professional profile where one is published. Notes of calls and emails (we do not copy the text of emails into these records), the stage of any conversation, tasks, and where and when we found the details | You. The restaurant's own website. Companies House. Map listings. A person who recommended you to us | Restaurants and contacts who never answered: 12 months from our last email, or from when we added them if we never emailed. Enquiries: 24 months from our last contact. Clients: as in the client row. Do-not-contact entries: see below | Our team. Our hosting and database providers |
| Emails to restaurant companies | To tell restaurants that may want it about our service | Legitimate interests (Art. 6(1)(f)): finding restaurants that may want a website with table booking built in, and offering it to them | Business email address. Name and job title, only where the restaurant publishes them. Restaurant and company details. Where and when we found the address. The emails we sent and when. Your replies and any request to stop | The restaurant's own website. Companies House. Map listings | 12 months after our last email if you never reply. 24 months from our last contact if you reply. If you ask us to stop, the address goes on our do-not-contact list | Our team. Our email provider. The server that sends our emails and its backup storage. Our team alert service when you reply (see "Who receives it") |
| Do-not-contact list, objections and privacy requests | To act on your choices and requests, and to show that we did | Legal obligation to handle your rights (Art. 6(1)(c), with Articles 12, 17 and 21). Legitimate interests (Art. 6(1)(f)): making sure we never contact you again after you said no | Your email address, or the whole web domain if a business asks for that. The reason and the date. If we erased your other details, we keep only a scrambled, one-way form of the address (a hash), which lets us recognise it but not read it. For requests: a hash of your address, the type of request, dates and the outcome | You, or our own records | Do-not-contact entries: for as long as we send emails to businesses, so that you stay off every future list. The record of an objection you sent through our form: 24 months. Privacy request records: 24 months after we close the request | Our team. Our hosting and database providers. The server that sends our emails, so it never writes to you again |
| Accessibility reports | To look into the problem you report, reply, and fix it | Legitimate interests (Art. 6(1)(f)): making our site and service usable for everyone. Where accessibility law requires us to answer a complaint about our booking service, that legal obligation (Art. 6(1)(c)) | Your email address. Your name, if you give it. The page, what went wrong, and the device or assistive technology you use, if you tell us | You | 24 months from our last reply to you | Our team. Our hosting and database providers |
| Website security logs | To keep the site safe and working, and to stop abuse | Legitimate interests (Art. 6(1)(f)): keeping the site secure and available | IP address, browser type, the time, the page requested and the result | Your browser, through our hosting provider | Kept by our hosting provider for a short time, then deleted | Our hosting provider |
There are no analytics on this site. We do not use analytics tools, advertising cookies, tracking pixels or third-party trackers. We may look at how our pages appear in search results through the search engines' own webmaster tools. Those tools add nothing to our pages and store nothing on your device.
To stop abuse of our forms, the server counts recent requests from each network address for up to 24 hours, in memory only. It does not write the address anywhere.
Most data comes from you, when you fill in a form, sign up, reply to us or become a client.
When we email a restaurant company, we did not get the address from the person who reads it. In that case the details come from public business sources:
- the restaurant's own website, usually its contact page;
- Companies House, the UK register of companies, to check the company's legal form and number;
- map listings, such as the restaurant's Google Maps entry, to find its website.
We never buy lists. We never take personal addresses from social networks, and we do not guess addresses. We record where and when we found each detail.
We share personal data only with the providers and categories of recipient named in this notice, and only what each needs to do its job. A provider that processes data for us does so under a contract that limits what it may do with it. The exception is Telegram, which runs its messaging service on its own terms (see below).
| Recipient | What they do for us | Where the data is | Transfers outside the EU and UK, and the safeguard |
|---|---|---|---|
| Vercel Inc. | Hosts this website and runs the code behind the forms | Our code runs in Vercel's Frankfurt region, Germany | Vercel is a US company. Transfers rely on the standard contractual clauses in Vercel's data processing addendum. For transfers from the United Kingdom the addendum also includes the UK addendum to those clauses issued by the Information Commissioner |
| Telegram | Sends our team short alerts | Telegram's servers. Telegram says it stores the data of accounts opened in the EU or UK in the Netherlands | Telegram Messenger Inc. is located outside the EU, as its own privacy policy says. See below |
What our team alerts contain.
- When you send the walkthrough form and it is saved in our database, the alert holds only the restaurant name, the city and a link to our records. No name, email or phone.
- A newsletter sign-up alert holds no email address.
- If our database cannot be reached when you send the walkthrough form, the full request goes to our team as a private Telegram message instead, so that a request you asked us to act on is not lost. Telegram's group companies are in the British Virgin Islands and Dubai, countries without an EU adequacy decision. We use this fallback only for the walkthrough form, only when the database fails, and only because it is needed to act on the request you made (GDPR Article 49(1)(b)). If you prefer, email hello@tablestial.com instead of using the form.
- For the newsletter sign-up, the form to stop our emails and the accessibility report form, nothing goes to Telegram if our database cannot be reached. The form tells you so, and you can email hello@tablestial.com instead.
- When you reply to one of our emails, our team gets an alert with your email address and restaurant name. It does not include the text of your reply.
We may also share data when the law requires it, for example with a tax authority or a court, and with professional advisers such as an accountant or a lawyer, who must keep it confidential.
We never sell personal data, and we never share it for anyone else's marketing.
Some of our providers are companies based in the United States, and our team alerts pass through Telegram, whose operator is located outside the EU. The table above lists each transfer and its safeguard. Write to hello@tablestial.com for a copy of a safeguard.
| Data | How long |
|---|---|
| Walkthrough, contact and calculator breakdown requests | 24 months from our last contact with you |
| Newsletter sign-up | Until you unsubscribe. The record of the sign-up and the unsubscribe: 24 months after you unsubscribe |
| Restaurants and contacts who never answered our emails | 12 months from our last email, or from when we added them if we never emailed |
| Contacts who replied to us | 24 months from our last contact |
| Client records | For the contract, then up to 3 years. Invoices and similar documents at least 5 years, accounting registers 10 years, as accounting law requires |
| Do-not-contact list | For as long as we email businesses, so that you are never contacted again. If your other details were erased, only a hash of the address |
| Objections sent through our form | 24 months. The do-not-contact entry stays |
| Privacy requests | 24 months after we close the request |
| Accessibility reports | 24 months from our last reply |
| Website security logs | A short time, set by our hosting provider |
| Demo entries | Until the demo is next reset |
| Our staff's change log (which staff member changed which record, by field name only) | 24 months |
We review these records once a month. When a period has ended, we delete the data or, where we must still recognise an address so that we never contact it again, keep only its hash. Because the review runs monthly, data can stay for up to a month after its period ends.
You can ask us to:
- see the personal data we hold about you and get a copy (access);
- correct data that is wrong or incomplete (rectification);
- delete your data (erasure). We then keep only a hash of your email address on our do-not-contact list, so that you are not contacted again by mistake;
- pause our use of your data while a question is settled (restriction);
- receive data you gave us in a common machine-readable format, or have it sent to another company (portability), where we use it on the basis of your consent or a contract;
- object to our use of your data based on legitimate interests. We then stop, unless we have strong legitimate grounds that override your interests, or we need the data for a legal claim;
- stop marketing. If you object to our emails or any other direct marketing, we stop. This right is absolute;
- withdraw consent at any time, for example by unsubscribing from the newsletter. This does not affect what we did before you withdrew.
Every newsletter email has an unsubscribe link that works without logging in and never expires, and a mail app's own unsubscribe button works the same way; it stops the newsletter and leaves anything else you asked us for alone.
To use any of these rights, email hello@tablestial.com or reply to any of our emails. To stop our emails only, you can also use the form on our page How we found you. It is free. We answer within one month. If a request is complex, we may take up to two more months, and we will tell you why within the first month. We may ask for information to confirm who you are before we act.
Please tell us first at hello@tablestial.com, so that we can put it right.
You can also complain to a data protection authority, for example where you live or work:
- Latvia: Data State Inspectorate (Datu valsts inspekcija), Elijas iela 17, Rīga, LV-1050, pasts@dvi.gov.lv, www.dvi.gov.lv. It is the authority that supervises us.
- United Kingdom: Information Commissioner's Office (ICO), ico.org.uk.
- Elsewhere in the EU: your national data protection authority.
We make no decisions about you by automated means alone that have legal or similarly significant effects.
Our records do run automatic checks before any email goes out. They stop emails to people we must not contact: sole traders, partnerships in England, Wales and Northern Ireland, personal email addresses, anyone on the do-not-contact list, and details that are too old. These checks can only stop an email. They never decide anything else about you.
This site stores only what is strictly necessary, or what you ask it to remember, such as your choice to pause animations. There is no cookie banner because there is nothing optional to agree to. Our cookie policy lists every item.
- Everything travels over an encrypted connection (HTTPS).
- Our records sit in a database that only named staff can open. Each person signs in with their own account, and each has only the access their role needs.
- Passwords are stored only in scrambled form.
- We log which staff member changed which record, by field name only, never the values.
- Our email server keeps the passwords of its mailboxes encrypted.
If a breach puts your personal data at risk, we will tell the supervisory authority within 72 hours where the law requires it, and we will tell you without undue delay if the risk to you is high.
Our site and service are for restaurant businesses. They are not meant for children, and we do not knowingly collect data from anyone under 16. If you think a child has sent us personal data, tell us and we will delete it.
When we change this notice, we publish the new version here with a new version number and date, and list the change below. If a change affects how we use data you already gave us, we will tell you before it applies, where we have a way to reach you.
| Version | Date | What changed |
|---|---|---|
| 1.0 | 1 November 2026 | New notice. Replaces the policy of September 2026. Adds one row per activity, our emails to restaurant companies and where their details come from, a retention table, the full list of rights, and how to complain to a data protection authority |
Email hello@tablestial.com.