Privacy policy
Last updated 23 October 2026
This is a pre-launch draft; some company details (legal entity name, registered address, grievance officer, jurisdiction) are still being finalised.
This policy explains what personal data Queueless handles when you visit our website, run your café or restaurant on Queueless, or order from a restaurant's QR menu, and what you can do about it. We collect what we need to run the service and nothing for advertising.
1. Who we are
Queueless is operated by [Legal entity name], [Registered office address, city, state, PIN]. For business accounts and our website we decide how your data is used (we are the "Data Fiduciary" under the Digital Personal Data Protection Act, 2023).
When a restaurant uses Queueless to take orders from its guests, the restaurant decides what happens with its guests' order data and we process it on its behalf.
Questions: privacy@queueless.app.
2. What we collect
Restaurant owners and staff: name, email, optional phone number, and your password (stored only as a secure hash by our authentication provider). Business details you enter: business name, GSTIN, venues, addresses, menus, prices, photos, tables and team roles. Orders, bills, discounts and voids your venues record, and an audit log of sensitive actions.
Guests ordering from a QR menu: no account. Your phone gets an anonymous session so you can place and track your own orders. We store what you order, your notes, calls for a waiter, and a name or phone number only if you choose to give one.
Payments for plans: processed by Razorpay. We receive the subscription status, amounts and Razorpay's reference ids, never card or UPI details. Guests pay restaurants directly; staff only record whether it was cash, UPI, card or other.
Contact form: what you write and send us, plus a one-way, salted hash of your IP address used only to stop spam. We never store the IP itself.
Website analytics, only if you agree: a random id stored in your browser, the pages you visit on our website, the site you came from (its domain only), campaign tags in the link, and whether you signed up. Never on QR menus or inside the dashboard. See the cookie policy.
Technical logs: our hosting providers keep standard request logs (such as IP address and browser) for security and troubleshooting.
3. Why we use it
- To provide the service you signed up for: menus, ordering, kitchen and floor screens, billing, reports and team access.
- To take payment for plans and keep accounting records we're required to keep.
- To keep the service secure: sign-in, access controls, rate limits and spam checks.
- To reply when you contact us.
- With your consent only: to understand which pages of our website help restaurants decide.
4. The AI assistant
On plans that include it, owners and managers can ask questions about their numbers. Each question, the conversation so far and the venue's totals (sales, best sellers, busiest hours, settings) are sent to Hugging Face and the inference provider it uses to generate an answer. Guests' names and phone numbers are never sent. The conversation is kept only in your browser tab, not on our servers.
6. How long we keep it
- Business accounts, menus, orders and bills: while the business account exists, because restaurants need their records for tax and accounting.
- After a business account is closed: deleted within 90 days, except what we must keep by law (such as payment records).
- Website analytics: 13 months, or until you delete it from cookie settings.
- Contact messages: up to 24 months.
7. Your rights
You can ask to access, correct or erase your personal data, withdraw consent, and nominate someone to act for you. Owners and staff can edit their profile in the app. Guests should first contact the restaurant, which controls its order data; we'll help it respond.
Write to privacy@queueless.app. If you're not satisfied, contact our Grievance Officer, [Grievance officer name], at grievance@queueless.app. You may also complain to the Data Protection Board of India.
8. Security
Data is encrypted in transit. Each business's data is separated by access rules in the database itself, so one restaurant can never read another's. Payment details are handled by Razorpay, not by us. No system is perfectly secure; if a breach affects you, we'll tell you and the authorities as the law requires.
9. Children
Business accounts are for adults. Guests of any age may order at a restaurant; we don't knowingly collect more than an anonymous session and their order.
10. Changes
We'll update the date above when this policy changes and tell account holders about significant changes by email or in the app.