Privacy policy
How personal data is handled under Regulation (EU) 2016/679 (GDPR).
Who is responsible
Each restaurant is the controller for the orders placed at its tables. The operator of this platform provides the software and acts as a processor on the restaurant's instructions (GDPR art. 28). The restaurant's own contact details are linked from the bottom of its menu.
What we process, and why
Ordering. When a guest scans a table's QR code we store which table it was, which dishes were ordered, any note they typed, and the payment status. No account, name, address or phone number is requested. Legal basis: performance of a contract, art. 6(1)(b).
Session cookie. One strictly necessary cookie keeps the table's session and, for staff, the login. It carries no advertising or analytics identifier and is exempt from consent under art. 5(3) of the ePrivacy Directive.
Receipt by email. Only if a guest types their address in to receive a receipt. It is used for that email and nothing else.
Restaurant accounts. Name, email and a hashed password for staff logins, plus the subscription record needed to invoice. Legal basis: contract and legal obligation, art. 6(1)(b) and (c).
What we do not do
No advertising, no profiling, no tracking pixels, no sale of data, and no transfer of personal data to third countries. Payment card details are never seen or stored by this service — card payments are handled by the payment provider.
How long data is kept
Order history is retained for the period each restaurant sets (365 days by default), after which it may be deleted, subject to the longer retention periods that tax law imposes on the restaurant's own accounting records. Account data is kept for as long as the subscription lasts.
Your rights
You have the right of access (art. 15), rectification (16), erasure (17), restriction (18), data portability (20) and objection (21), and the right to lodge a complaint with a supervisory authority (77). Requests about an order go to the restaurant that served you; requests about the platform itself go to the operator listed in the imprint.
Security
Traffic is encrypted in transit, passwords are stored only as salted hashes, and access to a restaurant's data is limited to its own staff accounts and the platform operator.