Privacy policy

Who we are

OrderOps is a service for restaurants: menus, orders, table reservations and integrations. It is provided by [Legal entity / sole proprietor name], [address] ("OrderOps", "we").

For questions about personal data, write to [data requests e-mail].

This is the pilot edition. The text will be reviewed by a lawyer before commercial launch, and changes will be published on this page.

Who is responsible for your data

• Restaurant guests. When you book a table on a restaurant’s page, widget or Telegram, that restaurant is the controller of your data. OrderOps processes it as a processor — only on the restaurant’s instructions and under a data processing agreement.
• Cabinet users and visitors of the OrderOps website. OrderOps is the controller of account data, website requests and technical data.

For questions about a specific booking, contact the restaurant first.

Data of guests who book a table

• name, phone and/or e-mail — to confirm the booking and contact you;
• Telegram identifier — only if you link Telegram to the booking yourself;
• booking details: date and time, party size, table or area, booking code and status;
• notes and request tags (for example "birthday", "high chair", "allergy"); allergy details live only in your notes;
• booking source: page, widget, Telegram, link UTM tags;
• a protected link to manage the booking: change it, cancel it or erase your data;
• if you tick “Remember me on this device”, your name, phone and e-mail are kept only in this device’s browser for up to 12 months to fill in the form next time; we do not receive them from there, and “Not me” in the form deletes them at once;
• technical request data (including the IP address) — to protect against abuse and automated requests.

Data of cabinet users and website visitors

• account: name, e-mail, role and the venues you can access; sign-in with a password or with Google if you choose it;
• website form requests: name, contact, venue name, message;
• the activity log of the cabinet, including views of a guest’s full phone number;
• technical data: IP address, browser type and request times in server logs; cookies needed for sign-in and the session.

Restaurant pages may enable the restaurant’s own analytics only with your consent. Booking events there contain no name, phone, e-mail or notes.

Why we process data

• to accept, confirm and run your booking;
• to send service messages by e-mail or Telegram: confirmation, reminders (at most one a day before and one 2 hours before the visit), a request to reconfirm, notices of changes or cancellation;
• to let restaurant staff work with bookings;
• to protect the service from abuse and keep security logs;
• to provide the service to restaurants, run accounts and answer requests.

We send guests no marketing and never sell personal data. Booking data is not sent to the restaurant’s POS system.

Legal bases

We process data under the Law of Ukraine "On Personal Data Protection". For guests and restaurants in the EU, this policy is worded to be compatible with the EU General Data Protection Regulation (GDPR).

• your consent — when you send a booking or link Telegram; you can withdraw it by erasing your data;
• performance of a contract — your booking with the restaurant, the restaurant’s contract with OrderOps;
• legitimate interest — service security, abuse protection, staff work with bookings;
• legal obligation — when the law requires us to keep or disclose data.

How long we keep data

• booking notes — 30 days after the visit;
• guest name and contacts — 12 months after the visit;
• bookings that never happened (unconfirmed, expired or rejected) — cleared at once;
• a restaurant may change these periods for its venue;
• account data — while the account and the contract are active, then for the periods the law requires.

After clearing, a booking keeps only de-identified data (date, party size, status) for the restaurant’s statistics.

Who can access data

Restaurant staff see bookings according to their role. A guest’s full phone number opens only through a separate action that is logged. Staff Telegram alerts carry only the time, party size, table, source, booking code and the guest’s initial.

We use these subprocessors:

• NoCodeBackend — database hosting (all service data, contacts encrypted); USA;
• Contabo — the server (VPS) running the application and background workers; region [to be confirmed];
• Cloudflare — network protection and delivery of website traffic; global network;
• OrderOps’s own mail server (mail.tolqa.com) — sending service e-mails; Germany (EU);
• Telegram — bot messages to guests who linked Telegram and staff alerts; region [to be confirmed];
• Google — sign-in with Google for cabinet users who choose it.

We notify restaurants in advance before adding a new subprocessor.

International transfers

The database is hosted in the USA, so data is transferred outside Ukraine and the EU. We choose providers that ensure adequate data protection and sign agreements with them. For the EU, transfers will be covered by standard contractual clauses [to be confirmed].

Your rights and how to use them

You have the right to know what data about you is processed, to access, correct or delete it, to restrict or object to processing, to withdraw consent, and to complain to the Ukrainian Parliament Commissioner for Human Rights (in the EU — to your data protection authority).

• erase your data yourself — through the booking management link in the e-mail or message; this erases the contacts of that booking and its moves;
• contact the restaurant — it is the controller of the booking data;
• write to us at [data requests e-mail] — we will pass the request to the restaurant and help fulfil it. We reply within 30 days.

How we protect data

• the guest’s name, phone, e-mail, Telegram and notes are stored encrypted (AES-256-GCM);
• returning guests are matched by keyed hashes, not by plain text;
• access is by role and venue: each restaurant sees only its own data;
• every view of a guest’s full phone number is logged;
• service logs contain no names, phones, e-mails or notes;
• booking management links are signed and can be revoked;
• we notify the restaurant of a data incident without undue delay and within 72 hours.

Children

Bookings and the cabinet are meant for adults. If you believe a child has sent us their data, write to us and we will delete it.

Changes to this policy

Pilot edition of 2026-10-12 (version privacy-2026-10-12-pilot). We will announce material changes on this page and notify restaurants by e-mail in advance.