Privacy notice — Slotina
Last updated: 4 November 2026
This notice explains what personal data we process when you visit slotina.io, join the Slotina early-access list, use the Slotina service at app.slotina.io or in the Slotina app for iOS and Android, or book, order or pay at a restaurant that uses Slotina. It explains why we process the data, who receives it and what rights you have. It is written for the UK General Data Protection Regulation (UK GDPR) and the EU General Data Protection Regulation (GDPR).
1. Who we are
Slotina is a product of Belavin Limited, a private company limited by shares registered in England and Wales with Companies House under number 16735157, registered office: 6 Salstar Close, Birmingham, B6 4PP, United Kingdom. Slotina is run separately from Belavin Limited's other products: it has its own website, its own application and its own database.
We are registered with the UK Information Commissioner's Office (ICO) under registration number 00014129250.
Contact for all privacy matters: hello@slotina.io.
Our representative in the European Union (Article 27 GDPR). Because we have no establishment in the EU, we have appointed Prighter EU Rep GmbH, Schellinggasse 3/10, 1010 Vienna, Austria, as our representative, both as controller and as processor. You can also contact our representative, or exercise your data protection rights through it, on Prighter's page for us: https://app.prighter.com/portal/18703347489.
2. Our two roles
We are the controller of the data we process for our own purposes: when you visit slotina.io, join the early-access list or write to us, and for the accounts of the restaurants, cafés, bars and other venues that use Slotina (the "venues") and their team members, including subscription and billing.
We are a processor for the data a venue keeps about its own guests: reservations, waiting-list entries, pre-orders, event tickets, private-dining enquiries, pickup and table orders, payments and the guest book. For that data the venue is the controller. It decides what it asks its guests and what it does with the answers, and we process the data only on its instructions, under our Data Processing Terms with the venue. Section 3.8 describes what this means for you as a guest.
3. What we collect and why
3.1 Visiting slotina.io
When you open a page, your browser necessarily sends technical data to the server that delivers it: your IP address, the date and time, the address requested, the referring page and information about your browser and operating system. Our hosting provider, Netlify, processes this data to deliver the site and to protect it against attacks. We look at it only when we investigate a fault or misuse.
We do not use analytics, advertising pixels, social-media plug-ins or any other tracking technology on slotina.io, and the site sets no cookies (see section 11 and our Cookie Statement).
3.2 The early-access list
If you join the list, we collect:
- What you enter: your e-mail address, your name, the name of your restaurant or venue, its country and city, its approximate size (a seat band: up to 30, 31–60, 61–120 or over 120) and, if you choose to give it, a telephone number;
- What we record with it: the language of the page you used, the page on which you filled in the form, the version of the privacy information shown next to the form, the time you signed up, when we sent the confirmation e-mail, when you confirmed and, later, when we sent you the launch e-mail, and a random code that is used in your confirmation and removal links.
We use this information only to:
- send you one e-mail asking you to confirm that the address is yours and that you want to be on the list (double opt-in);
- write to you once, when Slotina opens in your country;
- answer you if you write to us; and
- plan the launch (for example, which countries and cities to open first).
We send no newsletter and no offers from this list, and we never sell or share the information with anyone for their own purposes.
If you send the form again with the same e-mail address, we update your existing entry instead of creating a second one.
Notifications to our team. When someone joins the list, and when they confirm, our team receives a short internal e-mail with the details entered, so that we can see who is interested. These e-mails go only to our own mailbox.
3.3 Protection against bots and abuse
To keep automated spam out of our forms, the early-access form contains a hidden field that only bots fill in, and we limit how many times a form can be sent from the same e-mail address or connection within a short period. Sign-in, sign-up and the guest forms of app.slotina.io are protected in the same way, by limits on how often they can be used. We use no third-party bot-detection service.
3.4 Your Slotina account (venues and their teams)
If you create an account for a venue, or a venue gives you a login to its team, we process:
- Account data: your name, e-mail address, password (stored only as a one-way hash), your role in the team (for example owner, manager or host), your language, and, if you switch it on, the secret of your two-step sign-in (stored encrypted) and your recovery codes (stored only as hashes). A short PIN for a shared host-stand device is stored only as a hash.
- Venue data: the venue's name, address, country, contact details, opening hours, rooms and tables, menus, prices, photos, policies, settings and, if the venue sets it, its own privacy notice for guests.
- Team data the venue enters: rota shifts, availability, time off, recorded working hours, pay rates and tip allocations. For this data the venue is the controller and we are its processor, as for guest data (section 2).
- Activity log: a record of what was done in the venue's account and by which login (for example, who cancelled a booking), so that the venue can see who did what and we can investigate faults and misuse.
- Technical data: the IP address and device information of sign-ins and requests, security events, and records of how the service is used (for example, which screen an action was taken on). We use these to keep accounts secure, to find and fix faults and to improve the service. We do not use third-party analytics in the service.
We use this data to provide the service under our contract with the venue, to keep it secure, and to send the e-mails an account needs: confirming your address, resetting your password, notices about your subscription and about changes to our terms. We may also send the owner of an account a small number of letters about getting started with Slotina; every such letter tells you how to stop them.
3.5 Subscription and billing
A venue's subscription is bought on the web, never in the app. When the owner adds a card, Stripe's own payment page collects the card details; we never see or store a card number. We keep the Stripe customer and subscription identifiers, the plan, the price, the trial and payment dates, the payment status, the owner's consent to the monthly charge (when and in which version it was given), the venue's billing details and, where given, its VAT number and the result of any check we make on it, and our invoices.
3.6 The Slotina app
The Slotina app for iOS and Android shows the same venue console as app.slotina.io. It is for venue teams; guests do not need it and cannot create accounts in it. The app contains no advertising identifiers and no analytics SDK, and we do not share app data with data brokers.
The app asks for access to device functions only when you use the feature that needs them:
- Notifications: if you allow them, the app registers a push token, stored with your login together with your device platform and language, so that your team's phones and tablets are told about new online bookings, cancellations, waiting-list entries and orders. A notification shows the time, the date and the party size, never a guest's name or telephone number. The token is deleted when you sign out or the account is deleted. Declining notifications changes nothing else in the app.
- Camera and photos: only when you take or choose a picture yourself, for example of a dish, an event or a printed menu. Nothing is captured in the background and we never scan your library.
- Local network and Bluetooth: only to reach a kitchen or receipt printer on your own network.
- Location: only when you take a card payment with Tap to Pay, where your venue has it, because the payment provider requires the device's location to protect against fraud. We do not store your location.
The app does not record audio.
Crash reports. If the app crashes, it may send a crash report to Google Firebase Crashlytics: the app version, the device model and operating system, and the technical error with personal data removed. It contains no user identifier. You can switch crash reports off in the app's settings.
3.7 The help assistant and support requests
The console has a help chat. It answers from our help articles and from your venue's settings. If an AI model is used to write the answer, the model receives your question (with any e-mail addresses and telephone numbers in it replaced), up to three help articles and your venue's settings. It never receives guest data: no reservation, guest, message or payment is read for this. The model provider does not use the data to train its models. We keep only a usage record (when an answer was produced and how large it was), not the question or the answer.
If the matter is serious, if the chat cannot answer, or if you ask for a person, your question, your login's e-mail address and the venue it concerns are stored as a support request and sent to our team, who reply by e-mail.
3.8 Guests of venues that use Slotina
If you book a table, join a waiting list, buy an event ticket, send a private-dining enquiry, pre-order, order for pickup or at your table, or pay a deposit at a venue that uses Slotina, the venue is the controller of your data and we process it on its behalf. The venue's privacy notice, linked from every form, tells you how it uses your data; where the venue has not published its own, the form links to this notice.
Depending on what the venue asks, the data can include: your name, e-mail address and telephone number; the date, time and size of your booking; the occasion and your notes; allergies, dietary requirements and accessibility needs; your pre-order; the names and dietary answers of the people on your event tickets; your order and payment status; the messages the venue sends you; and whether you asked not to receive messages. Information about allergies, diet or health can be special-category data (Article 9 GDPR); the venue asks for it so that it can serve you safely, and we only store it and show it to the venue's team on the venue's instructions.
Each venue's guest data is kept separately. We do not combine one venue's guests with another's, we do not use guest data for our own marketing, we do not sell it, and we do not send it to any AI model. Messages to guests are sent in the venue's name; every message contains a link with which you can stop further messages that are not strictly about your booking.
Payments to a venue go to the venue's own account at Stripe. Stripe's payment page collects your card details; we pass Stripe only your e-mail address and the amount, and we never see or store your card number. Stripe processes your payment under its own terms with the venue.
To exercise your rights over this data, please contact the venue. If you write to us instead, we will pass your request to the venue without delay, provided we can tell which venue it concerns, and help the venue to answer it.
3.9 When you write to us
If you write to hello@slotina.io or reply to one of our e-mails, we process your e-mail address, your name if you give it, and the content of your message in order to answer you.
4. Legal bases
| Processing | Legal basis (UK GDPR and GDPR) |
|---|---|
| Early-access list: the confirmation e-mail, the one launch e-mail and keeping your entry until then (section 3.2) | Your consent, confirmed by double opt-in — Article 6(1)(a). You can withdraw it at any time with the link in any of our e-mails |
| Launch planning from the list and internal notifications to our team (section 3.2) | Our legitimate interest in preparing the launch and responding promptly to interested businesses — Article 6(1)(f) |
| Delivering the website and the service, server logs, protection against bots and abuse (sections 3.1, 3.3 and 3.4) | Our legitimate interest in operating a secure and stable service — Article 6(1)(f) |
| The venue's account, the service and the e-mails an account needs (sections 3.4 to 3.7) | Performance of our contract with the venue — Article 6(1)(b). For team members who are not themselves party to that contract: the legitimate interest of the venue and of us in giving the team access — Article 6(1)(f) |
| Activity log, usage records, crash reports, letters about getting started (sections 3.4 and 3.6) | Our legitimate interest in security, in fixing faults, in improving the service and in helping customers use it — Article 6(1)(f) |
| Push notifications (section 3.6) | Your permission on the device, and the performance of the contract — Article 6(1)(b) |
| Billing records and invoices (section 3.5) | Legal obligation (tax and accounting law) — Article 6(1)(c) |
| Guest data and team data the venue enters (sections 3.4 and 3.8) | We process it as the venue's processor (Article 28 GDPR). The legal basis is the venue's, and its own notice states it; for allergy, dietary or health information, normally your explicit consent — Article 9(2)(a) |
| Answering your messages (section 3.9) | Article 6(1)(b) where your message concerns a contract with us; otherwise our legitimate interest in answering enquiries — Article 6(1)(f) |
| Keeping or disclosing data where the law requires it | Legal obligation — Article 6(1)(c) |
Giving us your details is voluntary. Without an e-mail address, a name, the venue, its country, city and size, we cannot put you on the early-access list; the telephone number is optional. Without an e-mail address and a password, we cannot open an account.
5. The e-mails we send
- From the early-access list: the confirmation e-mail repeats what you entered and asks you to confirm. If you do not confirm, we delete the entry after 30 days and do not write again. The launch e-mail is sent once, only to confirmed entries, when Slotina opens in your country. Every e-mail from this list contains a link that deletes your entry immediately.
- To account holders: e-mails about your account, your subscription and changes to our terms, and a small number of letters about getting started, which you can stop.
- To guests, in the venue's name: confirmations, reminders and other messages the venue has switched on (section 3.8).
Our e-mails are sent from no-reply@slotina.io; replies go to hello@slotina.io. They contain no tracking images, and we do not record whether you opened them. Our e-mail provider tells us whether an e-mail was delivered or bounced, and we stop writing to an address that bounces or complains.
6. Recipients and processors
We use the following service providers, who process data on our behalf under a data-processing agreement — in most cases the provider's standard terms — and only as needed to run the website and the service:
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Netlify, Inc., 101 2nd Street, San Francisco, CA 94105, USA | Hosting of slotina.io and app.slotina.io; storage of the early-access list and of uploaded pictures (Netlify Blobs) | All data described in section 3 while it is delivered; the early-access list; pictures | USA (global network) |
| Neon, Inc., USA | Hosting of the Slotina database | All account, venue and guest data of the service | Database in London, United Kingdom |
| Plus Five Five, Inc. ("Resend"), 2261 Market Street #5039, San Francisco, CA 94114, USA | Sending e-mails (early-access list, account e-mails, e-mails to guests in the venue's name, internal notifications) | E-mail address, name, the content of the e-mail; whether it was delivered or bounced | USA |
| Stripe (Stripe Payments Europe, Limited, Ireland; Stripe Payments UK, Ltd., United Kingdom; Stripe, Inc., USA — depending on the country) | Our subscription billing; payments that guests make to a venue's own Stripe account | For billing: the owner's e-mail address, the card (held by Stripe only), amounts. For guest payments: the guest's e-mail address, the card (held by Stripe only), amounts | EU and USA |
| Google (Firebase Cloud Messaging and Firebase Crashlytics) | Push notifications to the venue team's devices; crash reports from the app | Push token, device platform and language, notification content (no guest name or telephone number); crash reports without user identifiers | USA |
| Google (Gemini API) | Writing answers in the help chat (section 3.7) | The question (with e-mail addresses and telephone numbers replaced), help articles, the venue's settings; never guest data; not used to train models | USA |
| [Name of our mailbox provider for hello@slotina.io] | Receiving and storing e-mails sent to us, internal notifications and support requests | Your messages, our internal notifications, support requests | [to be completed] |
Stripe also acts as a controller in its own right where the law requires it, for example to prevent fraud and to meet its obligations as a payment institution; its own privacy notice applies to that.
Apart from these providers, we disclose data only where we are legally required to do so. If a public authority asks us for data, we check that the request is lawful and binding, challenge it where it is not, disclose only the minimum it requires, and document it. Where the data is a venue's guest data, we tell the venue unless the law forbids it.
7. International transfers
We are based in the United Kingdom, and the Slotina database is in London. For people in the European Union, the United Kingdom is covered by an adequacy decision of the European Commission (Article 45 GDPR).
Netlify, Resend, Stripe, Google and Neon are based in, or may process data in, the United States. These transfers rely on:
- the provider's certification under the EU-U.S. Data Privacy Framework (European Commission adequacy decision of 10 July 2023) and, for data from the United Kingdom, the UK Extension to it (UK data bridge); and
- in addition, where the provider's terms include them, the European Commission's Standard Contractual Clauses (Article 46(2)(c) GDPR) together with the UK Addendum issued by the ICO.
You can ask us for a copy of the relevant safeguards at hello@slotina.io.
8. How long we keep data
| Data | Retention |
|---|---|
| An early-access entry that is not confirmed | Deleted 30 days after sign-up |
| A confirmed early-access entry | Until you delete it with the link in any of our e-mails or ask us to, and at the latest 18 months after sign-up |
| Our internal notification e-mails about an early-access entry | Deleted no later than the entry itself |
| Your messages to us and our replies | Until your enquiry is resolved, then for as long as needed to deal with any follow-up, at most 12 months, unless the law requires longer |
| A venue's account and its data, including its guest data | For as long as the account exists. After a subscription ends, the venue keeps access for 90 days to read and export its data. When the owner deletes the account, the data is erased at once; what is kept after that, and for how long, is set out on our account-deletion page |
| A team member's login | Until the venue removes it or the account is deleted |
| Activity log of a venue's account | 2 years |
| Pickup orders: the guest's name, contact details and notes | Removed 90 days after the pickup time |
| Support requests from the help chat | 365 days |
| Push tokens | Until you sign out or the account is deleted |
| Billing records and invoices | 6 years from the end of the financial year to which they relate (UK tax law) |
| Security and technical records (sign-in links, password-reset codes, rate-limit counters) | Up to 90 days |
| Records of how the service is used | 365 days |
| Server logs | According to Netlify's standard log retention periods |
Within a venue's account, the venue decides how long its guest data is kept: it can erase a guest at any time, and the guest's details are then removed from the guest book and from the venue's bookings and orders, while the venue's money records are kept without the guest's name.
When the early-access removal link is used, the entry is erased, not merely marked as removed. Deleted data may remain in our providers' backups for a short period until they are overwritten; it is not restored from them.
9. Your rights
Under the UK GDPR and the GDPR you have the right to:
- access the data we hold about you and receive a copy (Article 15);
- have inaccurate data corrected (Article 16) — on the early-access list you can also simply send the form again with the same e-mail address, and in your account you can edit your details yourself;
- have your data erased (Article 17) — the fastest way is the link in any of our early-access e-mails, or deleting your account (see our account-deletion page);
- restrict processing (Article 18);
- receive the data you gave us in a portable format (data portability, Article 20);
- object at any time, on grounds relating to your particular situation, to processing based on our legitimate interests (Article 21); we will then stop unless we have compelling legitimate grounds or need the data for legal claims;
- withdraw your consent at any time where we rely on consent — for example to the early-access list — without affecting the lawfulness of processing before the withdrawal.
To exercise any right, e-mail hello@slotina.io, or contact our EU representative (section 1). We answer within one month. We may ask you to confirm your identity if we have reasonable doubt about it — usually by replying from the e-mail address concerned. If you are a guest of a venue, please see section 3.8.
10. Complaints
You can complain to a data protection supervisory authority, in particular in the country where you live, work, or where you believe the infringement took place:
- United Kingdom: Information Commissioner's Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF — ico.org.uk
- Ireland: Data Protection Commission — dataprotection.ie
- Hungary: Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH) — naih.hu
- Poland: Prezes Urzędu Ochrony Danych Osobowych (UODO) — uodo.gov.pl
- Romania: Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP) — dataprotection.ro
- Germany: the data protection authority of your federal state (Land); a list is available at bfdi.bund.de
- Austria: Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna — dsb.gv.at
- France: Commission nationale de l'informatique et des libertés (CNIL) — cnil.fr
We would appreciate the chance to resolve your concern first: please write to hello@slotina.io.
11. Cookies and similar technologies
slotina.io sets no cookies and uses no analytics, advertising or other tracking technology. While the site is in a password-protected preview, your browser remembers the access login for the session; this is strictly necessary to show you the page.
app.slotina.io uses only what is strictly necessary for the service: a cookie that keeps you signed in, one that remembers the language of the console, and a few settings stored in your browser (for example, an unsent order or the kitchen screen's sound). It uses no analytics or advertising cookies, so it shows no cookie banner. Our Cookie Statement lists each of them by name.
12. No automated decisions, no sale of data
We do not make decisions about you based solely on automated processing, including profiling, that have legal or similarly significant effects. We do not sell personal data.
13. Children
The website, the early-access list and the service are intended for businesses and the people who run and work in them. They are not directed at children, and we do not knowingly collect data from anyone under 16 for our own purposes. A venue may record a child as a guest, for example in the size of a party or on an event ticket; that data is the venue's (section 3.8).
14. Security
The website and the service are delivered only over encrypted connections (HTTPS). Passwords are stored only as one-way hashes; two-step sign-in is available; the secrets of two-step sign-in are stored encrypted. Every venue's data is kept apart from every other venue's, access within a venue follows the roles the venue assigns, and access by our own staff is limited to what running and supporting the service needs and is logged. The early-access confirmation and removal links use random codes that cannot be guessed. Our hosting providers encrypt stored data and backups.
15. Changes to this notice
We may update this notice, for example when we add a feature or a provider. The current version is always on this page with its date. If we change it materially, we will tell account holders by e-mail before the change takes effect. We will not use the data you have already given us for a new purpose without first asking you where the law requires it.
16. Contact
Belavin Limited, 6 Salstar Close, Birmingham, B6 4PP, United Kingdom — hello@slotina.io