The parties and their roles
The controller is the business that uses Ordinero ("you"). We are the processor:
- 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.
This agreement covers only what we do on your behalf. For what we process for our own purposes (your account, billing, the security of the service, our usage analytics), we are the controller and the Privacy Policy applies.
On data protection matters, this agreement prevails over the Terms of Service.
What we process
| What | Description |
|---|---|
| Subject matter and purpose | Providing Ordinero to your restaurant: menu, orders, calls for a waiter, kitchen and till screens, payments, receipts and their transmission to myDATA, reviews and tips, statistics, the assistant and fraud checks. |
| Nature of the processing | Collection through the menu and the dashboard, storage, organisation, display to your staff, sending email on your behalf, transmission to your payment providers and, if you enable it, to AADE, analysis for statistics, and deletion. |
| Data subjects | Your guests and your staff. |
| Guest data | Table, order and notes, name, email and phone when given, payment status (no card details), tips, reviews and comments, calls for a waiter, the device, browser and operating system of the QR scan, and, with their consent, a visit identifier and their movements through the menu. |
| Special categories | An order's notes may mention allergies or dietary restrictions, which is health data (GDPR article 9). We do not ask for it in a separate field. |
| Staff data | Name, email, role and permissions, and who handled each table and order. |
| Duration | For as long as our contract lasts, and then until we return or delete the data under the "End" section. Within that time, data is kept as the Privacy Policy sets out or until you delete it. |
We process only on your instructions
We process the data only on your documented instructions, meaning this agreement, the Terms of Service and the settings you choose in Ordinero, and that includes transfers outside the EU. The only exception is what EU or Greek law requires of us; we then tell you beforehand, unless the law forbids it.
If we believe an instruction of yours breaches the GDPR or another data protection law, we tell you at once.
You are responsible for having a lawful basis for the data you give us to process, and for informing your guests and staff.
Confidentiality
Only those of us who need access to provide or support the service have it, and all of them are bound to keep the data confidential.
Security measures
We take the technical and organisational measures of GDPR article 32. Today they are:
| Measure | How it is applied |
|---|---|
| Hosting in the EU | The servers and the database are in Germany. |
| Encryption in transit | All traffic with the service goes over HTTPS (TLS). |
| Access control | Staff access is checked on the server against the user's restaurant and role, and anything not explicitly allowed is denied. The database also enforces its own row-level access rules. |
| Passwords and PINs | Account passwords and station PINs are stored only as hashes (bcrypt). Passkeys are supported too. |
| Abuse protection | Request limits, lock-out after repeated wrong PINs, a bot check (Cloudflare Turnstile) and a limit of three orders waiting for confirmation per table on guest orders, and attack protection on Cloudflare's network. |
| Keys and secrets | Payment providers' and myDATA keys are stored encrypted, and logs mask secrets and credentials. |
| Payment cards | Guests enter card details directly with Stripe or Cardlink; they never pass through our servers. |
| Logging | Account sign-ins and security actions are recorded in a security log. |
| Minimisation | Temporary sessions and rate limits are deleted automatically, and detailed menu statistics after the period you set. |
The measures are reviewed as the service evolves, and we update this section when they change. We never lower the overall level of protection.
Sub-processors
You give us general authorisation to use the sub-processors below. Each is bound by contract to the same data protection obligations as we are, and we remain liable to you for its compliance.
| Sub-processor | What it does | Where |
|---|---|---|
| Contabo GmbH | Hosting of the servers and the database | Germany |
| Cloudflare, Inc. | Content delivery and attack protection; traffic to the service passes through its network. The bot check on guest orders (Turnstile) sees the guest's IP, TLS fingerprint and User-Agent, which Cloudflare also uses as an independent controller to improve its detection (Turnstile Privacy Addendum) | US, with data centres worldwide |
| Resend | Sending emails to your guests (order confirmation, bill, receipt, updates) | US |
| OpenRouter and the model providers it forwards to | The assistant, the fraud check on orders and the other AI features you use | US and the provider's country |
Stripe and Cardlink are not our sub-processors: you use them under your own contract, and we pass payment details to them on your instructions. The same applies to AADE when you connect myDATA. In addition, some emails load fonts from Google when opened, so Google sees the recipient's IP address.
Before we add or replace a sub-processor, we tell you by email at least 30 days in advance and update this page. You can object on reasonable data protection grounds at admin@ordinero.gr. If we find no solution, you can end the contract before the change, and we refund what you paid for the period you did not use.
Transfers outside the EU
When a sub-processor processes data outside the European Economic Area, the transfer relies on a Commission adequacy decision, such as the EU-US Data Privacy Framework (Decision (EU) 2023/1795) when the recipient is certified, or on the standard contractual clauses of Decision (EU) 2021/914 with any supplementary measures needed.
Requests, incidents and impact assessments
- Data subjects' rights: we help you answer your guests' and staff's requests for access, rectification, erasure, restriction, portability and objection. If such a request reaches us, we forward it to you without delay and do not answer it ourselves without your instruction.
- Personal data breaches: if we learn of a breach affecting your data, we tell you without undue delay, so that you can meet the 72-hour deadline of GDPR article 33. We tell you what happened, which data and how many people it concerns, the likely consequences and what we are doing to contain it, and add what we do not know yet as soon as we learn it.
- Impact assessments: we help you with the information we have when you carry out an impact assessment or a prior consultation with the data protection authority (GDPR articles 35 and 36).
Demonstrating compliance and audits
We give you any information you need to show that the obligations of GDPR article 28 are met, and we allow audits, including inspections, by you or an auditor you appoint who is bound by confidentiality. For an audit you give us reasonable notice, and we carry it out in a way that does not expose other customers' data. Each party bears its own costs.
End: return and deletion
When the contract ends, or whenever you ask, we return the data to you in a structured, machine-readable format, as section A6 of the Terms of Service sets out, and delete it 30 days later, unless the law requires us to keep it. When you delete a restaurant, its data is deleted with it at once.
Liability
Liability between the parties follows section A9 of the Terms of Service, without prejudice to GDPR article 82 for data subjects.
Change history
- Version 1.2 · 28 October 2026Added to the security measures and to the Cloudflare sub-processor entry the bot check (Turnstile) on guest orders, using the guest's IP address, TLS fingerprint and User-Agent, and that Cloudflare also uses this data as an independent controller to improve its detection (Turnstile Privacy Addendum, 18 June 2025; articles 28 and 32 GDPR).
- Version 1.1 · 23 September 2026QR scans no longer keep the guest's IP address. As the Privacy Policy now sets out, the name, email, phone and IP on an order are cleared 12 months after it, and the name and comment on a review 24 months after it (article 5(1)(e) GDPR).
- Version 1.0 · 23 September 2026First published.