Privacy policy

Last updated 5 October 2026

1. Who we are

RestPOS by ESdesire ("RestPOS") is restaurant point-of-sale software made and run by ESdesire ("we", "us"). It is made up of:

• the RestPOS website and web app, where restaurant owners and staff sign in, run the till in a browser and manage the back office;
• the RestPOS desktop app, which runs a till on Windows or Linux computers and keeps working offline;
• the RestPOS Waiter app for Android phones.

You can reach us about privacy at [email protected].

2. Our role and the restaurant's role

ESdesire is the controller for the data we need to provide and protect the service: sign-in accounts, device records, security logs, licences, and the details people send us when they book a demo or email us.

Each restaurant is the controller for the business data it records in RestPOS, including its staff records and its customers' details, orders and reservations. We process that data on the restaurant's behalf and only to provide RestPOS. If you are a guest of a restaurant that uses RestPOS, please contact the restaurant first about your data. If you cannot reach them, write to us and we will pass your request on.

3. What we collect

Owner and staff accounts

• Name, email address, role and the outlets you work at.
• Your password and, for waiters, a sign-in PIN. We store these only as one-way hashes, never as readable text.
• If you turn on two-factor sign-in, the authenticator secret and recovery codes, stored encrypted.
• Language and timezone preferences, and when you last signed in.

Devices

• Desktop tills: an installation ID, a name for the till (by default the computer's network name), the operating system (Windows or Linux), the app version, a public key the till uses to prove its identity, and when it last checked in.
• Waiter phones: a random device ID created by the app, a device name (by default "Waiter phone (Android)"), the platform, the app version and when it last checked in.

We do not collect device location, contacts, photos, phone model, or advertising IDs.

Security and technical logs

• For signed-in sessions: IP address, browser or app type (the user agent) and last activity time. You can see and end your own sessions on the account security page.
• An audit log of security and settings changes, such as sign-in method changes, password resets, staff changes and device sign-ins, with the time, the account, the IP address and the user agent.
• Standard web server logs, which record IP address, user agent and the page requested.

Restaurant business data

Everything a restaurant enters while running RestPOS: menus and prices, recipes and stock, suppliers, purchases and expenses, staff records, register counts, orders, sales and payments. Payments are recorded by method and amount. RestPOS does not read or store payment card numbers. If a restaurant turns on online payments for online ordering, card details are handled by the payment provider it chooses.

Restaurant customers' data

Restaurants can record details about their customers, such as name, phone number, email address, delivery addresses, date of birth and anniversary, tax registration number, loyalty points, account balance, order history and reservations. If a restaurant offers online ordering, its customers can create an account with a password. The restaurant decides what to record and why.

Demo requests and messages

When you book a demo we receive your name, restaurant name, city, phone or WhatsApp number, email address if you give one, number of outlets and your message, plus the IP address and user agent of the request. When you email us, we receive your email and anything you include.

4. How we use it

• To provide RestPOS: signing you in, running the till, keeping tills and phones in sync, and checking licences and device limits.
• To keep accounts and restaurants secure: two-factor sign-in, session management, audit logs and spotting misuse.
• To support restaurants when they ask for help.
• To reply to demo requests and messages.
• To meet legal obligations.

We do not sell personal data, we do not use it for advertising, and we do not use analytics or tracking tools on RestPOS.

5. Who we share it with

• Our hosting provider, which runs the servers RestPOS is hosted on.
• Our email delivery provider, when we send emails such as password reset links or demo request alerts.
• Providers a restaurant connects itself. A restaurant can connect its own SMS, WhatsApp or email account (for example Twilio, Mobishastra, RCSoft or its own mail server) to send receipts or messages to its customers, and its own payment provider (Stripe, PayPal or Razorpay) for online ordering. That data goes to the provider under the restaurant's account and the provider's own terms.
• Google services on some screens. Some till screens load fonts from Google Fonts, and a restaurant's customer website can show a Google map. When these load, your browser contacts Google.
• Authorities, when the law requires us to, and a buyer or successor if ESdesire's business is transferred, under the same protections.

RestPOS does not send push notifications today. If we add them, we will use a push service such as Firebase Cloud Messaging and update this policy first.

6. Where data is kept

• On our servers, run for us by our hosting provider, together with regular backups.
• On the restaurant's desktop tills. To keep selling offline, each till keeps a local copy of the restaurant's data, including customer details and sales. The restaurant is responsible for the physical security of its computers, for example by using a Windows or Linux account password and full-disk encryption.
• On waiter phones. The app keeps its sign-in tokens in the phone's secure storage and a few settings (such as the server address and the last restaurant used) in app storage.

7. Cookies and local storage

RestPOS uses only cookies that it needs to work:

• a session cookie that keeps you signed in, and a security cookie that protects forms against forgery, for both the web app and the till;
• a "remember me" cookie, only if you choose "Keep me signed in", which lasts until you sign out or it expires.

The till also uses your browser's storage to hold sales made while offline until they are uploaded, and to remember till settings. We do not use advertising or analytics cookies.

8. How long we keep it

• Accounts and restaurant data: while the restaurant uses RestPOS. When a restaurant leaves, we delete or anonymise its data after a deletion request, except records that the restaurant or we must keep by law, such as tax and accounting records. See data deletion.
• Sessions: a session ends after two hours without activity, unless you chose "Keep me signed in".
• Security audit log: for as long as the restaurant's account exists.
• Web server and application logs: for a short period, normally about two weeks.
• Backups: kept for a limited rolling period and then replaced. Deleted data can remain in a backup until that backup is replaced.
• Demo requests: for as long as we need to follow up. Ask us at any time to delete yours.

9. Security

Connections to our servers use HTTPS. Passwords and PINs are stored as one-way hashes and two-factor secrets are encrypted. Access is limited by role, owners can require two-factor sign-in for their restaurant, and security changes are logged. Only authorised ESdesire staff can reach our servers. No system is perfectly secure; if you find a problem, please tell us at [email protected].

10. RestPOS Waiter app

The RestPOS Waiter app is for staff of restaurants that use RestPOS. It does not show adverts and contains no analytics or crash-reporting tools.

• What it sends: to sign in, the restaurant code, your email address, your PIN or password and, if needed, a two-factor code, together with the app's random device ID, device name, platform and app version. While you work, it sends the orders you take.
• What it keeps on the phone: sign-in tokens in secure storage, and settings such as the server address, the till address, the device name and the last restaurant, email and outlet used. Signing out removes the tokens, and uninstalling the app removes everything.
• Permissions: on Android the app uses only internet access. It can talk directly to the restaurant's till over the restaurant's own local network; that connection stays inside the restaurant's network. Connections to our servers use HTTPS.
• Deleting your data: see data deletion for how to ask for your account and device records to be deleted.

11. Your choices and rights

Depending on where you live, you may have the right to ask for a copy of your personal data, to correct it, to delete it, or to object to how it is used. Staff can update their own name and password in RestPOS. For anything else, email [email protected]. If your request is about data a restaurant holds about you as a guest, we will refer it to the restaurant. You can also complain to your local data protection authority.

12. Children

RestPOS is a business tool for restaurants and is not meant for children. We do not knowingly collect children's data for our own purposes.

13. Changes to this policy

We will update this page when RestPOS or the way we handle data changes, and change the date at the top. If a change is significant, we will tell restaurant owners before it takes effect.

14. Contact us

ESdesire, email [email protected].