Privacy policy
On this page
- 1. Who we are
- 2. Our two roles
- 3. If you book a table at a restaurant
- 4. Our booking widget on restaurant websites (including the WordPress plugin)
- 5. Website statistics
- 6. If you are a restaurant or a member of its staff
- 7. If you visit mytable.pro
- 8. Service providers (sub-processors)
- 9. Security
- 10. How long we keep data
- 11. Your rights
- 12. Changes
- Demo requests through this website
This policy explains what personal data myTable.pro handles, why, and what your rights are. It covers visitors of mytable.pro, the restaurants that use our service and their staff, and the guests who book through a restaurant that uses myTable.pro.
1. Who we are
myTable.pro is operated by Kirepo sàrl, a société à responsabilité limitée (sàrl) registered in Luxembourg under number B103574, VAT number LU20341752, with its registered office at 1 Rue de Wormeldange-Haut, 5488 Ehnen, Luxembourg.
Privacy questions: privacy@kirepo.lu. General contact: moien@mytable.pro · +352 20 21 00 55.
2. Our two roles
- For guests of a restaurant, the restaurant is the controller. It decides what it does with your booking. We process your data on its behalf, as its processor, under a data processing agreement (see Terms, section 8). To use your rights, contact the restaurant first; we will help it answer.
- For restaurants, their staff, and visitors of mytable.pro, we are the controller.
3. If you book a table at a restaurant
When you book through a restaurant's website, booking page, phone or chat agent, or in person, the restaurant may record:
- your name, email address and phone number;
- the date, time and size of your party;
- notes and allergies you or the staff type;
- your booking history at that restaurant (visits, cancellations, no-shows);
- your answers to a feedback survey, if you reply to one;
- the messages sent to you and whether they were delivered.
This data is used to take and manage your booking, send you a confirmation and reminders by email or SMS, let you change or cancel, prepare your visit, and ask for your feedback. Each restaurant sees only its own guests. We do not sell guest data and do not use it to market our own services.
If you add a booking to Apple Wallet, a pass with your booking details is created and signed through Apple, and Apple may send updates to your device when the booking changes.
If you book through the restaurant's phone or chat agent, what you say or type is processed to understand your request and make the booking. Calls are not recorded, and no transcript is kept: only the booking itself is saved.
You can ask the restaurant to show, correct or erase your data. The restaurant has an erasure tool in our staff app for this.
4. Our booking widget on restaurant websites (including the WordPress plugin)
A restaurant can add our booking widget to its own website, by a code snippet or by our WordPress plugin. Once the restaurant has set its key:
- the website loads our script from
widget.mytable.proon every page; - the widget loads the restaurant's settings and free times from
api.mytable.pro, and sends the address of the page and the restaurant's key with that request; - like any web request, this reaches our servers with your IP address and browser details;
- when you make a booking, the widget sends what you type in the form: name, contact details, party size, date and time, and any note (see section 3).
The widget may store your contact details in your browser, only to prefill your next booking at that restaurant. You can clear them by clearing your browser's site data.
The widget sets no cookies. If the restaurant uses website statistics, see section 5; with the WordPress plugin, a cookie banner that supports the WP Consent API passes your statistics choice to the widget.
The WordPress plugin does nothing until the restaurant sets its key. Its settings page then asks api.mytable.pro, from the restaurant's own server, whether the key is known and how the form is set to show; only the key is sent.
The restaurant decides whether to use the widget and is responsible for informing its website visitors.
5. Website statistics
A restaurant can turn on our website statistics, which count visits to its website. They work without cookies:
- your IP address is used only to work out your country and a hash that is salted and changes every day. The IP address itself is not stored;
- the country lookup runs on our own servers with a local MaxMind GeoLite2 database. Your IP address is not sent to MaxMind;
- only if you accept statistics in the restaurant's cookie banner, a random identifier is stored in your browser (localStorage), so that a return visit can be recognised. If you withdraw that consent, the identifier is erased.
6. If you are a restaurant or a member of its staff
We process:
- the restaurant's business and billing details, and its contact person;
- staff names, email addresses, roles, login details and PINs;
- a log of important actions in the staff app (who did what, and when), for security and so the restaurant can follow up;
- emails we send you about your account, such as a daily recap, and your support requests.
Legal bases: performing the contract with the restaurant (Art. 6(1)(b) GDPR), our legal obligations such as accounting (Art. 6(1)(c)), and our legitimate interest in running a secure service and supporting you (Art. 6(1)(f)).
7. If you visit mytable.pro
- mytable.pro uses no cookies, no advertising trackers and no third-party analytics.
- Your browser may keep your choice of light or dark theme and of video caption language (localStorage). This stays on your device.
- Our web server receives your IP address and browser details to deliver the pages. Server logs are kept for at most 30 days, to run and protect the service.
- The font of this website (Elza Text) is loaded from Adobe Fonts, a service of Adobe. When your browser loads it, Adobe receives your IP address, and Adobe counts the page view to bill the font licence.
- If you book a demo or write to us, your email program sends us your message. We use it to answer you and, if you become a customer, to set up your account (legitimate interest, or steps before a contract).
8. Service providers (sub-processors)
We use these providers to run the service.
- Hetzner — hosting of the service and its data, Germany.
- Mailgun — sending emails, EU region.
- seven.io — sending SMS, Germany.
- Apple — signing and updating Apple Wallet passes, only when a guest adds a pass.
- Backups — encrypted, stored on a separate Hetzner server in Germany.
The MaxMind GeoLite2 database runs on our own servers; MaxMind receives no personal data. Each provider is bound by a data processing agreement. If any provider transfers data outside the EU/EEA, appropriate safeguards under the GDPR apply, such as the European Commission's standard contractual clauses.
9. Security
Connections are encrypted (HTTPS). Each restaurant's data is kept apart from the others. Staff access depends on their role. Backups are encrypted. Only the people at our side who need access to run and support the service have it, and they are bound to confidentiality.
10. How long we keep data
- Guest data is kept while the restaurant's account is active and as the restaurant configures it. When the contract ends, it is deleted or anonymised within 90 days. Erased guests are anonymised at once. Some details are removed sooner, automatically: allergy and health notes 7 days after the visit, and names typed on a booking without a guest record after 3 months. Raw website-statistics visits are kept for 13 months, then only as totals.
- Restaurant and staff account data is kept for the duration of the contract and then deleted within 90 days, except invoices and accounting records, which we keep as long as the law requires.
- Backups are overwritten on a rolling basis within 12 months: daily copies for 30 days, monthly copies for 12 months.
11. Your rights
Under the GDPR you can ask for access to your data, correction, erasure, restriction, a copy in a portable format, and you can object to processing based on legitimate interest. Where processing is based on consent, you can withdraw it at any time.
If you are a guest, ask the restaurant first. If you write to us, we pass your request to the restaurant and help it answer. For anything where we are the controller, write to privacy@kirepo.lu. We answer within one month.
You can also complain to the Luxembourg data protection authority, the Commission nationale pour la protection des données (CNPD), or to the authority in your own EU country.
12. Changes
We may update this policy when the service or the law changes. The current version is always on this page. Restaurants are told by email about important changes.
Last updated: 21 November 2026
Demo requests through this website
This section explains what happens with the information you give us when you ask for a demo on this website.
Step 1: how we can reach you
The demo request form first asks for a phone number or an e-mail address, in one field. That is its only required entry; everything else, including your name and your restaurant, is optional. We use your contact details only to answer your request.
Step 2: a few optional questions
Once step 1 is sent, your request is saved. The form then asks a few more questions. All of them are optional, and you can skip them:
- how your restaurant takes bookings today, including the name of the system you use now (Zenchef, TheFork or other software), or that you use no software;
- the approximate number of seats;
- the name of your restaurant;
- when it suits you best for us to call (morning, afternoon or evening);
- your first name.
Sent automatically with your request
- The campaign tags of your visit, if the link you followed carried them (utm_source, utm_medium, utm_campaign).
- The website that referred you to this site, as its address and path only (never its query).
- The page you first landed on in this site, the page you sent the request from, its language, and the plan if you came from one. If you came from a price button, the request is marked as a price request.
- A request number, so that a request sent twice is stored once.
Only if you agree, the campaign tags, the referring website and the landing page are noted in your browser's session storage for this tab only, not in a cookie. The site asks first, in a small box at the bottom of the page ("May we note how you found us?"; in German "Dürfen wir uns merken, wie du zu uns gefunden hast?"). Before you answer, and if you say no, nothing is noted. Nothing of it leaves your browser unless you send a request, and your browser deletes it when you close the tab. If you send a request without having agreed, it carries only the campaign tags and the referring website of the page you send it from, read at that moment and not kept in your browser, and that page counts as the landing page. You can change your answer at any time with "Privacy settings" ("Datenschutz-Einstellungen") at the bottom of every page; if you take your agreement back, what was noted is deleted at once. Noting this in your browser is based on your consent (Article 4(3)(e) of the Luxembourg law of 30 May 2005 on privacy in electronic communications).
Protection against automated requests
- Technical data on our side: the time we received the request, the browser identification (user agent) and a salted hash of your IP address. The IP address itself is not stored with the request.
- The form has a field that people do not see, and the page notes when it was loaded. A request with that field filled in, or sent within a few seconds of loading the page, is treated as automated: it is neither stored nor passed on.
- To limit repeated requests, the server counts requests per IP address in its memory for ten minutes. This count is not stored.
Why we use it
We use this information to contact you about a demo and to follow up on it, and to understand which restaurants ask for one (internal reporting). Legal basis: steps taken at your request before entering into a contract (Art. 6(1)(b) GDPR), and our legitimate interest in answering enquiries and understanding where they come from (Art. 6(1)(f)).
Who receives it
- The request is stored on our server.
- It is sent to our team by e-mail and to our customer management system (CRM) through a direct, signed connection (a webhook).
- If you gave an e-mail address, a confirmation e-mail is sent to it. It says that we received your request and can be ignored by anyone who did not make one.
- We do not pass it to advertising networks or to anyone else for their own purposes.
How long we keep it
We keep this information only for as long as it is needed for these purposes, contacting you about the demo and the follow-up, and then delete it.
Browser storage
- The site sets no cookies.
- Your browser's local storage keeps the caption language you pick for the help videos (it stays on your device).
- Your browser's session storage, for this tab only, keeps what is described above under "Sent automatically with your request" (only if you agreed), and, from sending the form until the thank-you page has opened, your first name and your choice of how you take bookings today, so that the page can greet you. Nothing of it is in a web address.
- Your browser's local storage keeps your answer to the question "May we note how you found us?" (yes or no, the date of your answer and a version number), so that the site does not ask on every page. It asks again after 12 months, or sooner if what it notes changes. This stays on your device.
Hosting
The website is hosted by Hetzner Online GmbH on servers in Germany (EU).