§ Naksha Restaurant OS
Privacy policy
Last updated 16 November 2026
This policy explains what information Naksha Restaurant OS handles, why, where it is kept and the choices you have. It covers restaurant owners and their staff, guests whose details a restaurant records, and visitors to this website.
1. Who we are, and our two roles
Naksha Restaurant OS is an online service for restaurants, cafes and food businesses, operated by Naksha Agency, (GSTIN ) ("Naksha Restaurant OS", "we", "us").
We handle information in two different ways:
- About our own customers. When a restaurant opens an account, we decide how its account details (name, login, plan and invoices) are used, and we are responsible for them.
- On behalf of restaurants. The records a restaurant keeps in the software, including its guests' names and phone numbers, belong to that restaurant. We store and process them only on its instructions, to provide the service. If you are a guest and have a question about what a restaurant holds about you, the restaurant is the right place to ask first.
2. What we handle
If you run or work at a restaurant
- Account details: the restaurant's name, the owner's name, the email address or mobile number used to sign in, and a password, which we store only as a one-way hash.
- Devices: a label for each browser that signs in (for example "Android phone"), when it last synced, and a session token stored as a hash.
- Plan and billing: your plan, trial and renewal dates, and the invoices we issue to you.
- Staff set up by the restaurant: names, roles and the four-digit PINs used to switch user at the counter. PINs are part of the restaurant's own records and are not passwords to the account.
Records a restaurant keeps
- Menu, tables, orders, KOTs, bills and how each bill was paid (cash, UPI, card and so on).
- Stock, purchases, expenses, attendance and reservations.
- Customers the restaurant chooses to record: name, phone number, visits, loyalty points and any credit (khata) balance.
Technical information
Like any website, our hosting provider's servers log the IP address, browser type and time of each request for a short period, to keep the service secure and working.
What we do not collect
- Card numbers, UPI PINs or bank passwords. Payments between a guest and a restaurant happen outside the software; it only records the mode and amount.
- Your location, contacts, photos or anything else on your device.
- Advertising or analytics profiles. There are no third-party trackers on this website or in the app.
3. How we use it
- To run the service: keeping a restaurant's devices in step with each other and keeping a copy of its records.
- To manage accounts: trials, plans, invoices and messages about them.
- To help when asked. Our support team can see a restaurant's account details, plan, devices and how many records it holds. We look inside the records themselves only to fix a problem the restaurant has reported, or when the law requires it.
- To keep the service safe: spotting misuse, locking an account after repeated wrong passwords.
We do not use restaurants' records for advertising, and we do not sell or rent them to anyone.
4. Storage on your device
The app is built to work without internet, so it keeps a full copy of the restaurant's records in your browser's storage on each device, along with the token that keeps the device signed in and a few preferences such as the theme. This storage is essential to the app and is not used to track you. We do not set advertising cookies. Clearing the browser's data for the app removes the copy on that device.
5. Who else handles it
We use a small number of companies to provide the service. They process information only on our instructions:
- Neon hosts the database, in Singapore.
- Vercel hosts the website and the app and carries requests over its network.
We may also disclose information if the law requires it, or to protect the rights and safety of our users. If the business is ever sold or merged, restaurants will be told before their information moves.
6. Where it is kept
On the restaurant's own devices, and in a database located in Singapore. Requests pass through our hosting provider's network, which operates in several countries.
7. How we protect it
- Connections between your device and our servers are encrypted.
- Passwords and session tokens are stored only as hashes.
- Each restaurant's records are kept apart, and only devices signed in to a restaurant's account can reach its records.
- An owner can see every device that is signed in and sign any of them out.
- Repeated wrong passwords lock an account for a while.
No system is perfectly secure. If we learn of a breach that affects you, we will tell you and the authorities as the law requires.
8. How long we keep it
- A restaurant's records are kept for as long as it has an account. If a plan ends, nothing is deleted.
- An owner can delete the account and its cloud records at any time from Settings, Cloud sync, or by asking us. The records are removed from the live database at once and from short-term recovery copies within 30 days.
- Copies on a restaurant's own devices stay there until the restaurant clears them.
- Invoices we have issued, and the records tax law requires us to keep, are kept for as long as that law requires.
9. Your choices and rights
You can ask us for a copy of the information we hold about you, ask us to correct it, or ask us to delete it. Restaurant owners can do most of this themselves inside the app, including downloading a full backup. If you are a guest of a restaurant, please ask the restaurant first; we will help it respond. You can also withdraw consent or complain to us using the details below.
10. Children
The service is for businesses and is not directed at children. We do not knowingly collect information from anyone under 18.
11. Changes to this policy
If we change this policy in a way that matters, we will say so on this page and, for account holders, inside the app before the change takes effect.
How to reach us
Write to us through naksha.agency. Our direct support contact is listed on the contact page.
Grievance officer
Complaints about how your information is handled go to our grievance officer, , at . We acknowledge a complaint within 24 hours and resolve it within 15 days.
Complaints about how your information is handled can be sent to the contact above, marked "Grievance". We acknowledge a complaint within 24 hours and resolve it within 15 days.