Privacy policy

1. What data we collect

Restaurant owners and managers

• Account identification: Your name, email address, mobile phone number, and a securely hashed password.
• Restaurant profile: Business name, city, web address (subdomain), UPI ID for guest payouts, and branding (logo/colors).
• Operational records: Digital menu items, floor tables, team member profiles, order history, payment summaries, and platform wallet activity.

Restaurant staff (waiters and kitchen team)

• Staff profile: Name, assigned role (waiter, chef, or manager), internal staff ID code, and secure login credentials.
• Service activity: Assigned tables, tickets acknowledged, orders served, and assistance requests received.

Dine-in guests

• Table session data: The table number, active table session ID, items, special instructions notes, and customizations ordered, order status, and bill total. Special instructions are stored with the order items only, are never attached to guest profiles, and follow the same retention and deletion schedule as order records.
• Name and mobile phone number: When a guest provides their name or mobile number (for example, when a restaurant requires mobile verification before ordering, or for digital receipt delivery).
• One-time verification codes (OTP): Temporary numeric codes sent via SMS or email to authenticate accounts or verify orders. Once verified or expired, OTP codes are invalidated immediately.
• Feedback and ratings: Optional star ratings and private feedback comments submitted at the conclusion of a dining visit.
• Shared tables: When several guests order together at one table, the first guest to verify their email becomes the host of that table session and is the only one who sends orders to the kitchen and requests the bill. Other guests join with a display name of their choosing — no email or phone number is required of them — and a cookie holding a random token (stored only as a cryptographic hash) that keeps their device recognised for that one session. Guests at a shared table see only each other's first names and which items each person added; they never see another guest's email address or phone number. Royal Points for a shared table are earned by the host who settles the bill, even where a restaurant lets other verified guests place their own orders onto the same bill.

Payment credentials: Neario Dineout does not collect, process, or store credit card numbers, debit card numbers, or net banking passwords. Diners pay restaurants directly using their chosen UPI app or in-person cash.

2. Why we collect this data and how it is used

• To deliver the dine-in service: Accurately dispatching table orders to the kitchen display, notifying assigned waiters when food is ready, and calculating itemized bills with applicable restaurant taxes.
• To authenticate sessions and protect security: Verifying owner and staff logins, preventing unauthorized orders, and ensuring table isolation so diners only see their own bill.
• To run the platform wallet: Deducting the ₹2 per bill platform fee, tracking welcome credits and promotional coupons, and verifying the wallet recharges restaurants pay us (including the UTR and any payment screenshot they submit).
• To provide customer support: Assisting restaurants and guests with technical inquiries, billing queries, and important system operational notices.

3. Who we share your data with

Guest orders, items, and billing totals are directly shared with the specific restaurant where the order was placed. We do not sell, rent, or trade personal data to data brokers or third-party advertisers.

We work with trusted technical infrastructure providers strictly necessary to operate our service (such as cloud database hosting and transactional SMS/email delivery providers). These partners process data solely under strict confidentiality instructions.

4. Data retention and deletion

• Active accounts: Restaurant owner and staff account information is maintained as long as the restaurant remains active on Neario Dineout.
• Order & billing history: Completed guest orders and itemized financial records are retained for accounting, taxation, and platform fee settlement purposes in accordance with Indian commercial record-keeping regulations.
• Temporary verification state: OTP codes expire within minutes. Ephemeral session tokens (such as active guest table cookies) expire automatically within 12 hours.
• Shared table sessions: Display names chosen by guests who join a shared table, the device tokens that bind them to that session, and the table's join code are erased as soon as the table's bill is settled and the session closes. What remains afterwards is the order and billing history above, which records only which items were ordered — not who at the table added them.

5. How to request data deletion

Under applicable Indian data protection law (including the Digital Personal Data Protection Act), you have the right to request access to your personal data, request correction of inaccurate records, or request deletion of your information when it is no longer required for legitimate business or legal obligations.

To request deletion of your data or account, send an email to info@neariodineout.in with the subject line “Data Deletion Request”. We will process and confirm your request within 30 days.

6. Cookies and local storage

We use strictly necessary cookies to keep your session authenticated and secure, and privacy-respecting local storage for items like notification mute preferences. For a full breakdown of every cookie and storage key we use, please see our dedicated Cookie policy.

7. Contact us

For any privacy questions, concerns, or data requests, please write to: