Privacy Policy

QueueWho is provided by Monika Sharma, trading as QueueWho, a sole proprietorship, with its registered office at 40, Krishna Enclave, Lane 7, Subhash Nagar, Dehradun, Uttarakhand 248002 (“we”, “us”). This policy is published under the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025, and the Information Technology Act, 2000 and the rules made under it.

We are the Data Fiduciary, and this policy applies, for the personal data of:

• restaurant owners and the people who sign up or are invited to manage a restaurant;
• restaurant staff who sign in to the console (owners, managers, cashiers, waiters, kitchen staff);
• our own platform administrators and support team;
• people who visit this website or contact us.

Guests who order at a restaurant are covered by the privacy notice for guests. For guest data the restaurant is the Data Fiduciary and we are its Data Processor, under the Data Processing Agreement.

• Name, work email address, mobile (WhatsApp) number

  Whose: Owners, staff, admins

  Where it comes from: The invitation sent by an owner or manager, or by us when a restaurant is set up

• Password (stored only as a one-way hash), two-factor secret (encrypted), passkeys, shared-device PIN (hash only)

  Whose: Owners, staff, admins

  Where it comes from: You, when you set them

• Role, outlets you work in, invitations, shift clock-in and clock-out times

  Whose: Staff

  Where it comes from: The restaurant's owner or manager, and you

• Sign-in records: IP address, browser, time of sign-in and last activity

  Whose: Everyone who signs in

  Where it comes from: Your browser, automatically

• Activity records: who did what and when (for example a refund, a price change, a data download)

  Whose: Owners, staff, admins

  Where it comes from: Your use of the console

• Restaurant business details: legal name, address, phone, GSTIN, FSSAI licence number, UPI ID, payment gateway keys (encrypted)

  Whose: Owners (personal data where the restaurant is a sole proprietorship)

  Where it comes from: The owner

• Subscription and billing records

  Whose: Owners

  Where it comes from: Our billing

• Messages you send us and our replies

  Whose: Anyone who contacts us

  Where it comes from: You

• Technical data: IP address, browser type, pages requested

  Whose: Website visitors

  Where it comes from: Your browser, automatically

• To create and secure accounts, sign you in, and keep accounts safe (two-factor sign-in, locking after repeated failed attempts).
• To provide the service the restaurant subscribed to: orders, kitchen display, billing, reports, staff management.
• To keep an accountable record of sensitive actions, which helps restaurants prevent fraud and settle disputes.
• To bill for the subscription, keep accounts and tax records, and meet legal obligations.
• To provide support when you or your restaurant ask for it.
• To detect, prevent and investigate security incidents, abuse and fraud.
• To send service emails: invitations, password resets, security alerts, and notices about the subscription. We don't send marketing emails without your consent.

• Consent, which you give when you accept an invitation or contact us, and can withdraw at any time. Withdrawing consent to sign-in data means the account can no longer be used.
• Legitimate uses under section 7 of the DPDP Act: data you provide voluntarily for a specified purpose, compliance with law (for example tax and accounting records), and, for staff, purposes related to employment that the restaurant, as your employer, needs (such as shift records and preventing loss).

We do not sell personal data or share it for advertising. We share it only:

• within the restaurant: owners and managers see their staff's names, roles and activity;
• with the service providers below, under contracts that limit them to our instructions and require them to protect the data;
• with a payment gateway, only through the restaurant's own gateway account;
• with authorities, when the law requires it, for example on a lawful order from a court, the police, CERT-In or the Data Protection Board;
• with a buyer or successor, if our business is transferred, on the same terms as this policy.

• Amazon Web Services (or the hosting provider named in our records)

  What for: Hosting the application, its database and uploaded files

  Data: All data held on the platform, including uploaded photos and videos

  Where: Australia (Sydney)

• Cloudflare, Inc.

  What for: Content delivery, DNS, protection from attacks, the bot check on some forms, backup storage (if used)

  Data: IP address, browser details, pages requested; encrypted backups if backup storage is used

  Where: Global network (including outside India)

• The payment gateway the restaurant chose: Cashfree, Razorpay, PhonePe, PayU or Paytm

  What for: Taking online payments and refunds (the restaurant's own gateway account)

  Data: Guest's mobile number, name (some gateways), order amount and reference; card or UPI details are entered on the gateway's own page and never reach us

  Where: India

• MSG91 (Walkover Web Solutions Pvt. Ltd.)

  What for: SMS: one-time codes, order updates and, with consent, offers

  Data: Mobile number, message text, restaurant name, guest's first name

  Where: India

• Meta Platforms (WhatsApp Business Cloud API), if the restaurant uses WhatsApp

  What for: WhatsApp messages: one-time codes, order updates and, with consent, offers

  Data: Mobile number, message text, restaurant name, guest's first name

  Where: Outside India

• Resend

  What for: Email: invitations, sign-in and password emails, receipts a guest asks for, alerts to owners

  Data: Email address, name, email text

  Where: United States

• Google (Gemini and Veo) or Anthropic (Claude), whichever the platform uses

  What for: AI features: reading menu photos, writing dish descriptions and translations, the menu assistant

  Data: Menu photos and text, sales figures for reports; the text a guest types into the menu assistant

  Where: United States

• Sentry (Functional Software, Inc.), if enabled

  What for: Finding and fixing software errors

  Data: Technical error reports, with names, numbers, cookies and secret links removed

  Where: United States or European Union

Our database and files are hosted by Amazon Web Services in Australia (Sydney). Some other providers listed above (email, AI, error monitoring and parts of Cloudflare's network) also process data outside India. Section 16 of the DPDP Act allows this except to countries the Government of India restricts by notification; we will stop any transfer to a restricted country.

• Account details (name, email, sign-in methods)

  Kept for: While the account is active. Deleted within 90 days after the account is closed or the person leaves all restaurants, unless needed for a legal claim

• Sign-in sessions

  Kept for: Until sign-out, or 14 days (shorter for administrators)

• Security logs (IP address, browser, pages requested)

  Kept for: 1 year, as the DPDP Rules and CERT-In directions require, then deleted

• Activity records of sensitive actions

  Kept for: As long as the restaurant's billing records: at least 72 months from the due date of the GST annual return for that year

• Subscription invoices and accounting records

  Kept for: 8 years, as tax and company law require

• Restaurant data after the subscription ends

  Kept for: Available for export for 30 days, then deleted within 90 days, except records the law requires to be kept

• Backups

  Kept for: Up to 30 days

You can ask for a summary of your personal data and who it was shared with, have it corrected, completed, updated or erased, withdraw consent, have a grievance resolved, and nominate someone to act for you if you die or can't act (DPDP Act sections 11 to 14).

Email [email protected] from the email address of your account, or use your account page for sign-in settings. If you work at a restaurant, some records (such as who settled a bill) belong to the restaurant's business records and may need to be kept; we will tell you if so, and why. We acknowledge requests within 24 hours and resolve them within 15 days, never later than 90 days.

• Encrypted connections (HTTPS with HSTS) and a strict content security policy.
• Passwords hashed with Argon2; two-factor secrets and payment keys encrypted; administrators must use two-factor sign-in, and owners need it to change payment settings.
• Each restaurant's data separated by row-level security in the database; staff see only what their role allows.
• Support access needs the restaurant's permission, is limited in time and scope, hides guest details unless allowed, and is logged.
• Append-only activity logs that the application itself cannot alter.
• Daily backups, kept off the server, with restores practised.
• A written plan for responding to security incidents and personal data breaches.

If a breach affects your personal data, we will tell you without delay, in plain language: what happened and when, the likely consequences, what we are doing about it, what you can do to protect yourself, and who to contact. We will report it to the Data Protection Board of India as the DPDP Rules require (an initial report without delay and a detailed report within 72 hours), and to CERT-In within 6 hours where its directions apply. Where the breach concerns guest data, we inform the restaurant straight away so it can meet its own duties.

Console accounts are only for people aged 18 or over. We don't knowingly collect children's personal data for our own purposes, and we don't track or profile anyone for advertising.

We use only the cookies needed to run the service: no advertising or analytics cookies. See the Cookie Policy.

If you are not satisfied with our answer, you can complain to the Data Protection Board of India. See Grievance redressal for the full process.

We will post any change here with a new version and date. If a change affects how we use your data in a significant way, we will tell account holders by email at least 30 days before it takes effect, and ask for fresh consent where the law requires.