Last updated: 16 November 2026
- We keep what is needed to run Tably for you; passwords and PINs only as hashes.
- What a restaurant enters about its staff and guests is processed on its behalf, only to provide the service.
- We do not sell personal data and do not use it for advertising.
- Payments go through Paddle: card details never reach our servers.
- Google Analytics runs only on our public pages, never in a workspace or on the tablets.
- A deleted restaurant’s data is gone within 30 days (backups within 14). Questions: support@tablypos.com.
1.Who is responsible
Daniil Safonov, trading as Tably, Mittapheap Street, Village 5, Sangkat 4, Preah Sihanouk Province, Cambodia (“we”) runs Tably POS at tablypos.com and in the Tably apps. For your account and billing we decide how personal data is used. For the data a restaurant enters about its staff and guests, the restaurant decides and we process it on its behalf, only to provide the service, under the Data Processing Addendum. Contact: support@tablypos.com.
2.What we keep
- Your account: name, email, your position, the restaurants you belong to and your role there. Passwords are stored only as a salted hash (PBKDF2), never in readable form.
- Billing: your plan and add-ons, invoices, the email for invoices and payment status. Card details are entered with Paddle and never reach our servers.
- What the restaurant enters: menu, orders and receipts, stock and suppliers, transactions and accounts; employees (name, phone, role, PIN as a hash, schedule, salary and payments, and — if the restaurant adds them — birthday, address, emergency contact, identity document details and scans, photo; with Time clock turned on, a photo taken on the tablet when they clock in and out — the tablet only checks that a face is in the picture, on the device itself; we do not recognise faces or keep any facial template); customers (name, phone, visits, spending, discounts).
- Guests using a QR menu: guests need no account and give no name or contact. What they order or ask for (a waiter, the bill) goes to the restaurant with their table or number, as the restaurant’s data; their phone keeps a random id (so a guest sees only their own requests), their basket and their language.
- Gift cards and deposits: each card’s code, balance and what was bought and spent with it, and — when the restaurant adds them — the guest’s name, phone, email and a message for the card. A guest with an email gets the card and notes about it (bought, topped up, spent, ending soon) from our email service on the restaurant’s behalf; the card’s own page can be opened by whoever has its link.
- Problem reports: what you write when you report a problem from the website, the screenshots you add and the page you were on, with your name and email, so we can answer you. Screenshots may show your restaurant’s data; only your restaurant and our team can open them.
- Devices and activity: the tablets of a restaurant, who signed in on them and when, an activity log of changes, and technical logs our servers keep for security (such as IP addresses and error reports).
3.Why we use it
- To provide the service: sign-in, keeping your restaurant’s data, syncing the tablets, printing, reports, payroll.
- To bill for the plans and send account emails (sign-in codes, invitations, invoices, important notices).
- To keep Tably secure, find and fix errors (including the problems you report to us), and prevent misuse.
- To meet legal obligations, such as keeping invoices.
We do not sell personal data, do not use it for advertising, and do not use the restaurants’ data about their staff and guests for our own purposes.
4.Who else processes it
Only services that help us run Tably, each for its own part: the hosting provider of our servers; an email delivery service (Brevo) for account emails; Paddle.com, our online reseller and the Merchant of Record for our orders, which processes payments and receipts as a controller under its own privacy notice; Google Fonts, which delivers some fonts of the sign-in page to your browser (and so sees your IP address); Google Analytics, which counts visits to our public pages (see section 5); DeepL, which translates a restaurant’s menu texts for its QR menu when the restaurant asks for it (menu texts only, no personal data); Openverse, Wikimedia Commons, Pixabay and Pexels, which are searched with a dish’s name when you look for a picture for it (no personal data); an exchange-rate service for the second currency’s rate (no personal data); jsDelivr and Google, which deliver to a tablet the face-detection code used by Time clock and the QR reader used for gift cards (and so see the tablet’s IP address). They act on our instructions and may process data in countries other than yours, with the protection the law that applies to them requires. We may disclose data when the law requires it.
The full list, with what each one does and where, is on the Sub-processors page.
What a restaurant sends elsewhere itself. Some features send data to places the restaurant chooses, under that service’s own terms: Telegram notifications (the Telegram add-on) send shift closes, sales, expenses, staff names and similar messages to the Telegram chats the restaurant connects; API keys, webhooks and AI assistants connected in Settings → Integrations receive the data their key allows. The restaurant decides what to connect and can disconnect it at any time.
5.Cookies and storage on your devices
The website uses one cookie that keeps you signed in, and keeps a few preferences in your browser (for example which tips you closed). The tablet app keeps the restaurant’s menu, open orders and settings on the device so it works without internet; a kitchen display also keeps its tickets there. We do not use advertising cookies.
On our public pages only (the home page, Pricing, Download, Developers and these legal pages) we use Google Analytics to see how many people visit, which pages they read and where they come from, so we can improve the site. It collects information about your visit (the pages you open, your browser and device, an approximate location from your IP address) and may set its own cookies for that. Visitors from the European Economic Area, the United Kingdom and Switzerland are counted without these cookies. Google Analytics never runs inside a restaurant’s workspace or on the tablets, so it does not see restaurant, staff or guest data. Google processes this data under its own privacy policy (policies.google.com/privacy); you can block it with your browser’s settings or Google’s opt-out add-on (tools.google.com/dlpage/gaoptout).
6.How long we keep it
As long as your account or the restaurant uses Tably. When a restaurant is deleted at its request, its data is deleted from our systems within 30 days, except invoices and what the law requires us to keep. Daily database backups are kept for 14 days, so deleted data disappears from them within that time. Server logs are kept for a limited time for security.
7.Security
Connections are encrypted (HTTPS); passwords and PINs are stored as hashes; each restaurant’s data is kept apart from the others; staff see only what their role allows. No system is perfectly secure: keep your passwords and PINs to yourself and tell us of any suspected misuse.
8.Your choices and rights
You can see and correct your account details in Profile settings, and a restaurant can correct or remove the data about its staff and guests. You can ask us for a copy of your personal data, its correction or deletion, or object to its use, by writing to support@tablypos.com. A staff member or guest of a restaurant should first ask that restaurant; we help it answer.
9.Changes
We may update this policy; the date at the top shows the latest version, and we tell you about important changes in the app or by email.