NOTICE VERSION 2026-10-18.1
Development draft — not ready for public launch. The operator’s legal identity, privacy contact and address must be configured and the data inventory, retention and vendor arrangements reviewed before publication.
This notice explains the V2 restaurant platform’s use of personal information. Restaurant owners also need to identify their restaurant and provide an accurate notice for their customers before V2 ordering launches.
Platform operator: not configured yet
The platform manages restaurant owner accounts and subscriptions. Restaurants use the service to manage their customers’ orders. Responsibility for each purpose must be set out in the restaurant agreement; hosting data does not by itself decide the legal roles.
| Information | Purpose |
|---|---|
| Owner name, email and password hash | Create, secure and administer the owner account. Passwords are not stored in plain text. |
| Restaurant identity, logo, address, contact details, service hours and menu | Configure the restaurant and its preview. Details intentionally published by the owner may be visible to guests once public ordering is available. |
| Subscription plan, amount, transaction reference and review result | Verify subscription payments and maintain subscription records. We do not ask for UPI PINs or bank passwords. |
| Accounts ledger events: bill/source references, amounts, methods, payment decisions, refunds, timestamps and recorded actor | Maintain restaurant operational records, reconcile verified collections and provide owner reports/exports. Unverified payment reports are recorded separately from received funds. |
| Sign-in attempts and administrative actions | Protect accounts, investigate misuse and record important changes. Hosting providers may also maintain access and security logs. |
| Privacy receipt, notice version, choices and timestamps | Remember and record your privacy choices. The privacy ledger does not record your IP, name, phone or account ID. |
V2 ordering is still being developed. Its customer notice must explain the actual collection of order details, table sessions, optional dine-in name/phone, required takeaway contact details, payment reports and feedback before that flow is published. Order information must not automatically become a marketing contact list.
| Storage | Use and duration |
|---|---|
| Restaurant/platform session cookies | Essential sign-in and session access; normally session cookies. |
| Basket in sessionStorage | Essential cart contents in the restaurant ordering interface, retained for the browser tab’s session. |
| v2_privacy_guard (with __Host- prefix on HTTPS) | Essential security token for saving a privacy choice; up to 180 days. |
| privacy-denied:… in localStorage | Essential deny-only safety marker when saving fails; stays until a successful choice is saved or browser storage is cleared. |
| v2_privacy_choice (with __Host- prefix on HTTPS) | Signed privacy preference receipt; up to 180 days or until replaced. This is a product setting, not a legal retention requirement. |
Optional analytics: not enabled. Advertising tools: not enabled. If optional tools are introduced, this notice must name the providers, purposes, data and lifetimes before enabling them.
There is no advertising or analytics SDK in the current module. Clicking an external UPI or Google review link opens a separate service governed by its own notice.
You can refuse optional tracking and still use the service. Open to change or withdraw optional choices. Changing cookie settings does not cancel an order or subscription.
You may ask for information about personal data processing, correction, erasure, withdrawal of consent, grievance review or nomination, subject to applicable law and necessary verification. Contact the responsible operator below; do not send passwords, UPI PINs or identity documents in your first message. We will request only proportionate information needed to identify the records and prevent disclosure to someone else.
A working privacy/grievance contact must be configured before launch. This draft does not provide an operational request channel yet.
Raise grievances with the responsible operator first. Where available under the applicable DPDP framework, you may use the Data Protection Board’s official complaint mechanism after the required steps. We do not collect or submit Board complaints through this website.
Account, transaction, security, consent and backup records have different purposes and retention needs. Applicable accounting, security, dispute and other legal requirements may require records to be retained after a request. The final retention schedule and deletion procedures are still being configured; no automatic deletion deadline is promised by this draft.
Hosting and contracted service providers may process data to operate the service. A reviewed vendor list, hosting locations, access controls and processing agreements must be completed before release. We do not sell personal information through this module.
The owner account is intended for adults representing restaurants. Do not use a child’s personal information to register. V2 does not yet implement verified parental consent for children’s personal data; a simple age checkbox would not establish it. That workflow must be addressed before introducing a service that requires it.
If you need this notice explained in another language, contact the privacy team. Language access must be provided as required; this English draft is not a complete multilingual implementation.
This module supports privacy controls. A cookie banner alone does not establish compliance with the Digital Personal Data Protection Act. The Act and Rules have phased commencement and the operator must assess its applicable obligations.