Who we are
Ordinero is software for restaurants, cafés and bars: QR menus, ordering and payment from the table, a till, kitchen displays and store management. The provider's details:
- Name
- Ordinero
- admin@ordinero.gr
- Website
- ordinero.gr
The business that provides Ordinero has not completed its registration yet. Its legal name, registered address, VAT number and business registry number will be published here as soon as it has. Until then, write to the email above about anything.
We have not appointed a Data Protection Officer (DPO): at our current size and type of processing, article 37 GDPR does not require one. For anything about your data, write to admin@ordinero.gr.
Who decides what
Depending on who you are, the "controller" (whoever decides why and how your data is processed) is either us or the restaurant.
- We are the controller for the accounts of businesses and their staff, the subscription and its billing, support, the security of the service, the ordinero.gr waiting list and our own usage analytics.
- The restaurant is the controller for everything about its guests: orders, payments and tips, reviews, calls for a waiter, QR scans and menu statistics. We process these on its behalf, as "processor", under the Data Processing Agreement (article 28 GDPR).
If you are a restaurant's guest and want to use one of your rights, contact the restaurant. If you write to us, we will pass your request on and help the restaurant answer you.
What data we process
Businesses and staff
- Account details: name, email, phone, address, photo and a short bio, if you fill them in. Staff accounts are created by the owner, with an email and password the owner sets.
- Sign-in: your password (stored only as a hash), your passkeys (only the public key) and station PINs (only as hashes).
- Security: sessions and devices (browser, device type), and a security log with IP addresses, browser and actions such as sign-in, password change or signing devices out.
- Store: name, address and coordinates, menus, prices, photos, tables, staff roles and permissions, and the details you give for myDATA receipts (legal name, VAT number).
- Subscription: your plan and billing details at Stripe. Your card details are held by Stripe, not by us.
- Support: subject, message and priority of your requests.
- Assistant (artificial intelligence): your questions and the answers, with the model, timings and cost of each answer.
Restaurants' guests
- Order: the dishes, options, the notes you write, the table, time and language. Name and email are optional; you give them if you want a receipt and updates by email. When staff enter the order, they may also record a phone number.
- Payment and tip: amount, method, status. Your card goes straight to Stripe or Cardlink and never passes through us.
- Ordering together at the table, if you use it: a name, if you choose to type one (otherwise “Guest” and a number), the people you add to your party, each person's dishes and when you are ready. Only the phones ordering at the same table see them, live, and we do not store them. When the order is sent and each person pays their own share, the names become the name of that share of the bill and are kept with the payment.
- Review: rating, tags, comment and whether you liked each dish; your name only if you choose to show it. Only the restaurant sees your review. The menu shows publicly only how many guests liked each dish, without names, once at least 5 have rated it.
- Call for a waiter: the kind of call and any note you write.
- QR scan: device type, browser and operating system with their versions, and the page you came from (referrer). Not your IP address.
- Menu statistics, only with your consent: a random visit ID, which dishes you saw and opened, what you put in the cart and what you typed in the search. No IP, browser or notes.
- Fraud check: a flag on the order, if it looks fake (see Artificial intelligence and automated checks).
- Bot check: when you send an order, Cloudflare (Turnstile) checks that a person is sending it, using your IP address, TLS fingerprint and your browser's User-Agent. We keep nothing from the check except whether it passed.
Visitors to ordinero.gr
- Waiting list: your email, your language and a confirmation code.
- Usage analytics through Amplitude, only with your consent: pages, clicks, device and browser, IP address (for approximate location), where the visit came from, and a recording of on-screen activity with text and typing hidden. Details in the Cookie Policy.
- Rate limits: to stop abuse we keep, for 24 hours, a hash of your IP address or account together with the part of the service you used.
Why we process it, and on what legal basis
| Purpose | Legal basis (GDPR) |
|---|---|
| Accounts, sign-in and providing the service to businesses | Performance of a contract, article 6(1)(b) |
| Staff accounts the business asks for | The business's and our legitimate interest in giving it the accounts it asked for, article 6(1)(f) |
| Subscription, invoices, accounting and tax records | Performance of a contract and legal obligation, article 6(1)(b) and (c) |
| Service emails: account confirmation, password reset, approvals | Performance of a contract, article 6(1)(b) |
| Account security, abuse prevention, rate limits | Legitimate interest in keeping the service and accounts secure, article 6(1)(f) |
| Support, and automatic estimate of a request's priority | Performance of a contract, and legitimate interest in answering urgent requests first, article 6(1)(b) and (f) |
| AI assistant, automatic menu translation, AI dish photos, AI stock-taking | Performance of a contract: they are features you ask for, article 6(1)(b) |
| Measuring the assistant's cost and speed (without the message text) | Legitimate interest in controlling the service's cost and reliability, article 6(1)(f) |
| Finding and fixing errors on our servers (only the error message and the route, no account or request data) | Legitimate interest in keeping the service working properly, article 6(1)(f) |
| Usage analytics with Amplitude, and menu statistics | Consent, article 6(1)(a) GDPR and article 4(5) Greek Law 3471/2006 |
| The ordinero.gr waiting list | Steps you asked for before a contract, article 6(1)(b) |
| Complying with the law and requests from public authorities | Legal obligation, article 6(1)(c) |
| Establishing, exercising or defending legal claims | Legitimate interest, article 6(1)(f) |
For its guests' data, the restaurant sets the legal basis: usually performance of the contract for the order and payment, legitimate interest for the fraud check, QR scans and the dish scores on the menu, and your consent for menu statistics.
We send no marketing emails and do not use your data for advertising.
Allergies and other sensitive information
If you write an allergy or a dietary need about your health in the order notes, that is a special category of data (article 9 GDPR). You write it only if you want to, and by writing it you give your explicit consent for the restaurant to use it to prepare your order correctly (article 9(2)(a)).
Notes are shown in the kitchen, at the till and in the order emails, if you gave your email. They do not go to the payment provider. The fraud check does not send its AI model notes that mention an allergy or intolerance, an illness or medicine, a pregnancy, a vegetarian or vegan diet, or a religious practice such as halal, kosher or fasting. It recognises them by specific words, mainly in Greek and English, so a note that says it in other words or another language can still reach the model if it also has suspicious words or is unusually long. So do not write anything else personal there.
For a serious allergy, tell the restaurant's staff too. Allergen information on the menu is the restaurant's responsibility and, when a menu is translated automatically, the translation can contain mistakes.
Artificial intelligence and automated checks
Some features send text or images to AI models through OpenRouter (US), which forwards them to the model's provider:
| Feature | What is sent |
|---|---|
| Assistant for owners | Your question, the earlier questions in the chat and the figures it needs to answer (sales, dishes, stock, tables, menu statistics). If answer checking is on, the question, the figures and the draft answer are also sent to a second model for a cross-check. |
| AI stock-taking | Stock notes and photos of supplier invoices. |
| Automatic menu translation | Only the menu's texts. |
| AI dish photos | The description you write and the photos you pick as a base. |
| Fraud check on orders | Only when the name or notes contain suspicious words, or the notes are unusually long: the order's name, notes, dishes and total. Not notes it recognises as being about your health, diet or faith (see Allergies and other sensitive information). |
| Support request priority | The request's category, subject and message. |
For all of them we ask OpenRouter to use only providers that do not train models on what they are sent. For AI dish photos, OpenRouter does not yet confirm that it honours this request.
The assistant tells you that its answers come from an AI model, as article 50 of the Artificial Intelligence Act, Regulation (EU) 2024/1689, requires. Its answers can be wrong.
Every dish photo made with AI says so inside the file itself, in a machine-readable form: the IPTC value trainedAlgorithmicMedia, in its XMP metadata. Wherever such a photo appears on a menu, guests see an “AI image” label on it. The same goes for photos a restaurant made with another AI tool, if their file carries the same value. When at least a quarter of the menu text a guest reads is a machine translation the restaurant has not edited, the menu shows a note that it was translated automatically by AI, and the menu data says so. The marks hold no personal data (article 50 of the same Regulation).
We make no decisions based solely on automated processing that have legal or similarly significant effects on you (article 22 GDPR). The fraud check never refuses an order: it only flags it on the Service station, where staff confirm every order not paid online anyway. The app refuses an order only when the bot check fails or when three orders at the table are already waiting for confirmation, and cancels any order staff did not confirm and nobody paid within 20 minutes. In each of these cases you can ask staff to put it through. The priority estimate can lower a support request's priority, but a person reads every request.
Who receives it
We do not sell data. We share it only with those needed to run the service, under contracts that bind them to protect it and use it only for us:
| Recipient | For | Where |
|---|---|---|
| Contabo GmbH | Hosting of the servers and the database | Germany |
| Cloudflare, Inc. | Content delivery and attack protection; the app's traffic to its database passes through its network. It also runs the bot check when an order is sent, and uses the check's data, as an independent controller, to improve its bot detection (Turnstile Privacy Addendum) | US, with data centres worldwide |
| Stripe | Guest payments, into the restaurant's Stripe account: the order number, the dishes with their options, the amounts, and your name and email if you gave them, but not your notes. Also our subscriptions. Stripe is also an independent controller for fraud prevention and its legal duties: Stripe's privacy policy | Ireland and US |
| Cardlink | Payments, when the restaurant uses Cardlink: description, amount, email, phone and billing address | Greece |
| Resend | Sending email: account and waiting-list emails, and to guests order confirmations, bills, receipts and updates | US |
| OpenRouter and the model providers it forwards to | The AI features in the section above | US and the provider's country |
| Amplitude, Inc. | Usage analytics (with consent), including errors the app shows you; measuring the assistant's cost and speed with your account ID but without the message text; and reports of errors on our servers, with the error message and the route but no account or request data | US |
| AADE (Greek tax authority) | If the restaurant connects myDATA, its receipts are transmitted with its own credentials; retail receipts carry no guest details | Greece |
| Unsplash, OpenFreeMap, OpenStreetMap Foundation | Photos, maps and geocoding loaded by your browser; they see your IP address | Canada, US, EU, UK |
| Some of our emails load fonts from Google when you open them, so Google sees your IP address | US |
Also: the restaurant sees what you send it with your order, and an owner sees their staff's activity in Ordinero. We give data to public authorities only when the law requires it, and to our legal or accounting advisers when needed, under a duty of confidentiality.
Transfers outside the European Union
Where a recipient is outside the EU or the European Economic Area, the transfer relies on:
- the Commission's adequacy decision for the EU-US Data Privacy Framework (Decision (EU) 2023/1795), for US companies certified under it;
- otherwise, the Commission's Standard Contractual Clauses (Decision (EU) 2021/914) with any supplementary measures needed;
- for the United Kingdom and Canada, the Commission's adequacy decisions.
You can ask for a copy of the safeguards at admin@ordinero.gr.
How long we keep it
| Data | Period |
|---|---|
| Business or staff account | As long as the account exists. If you ask us to delete it, we do so within 30 days, except what the law requires us to keep. |
| Invoices and billing records | At least 5 years from the end of the year in which the tax return they relate to is due, and longer while the tax authority can still audit them or a case about them is pending (article 13(2) of Law 5104/2024). |
| Security log (IP, browser, actions) | 12 months, or until the account is deleted, if that is sooner. |
| Temporary QR, phone and screen-pairing sign-in sessions | Deleted 1 hour after they expire. |
| Rate limits (hash of IP or account) | 24 hours. |
| Assistant chats | Until you delete them. Chats left idle for 180 days are deleted automatically. |
| Support requests | While open. Once closed, 24 months from the last message. Deleted sooner if the account is deleted. |
| Waiting list | Until sign-up opens for you or you ask us to remove you. |
| Name, email and phone on an order | Cleared 12 months after the order. |
| Name and comment on a review | Cleared 24 months after the review. The score and tags stay. |
| Orders, payments, reviews, calls for a waiter, QR scans | On the restaurant's behalf, as long as the restaurant is on Ordinero or until it deletes them. When the store is deleted, they are deleted with it. The law requires the restaurant to keep its tax records at least 5 years from the end of the year in which the tax return they relate to is due (article 13(2) of Law 5104/2024). |
| Detailed menu statistics | As long as the restaurant sets, 90 days unless it sets otherwise (from 1 to 730). After that only aggregated totals remain. |
| Usage analytics at Amplitude | As set in our Amplitude account. If you withdraw consent, all new collection stops. |
When a period ends, the data is deleted or kept only in a form that does not identify you. Backups are overwritten on their own cycle.
Your rights
Under articles 15 to 22 GDPR, you have the right to:
- access: find out whether we process your data and get a copy;
- rectification of anything wrong or incomplete;
- erasure, when the data is no longer needed or there is no lawful basis;
- restriction of processing, for example while we look into an objection;
- portability: get what you gave us in a structured, machine-readable format, or have us send it to someone else;
- withdraw consent at any time, without affecting anything done lawfully before.
Right to object (article 21 GDPR). Where we process your data on the basis of legitimate interest, you can object at any time, on grounds relating to your particular situation. We then stop, unless we show compelling legitimate grounds that override your interests, or need the data for legal claims.
To use a right, write to admin@ordinero.gr. We answer free of charge within one month, which can be extended by two more months for complex requests, and we will tell you why. We may ask you to confirm your identity. For a restaurant's guest data, contact the restaurant (see Who decides what).
Complaints to the Data Protection Authority
If you believe we are infringing your rights, you can lodge a complaint with the Hellenic Data Protection Authority: 1-3 Kifisias Ave., 115 23 Athens, Greece, tel. +30 210 6475600, www.dpa.gr. We would appreciate the chance to sort it out first, so please write to us too.
Do you have to give us your data?
To open and use an account we need an email and a password or passkey; without them we cannot provide the service. For a subscription we need billing details. As a restaurant's guest you can order without a name or email; without an email you simply will not get a receipt and updates by email.
Security
We encrypt every connection (HTTPS), store passwords and PINs only as hashes, support passkeys, keep sign-in cookies out of page scripts' reach (httpOnly), limit access by store and role, and host the database in Germany. No online service is perfectly secure.
If a breach may affect you, we tell the Data Protection Authority within 72 hours, and you without undue delay when the risk is high (articles 33 and 34 GDPR). For guest data we tell the restaurant, as the controller.
Children
Only adults open Ordinero accounts, on behalf of a business. Anyone can use the menus. In Greece, people under 15 cannot consent on their own to information society services (article 21 Greek Law 4624/2019): if you are under 15, press Reject in the cookie panel or ask a parent to decide.
Changes to this policy
We update it when the law changes or the way the service works changes. The date and version at the top show when it last changed, and the history at the end shows what changed. For significant changes we tell account holders by email or in the app.
Change history
- Version 1.6 · 28 October 2026Added Cloudflare's bot check (Turnstile) when an order is sent, with the data Cloudflare sees and its role under its Turnstile Privacy Addendum (18 June 2025), and that staff now confirm on the Service station every guest order not paid online, while orders nobody confirms or pays are cancelled after 20 minutes (recipients and automated decisions, articles 13 and 22 GDPR).
- Version 1.5 · 9 October 2026Added that we send Amplitude reports of errors on our servers, with only the error message and the page or API route and no account or request data, so we can find and fix them, and that errors the app shows you reach Amplitude only with your consent (recipients and purposes, article 13 GDPR).
- Version 1.4 · 8 October 2026Added the data of the new ordering-together-at-the-table feature: the optional name, each person's dishes and readiness, which only the phones at the same table see live, and that the names become the name of each share of the bill (information on the data collected, article 13 GDPR).
- Version 1.3.3 · 23 September 2026Orders no longer have a tracking code (PIN). An order is tracked by its order number, so the code was unnecessary (data minimisation, article 5(1)(c) GDPR). Removed it from the order data and the retention table.
- Version 1.3.2 · 23 September 2026We no longer keep the IP address and browser an order was sent from, or a copy of the guest's name in the security log (data minimisation, article 5(1)(c) GDPR). Removed them from the order data and the retention table.
- Version 1.3.1 · 23 September 2026Added that AI dish photos say inside their file, in a machine-readable form, that AI made them, that menus show them with an “AI image” label, and that a menu read in a machine translation says so in a note and in its data (article 50 of Regulation (EU) 2024/1689). The marks hold no personal data.
- Version 1.3 · 23 September 2026Retention limits where there were none (article 5(1)(e) GDPR): security log 12 months; name, email, phone and IP on orders 12 months; name and comment on reviews 24 months; closed support requests 24 months. QR scans no longer keep the IP address. Added that we keep each order's IP address and browser for the security of the service, and the period for tax records now follows article 13(2) of Law 5104/2024.
- Version 1.2 · 23 September 2026The menu now shows how many guests liked each dish, from their reviews and without names, once at least 5 have rated it, instead of a rating the restaurant typed in itself (article 9στ points λγ΄ and λδ΄ of Greek Law 2251/1994, added by Law 4933/2022). Added this to the review data and to the legal bases.
- Version 1.0.1 · 23 September 2026Order notes no longer go to Stripe, and the fraud check no longer sends its AI model notes it recognises as being about health, diet or faith (article 9 GDPR). Every AI feature now asks OpenRouter for providers that do not train models on the data. The text used to say the providers do not keep it, which OpenRouter does not promise.
- Version 1.0 · 23 September 2026First published.