This notice explains how Some1, operated by Sintax Error Private Limited, processes personal and business information on our website, guest menus, venue and kitchen dashboards, and admin services. It describes the current product, not permission to collect anything we might build later.
Effective 1 November 2026 · Revision 2026-11-01.5
1. Who handles your information
Some1 operates the platform and handles account, service, billing, verification and security information. Each venue also handles the information it needs to serve its guests and manage its own business. Contact that venue about its food service and independent practices; contact Some1 about the platform or a data request. Our business and grievance details are on Contact & grievances.
2. What we collect, why and who can see it
The entries below describe actual features and their data use. You do not need to enable every feature. Public menu browsing, signed-in table ordering, voice, optional memory and venue billing use different information.
On-device table QR scanning
Information
If you tap Scan QR, your browser asks permission to use the camera. Camera frames are decoded locally in your browser to read a table link for the current venue. Frames are not uploaded, saved or sent to analytics.
Purpose
Let you rejoin a table after your table visit ends while retaining your sign-in. The camera stops on a successful scan, when closed, when you leave the page or when the page is hidden.
Access and choices
Local camera processing on your device only. The scanned venue/table link goes through the same authenticated table-joining checks as an ordinary QR link.
Synthetic platform voices and samples
Information
Approved synthetic voice IDs, original adult voice design descriptions, availability/default configuration, generated English/Hindi sample audio, provider usage evidence and administrator audit records; the selected voice identity and description pinned to each visit and voice session.
Purpose
Create and maintain reusable platform voices, let owners preview and choose an approved Expressive voice, and keep ongoing visits consistent. Voice generation and previews happen beforehand, without guest information or recordings of a reference person. Playing stored previews makes no new AI request. Existing voice credit rates and order-confirmation authority remain unchanged.
Access and choices
OpenAI processes voice-creation descriptions and synthetic preview scripts; Some1 infrastructure stores the catalogue and public sample assets. Authenticated venue staff choose approved voices and only platform administrators manage availability/defaults. Platform assets remain while operationally used; retirement/deletion does not promise immediate removal from provider records or backups. Prompt-generated voice creation is not eligible for OpenAI Zero Data Retention; provider retention limitations apply. Conversation API storage remains disabled, which is not a guarantee of zero provider retention. Voices are AI-generated and are not representations of a real person.
Opening venue reconciliation
Information
Venue-scoped historical receipt amount, covered statement period and cutoff, recorded receipt baseline, statement reference, owner explanation, approving account and time, and linked correction revisions.
Purpose
At an authorised venue’s request, separately identify historical receipts declared to precede Some1 tracking, reconcile a fixed statement baseline and carry the opening amount in later reports. Supporting item-level records may be unavailable. When the owner identifies the opening amount as historical sales paid by UPI, reports include it once in accepted sales and UPI receipts and label it before tracked activity in statements. It does not invent item details or order counts, create a new payment today, add guest credit, settle customer debts or verify individual bank transactions.
Access and choices
That venue’s authorised owner and Some1 operations only. Financial and audit records follow existing operational retention and deletion review. No new provider, marketing purpose or cross-venue sharing is introduced.
Guest credit at a venue
Information
Venue and authenticated guest account, available credit balance, actual money received, amount applied to a bill, credit added or used, and linked payment/staff audit records.
Purpose
Apply staff-confirmed excess payments to the same guest’s other pending bills at the same venue, oldest first where the guest’s share is established, and retain only the remainder as guest credit. Original receipts and linked bill settlements remain recorded without counting the money twice. Credit is separate from item sales and Some1 AI usage credits; it is not transferred between venues.
Access and choices
Authorised venue billing staff and Some1 operations for reconciliation. Credit and financial evidence follow existing billing retention and deletion review; reconcile remaining credit before deleting the account or venue. No new provider or marketing use is introduced.
Venue bill discounts and round-offs
Information
Signed adjustment amount, discount type/value and calculation base where applicable, bill reference, customer attribution, reason and optional note, authenticated staff name/account/email and recording time.
Purpose
Record authorised table discounts and small bill reductions or increases separately from actual Cash/UPI receipts, reconcile balances and show venue totals by reason, staff and customer. A round-off does not confirm that money was received.
Access and choices
Owner/cashier staff of that venue can record adjustments; authorised venue staff can inspect bill history and owners can inspect grouped reports. Guests see only their own applicable adjustment amount. Financial and audit records follow the operational retention and deletion review described below; they are not used for advertising or food memory.
Carry out a confirmed account deletion without changing unrelated venues or guests, prevent deleted accounts from being restored by delayed jobs, and retain evidence of the request.
Access and choices
The account holder and authorised Some1 operations staff; Clerk receives the guest sign-in deletion request. Required financial, dispute, consent and deletion evidence remains restricted. Shared files still used by another venue are preserved. These retained records are not used as guest food memory or for marketing.
Venue AI personalities
Information
Owner-entered profile names, conversational style instructions, selected enabled GPT-Live voice, safety-review model/version and time, and active selection.
Purpose
Save separate optional personality profiles, screen them before saving and apply the selected style and voice to new conversations without changing venue knowledge or platform rules.
Access and choices
Venue owners and authorised Some1 administrators; authorised kitchen staff can see the selected profile name and voice in voice settings, without its instructions. Submitted name/style is sent to OpenAI for safety review with API storage disabled; the selected style is included in GPT-Live conversation context. Owners can delete custom profiles; deleting the active profile selects Default for new conversations. The built-in Default cannot be deleted. Existing conversation snapshots and call history follow their existing session/diagnostic retention rather than being erased with a custom profile. Otherwise profiles remain until venue deletion. Automated review is not a safety guarantee. Do not enter secrets or private personal information.
Venue knowledge safety review
Information
Submitted venue knowledge, automated findings, review state, model/prompt version and review time.
Purpose
Help administrators identify unsafe instructions and prompt-injection attempts before reviewing an application. It is advisory and does not approve applications or guarantee safety. It does not run during guest conversations.
Access and choices
Some1 authorised administrators and OpenAI for automated analysis. Only the submitted knowledge is sent; registration contact fields, documents and map coordinates are excluded. API storage is disabled for this request; provider operational retention may still apply. Findings follow application operational-record retention and deletion review.
Notify the applicant about approval, requested information or a declined application. These are service messages, not marketing.
Access and choices
Some1 authorised administrators and infrastructure providers; Google Gmail processes the recipient and message to send email from the company account. Messages may remain in the sending mailbox and the recipient’s email service. Delivery records follow our operational-record retention and deletion review.
Venue map selection
Information
Selected venue coordinates saved with the application; IP address, browser request information and map areas sent directly to OpenStreetMap Foundation when the embedded map is opened.
Purpose
Display an interactive map so the owner can place and confirm the venue pin.
Access and choices
Some1 and its infrastructure providers store the application pin. OpenStreetMap Foundation receives map-image requests only when the owner opens the map, under its own privacy policy. Manual coordinate entry remains available without loading map images.
Policy agreements
Information
Authenticated account identifier and email, guest or venue policy audience, exact policy revision and notice, affirmative terms acceptance and privacy/data acknowledgement, the acceptance method, and server-recorded acceptance time. A temporary browser-session marker contains only the shown policy version and sign-in click time.
Purpose
Show the appropriate notice alongside guest sign-in or before continuing, remember your agreement, request a fresh agreement when the applicable revision changes, and document the agreement for support or a dispute. This is separate from optional memory or payment authorisation.
Access and choices
Some1 authorised administrators and our infrastructure providers. We do not collect an extra IP address or device fingerprint for this agreement. Agreement records are retained for account administration and applicable record or dispute obligations.
Account and sign-in
Information
Account identifier, name, email, profile photo and sign-in/security information supplied by your sign-in provider; required account name entered by manual email guests when their sign-in account has no name; your chosen display name and language; verified owner or guest phone number and verification time.
Purpose
Authenticate you, protect access, identify table participants and venue staff, and address account issues. Venue-account emails cannot be used for guest participation; use a separate guest email.
Access and choices
Some1 and our authentication/infrastructure providers. A venue you join can see the identity fields used in its guest and customer directory.
Phone verification
Information
Owner and guest phone number, verification time, and temporary provider request identifier and attempt count. WhatsApp or SMS codes are checked by MSG91 and are not stored in Some1.
Purpose
Confirm a contact number once and after changes; enable service, billing and dispute contact while keeping email sign-in.
Access and choices
Some1, MSG91 for delivery and verification, and infrastructure providers. Authorised staff at venues with an approved visit can see the guest’s current verified number. Other guests and unrelated venues cannot. Pending verification requests expire after fifteen minutes and are scheduled for deletion.
Table visits, orders and takeaway
Information
Venue and table identifiers, visit times, guest names, menu selections, quantities, modifiers, order notes, requests, requested item cancellations and replacements, kitchen decisions/reasons and authenticated decision-maker/time, order status and kitchen acknowledgement, bills and payment allocation/reference records. Staff must enter a takeaway customer's name or select a returning customer before submitting the order. For pending or waived takeaway balances, staff reuse a saved venue contact or the explicitly linked guest’s verified sign-in mobile for billing; if neither exists, staff save a customer-provided mobile as a venue-scoped billing contact. Names alone do not link a bill to an account. Staff-entered billing contacts do not change verified sign-in numbers. Staff can search saved counter contacts by name or by a mobile prefix of at least four digits. Payment corrections retain the previous amount/method, original receipt date, optional correction note and authenticated staff identity/time; corrected balances may remain pending or be explicitly waived.
Purpose
Send confirmed orders and requests to the correct team, show dashboard alerts and optional locally generated sound until staff respond, fulfil service, apply kitchen-approved changes together while preserving cancelled-item history, split or settle bills, prevent duplicate transactions and maintain venue records, contact customers about their bills and reconcile corrections without counting unpaid or waived amounts as money received.
Access and choices
Some1 and authorised staff of that venue. Guests see only their own orders, requests and applicable item-payment allocations, plus the name of the guest currently talking with their table’s host. Authorised venue staff retain the full table bill and can settle an individual guest’s items or the whole table.
Venue map location
Information
The venue's address and map pin are supplied during onboarding and may be edited by its owner. Guest phone coordinates are not requested or checked for table access.
Purpose
Identify the venue. Guests join by a valid table QR and authenticated account, subject to venue approval and opening controls.
Access and choices
Some1 and authorised venue staff process the venue details. Owners may optionally use their browser location to set their own venue pin; guests do not need location permission.
Owner dashboard assistant
Information
Owner-entered questions, optional microphone audio for transcription or live owner calls, live captions and verified report cards, temporary answers, limited venue-scoped operational records including guest display names, orders, bills and aggregate analytics, and credit/usage metadata.
Purpose
On the owner's explicit activation, answer operational questions about that owner's venue. The assistant reads records only; it cannot accept orders, alter payments or settings, or access other venues. Mic transcription fills an editable prompt; owners separately send questions. Optional Call Some1 is a separate read-only live conversation with the same owner and venue restrictions. Owners may request audio playback of a saved answer. Verify important answers against original records.
Access and choices
The authenticated venue owner and OpenAI for answering/transcription, with Some1 operational access. Customer contact fields and account identifiers are excluded from model context. Owner calls may save private diagnostic audio only after the displayed call notice is accepted while the venue setting is enabled. This setting initially displays as on and owners can turn it off before starting or in venue Settings. Audio is restricted to Some1 administrators for troubleshooting and improving Some1, kept for up to 7 days, and is not a venue playback library. Turning it off prevents new stored audio and queues deletion of existing diagnostic recordings; provider processing remains separate. This setting does not enable a model-training pipeline. Sent questions and answers are saved to the signed-in account for up to 24 hours so chat can resume across browser sessions, then scheduled for deletion. Each owner or authorised testing administrator can read only their own saved conversation at that venue. Financial, credit and security metadata follow ordinary operational retention. Provider processing/retention is separate. Successful answers use 1 shared AI credit and successful transcriptions use 1 more, even if not sent; failed operations release reservations. The text/transcription pilot has a 20-credit venue limit per IST day and can be switched off. Optional saved-answer playback is included without an additional user credit charge and does not enable the microphone. Live owner calls use OpenAI GPT-Live and the displayed time-based Expressive rate from the same venue voice balance, independently of text-answer charges. Live owner call transcripts and report cards are retained separately for up to 30 days as private account-and-venue call history; this history is not food memory or an order instruction. Venue users see text and duration, not audio recordings. Some1 administrator debugging access to this content follows the optional diagnostic setting. Scheduled expiry and account/venue deletion remove this temporary content; retained billing and supplier-cost records remain separate. The live display and stored transcript may differ from audio actually heard when interrupted or disconnected. Audio generation starts only on request. Provider processing and retention remain separate.
AI host and conversation
Information
Microphone audio while voice is active, transcripts, typed messages, assistant replies, recent conversation summaries, relevant menu/host context, consented preferences and order/tool results.
Purpose
Recognise speech, reply, recommend menu items, prepare orders for your confirmation and keep the current conversation coherent. AI responses can be wrong; confirm important details with staff.
Access and choices
Some1 and the AI/voice providers needed for the selected experience. Our application does not provide a permanent guest audio recording library; provider processing and retention are separate from our temporary text history.
Optional guest memory
Information
Preferences you enter, favourite items, language and food/drink preferences learned from what you explicitly say when memory is enabled; consent choices and the date from which history may be used.
Purpose
Personalise future suggestions at the selected venue. Account preferences can be reused across participating venues only when you enable that separate choice.
Access and choices
Some1 and the host serving you. Venue-specific preferences are shown to the team only when you choose sharing. Disabling memory does not remove the venue's ordinary order, customer or payment records.
Venue application and verification
Information
Applicant/account details, owner name, email, phone, business identity and address, selected venue type (café, restaurant, bar or club), registration/tax details where supplied, venue map pin, supporting business documents where requested, saved draft fields and current onboarding step, AI-prepared venue knowledge and pasted answer, optional manager name/phone, owner phone verification status/time, logo, review status and correspondence.
Purpose
Save progress to the signed-in account and resume later, verify the owner phone through MSG91 using WhatsApp or SMS, manually review the application, grant access, configure the venue and its type-specific wording and host context, and review evidence for sensitive identity changes. Business-document upload is temporarily waived for new onboarding; manual approval still applies. Provide optional manager contacts only with their permission. Free signup does not automatically activate a venue.
Access and choices
The applicant and authorised Some1 reviewers for private documents. Approved public venue identity, venue type, logo, menu and descriptions are visible to guests; approved host knowledge is available to the AI and may inform guest answers.
Venue operation and content
Information
Staff emails and roles, menu text/prices, confirmed food types, ingredients, spice and sweetness levels, allergens and images, tables, owner-selected host experience, service schedules, optional daily Expressive budget threshold and day-level used/reserved credit totals, and platform/venue availability settings, host settings, venue knowledge, character instructions, uploaded reference audio and rights confirmations, content revisions and administrative actions.
Purpose
Operate the venue workspace, configure guest service, produce authorised host style guidance, manage permissions and investigate changes.
Access and choices
Some1 and authorised venue staff according to role. Relevant content goes to AI providers for host features. Do not upload confidential material or audio you do not have permission to use.
Plans, credits, invoices and AutoPay
Information
Venue billing name/address/GSTIN, plan and price snapshots, credit purchases and usage, coupons, invoices, credit notes, payment/order/refund IDs and statuses. AutoPay also uses the owner's contact details, customer/token identifiers, consent time, threshold, refill amount and spending cap.
Purpose
Process authorised purchases, allocate and reconcile credits, attribute usage to visits/orders, issue billing documents, handle disputes/refunds and execute separately authorised automatic top-ups.
Access and choices
Some1, authorised venue billing users, Razorpay and payment/banking partners. Payment credentials are entered with the payment provider; Some1 does not ask for or store card numbers, CVV, UPI PINs or banking passwords.
Preserve unsettled bills when a table is released, alert the same venue's owner/cashier when an assigned account joins another visit, and require kitchen approval for new self-service orders while an assigned balance remains unpaid at that venue. Earlier and current balances are shown separately and together without recording the earlier debt as another sale. Location loss does not create an incident. There is no background tracking, shared cross-venue blacklist or automatic platform ban.
Access and choices
Only the venue's owner/cashier and authorised Some1 support review incident details; kitchen staff see the assigned unpaid amount needed to approve a new order. Guests receive their own pending-balance notice and can request correction from the cashier or Some1 contact page. Financial records follow the operational/dispute retention described below; resolved records do not require additional order approval.
Optional product analytics
Information
In an enabled guest menu unless turned off: broad menu/order/voice lifecycle events, a random in-memory session identifier, venue identifier, interface type, browser/device category, application version and broad error category. No names, contacts, account IDs, QR keys, search text, menu selections, order contents, prices, payment details, transcripts or audio are included.
Purpose
Measure menu usability, ordering funnels and voice reliability. Client observations are not financial records or authority for orders or payments.
Access and choices
Some1 authorised product operators and PostHog in the configured hosting region. Shared-project access is restricted to Some1 operators; venue filters are not access controls. Usage analytics starts on at enabled venues unless this browser has an off preference or sends a Do Not Track or Global Privacy Control signal. The guest can turn it off in Settings at the bottom of the menu without affecting service. Only an on/off preference is saved in this browser for Some1 menus until changed or site data is cleared; no analytics identifier is saved in browser storage. The random identifier lasts only for this menu. If browser storage cannot be read, analytics starts off; changes that cannot be saved last only for the current menu. Turning it off stops future collection and drops unsent events, but does not erase events already received by PostHog. The configured US PostHog Free plan has one-year event retention; provider deletion and backup limitations apply. Session replay and heatmaps remain disabled pending a separate privacy and performance review. PostHog receives normal network connection metadata such as IP while handling requests; application event geolocation enrichment is disabled.
Customer directory and venue analytics
Information
Guest identity/contact/profile fields, first and recent visit dates, visit counts, orders, fulfilment, sales, collections and voice usage/order attribution.
Purpose
Let the venue recognise returning guests, find a customer for takeaway, understand its performance and reconcile service costs. These operational records are separate from optional AI memory.
Access and choices
Authorised staff access their venue's directory; the venue owner accesses its analytics. Some1 administrators can access necessary operational records for support and platform administration. Other venues do not receive that venue's directory.
Enquiries, reliability and security
Information
Enquiry name, business, industry, city, contact and message; service usage counts, supplier cost records, provider request IDs, trial consent version, model/voice IDs, token totals, billed transcription duration when supplied, submitted speech-character counts, preview completion status, latency/error/tool metrics, audit records and infrastructure request/security logs such as network/device information.
Purpose
Respond to enquiries, diagnose service failures, enforce quotas, prevent misuse, account for costs and improve reliability. Performance diagnostics do not require storing the content of each conversation. At venues with private access troubleshooting enabled, seven-day voice access logs link the signed-in account name to a browser/platform category, permission result, error category, timing. These client reports help investigate failures and do not prove physical attendance. They contain no exact guest GPS coordinates or audio recordings.
Access and choices
Authorised Some1 personnel and relevant hosting, database and authentication providers; venue users see the operational summaries permitted for their role. Private access troubleshooting logs are visible only to that venue’s owner and authorised Some1 administrators and are scheduled for deletion after seven days.
3. Your choices and sensitive information
Memory is optional. Use Your usual & preferences and your guest profile controls to review or change saved preferences, switch off learning, and control cross-venue use or sharing with staff. Turning memory off clears the saved preferences for the control you changed and stops future preference learning there; the account and venue-specific controls are separate. It does not erase invoices, past orders, ordinary customer directory entries or temporarily retained conversation text.
You can stop voice or revoke microphone permission. Guest table access does not request location permission. Features that require that information may then be unavailable. Optional personalisation is not required to order manually. Browser permission is not permission for advertising or unrestricted future data use.
Avoid entering passwords, payment secrets, government identity numbers or another person's private information into the AI host. Tell staff directly about allergies and safety-critical needs. If you put health or other sensitive information in an order note or conversation, it must be processed to handle that message; our preference summarisation is instructed not to learn health, allergies, religion or other sensitive traits as lasting preferences. This is not a guarantee that AI will never make an error.
For venue verification, upload only relevant business evidence and redact unrelated personal details where possible. Do not submit unmasked Aadhaar or full payment credentials when they are not required. For reference voices, obtain the speaker's permission before upload.
4. Service providers and transfers
Our current infrastructure uses Clerk for email authentication, MSG91 for phone verification and WhatsApp (Meta) when that delivery channel is used, Convex for application data/functions/storage and Railway for application hosting. OpenAI processes AI, transcription and host requests. When a venue chooses Fluent, Sarvam processes microphone audio, transcriptions, relevant venue/menu information, authorised guest context, tool messages and generated speech after separate voice agreement. Known guest and venue names may also be temporarily sent to Sarvam’s transliteration API for pronunciation in the conversation language, with a conversation-local cache and timeout fallback; no permanent name dictionary is created. OpenAI safety checks still apply. Some1 retains request identifiers, reported token/audio-duration usage and speech-character estimates for debugging and supplier-cost reconciliation; these are not final supplier invoices. Voice preview requests record the staff account, selected voice, character count, request ID and completion status. No additional raw-audio archive is created by Fluent. The configured account’s model-training setting has been turned off, but Sarvam’s account-specific API retention period is not yet confirmed. We have requested clarification from Sarvam; there is no zero-retention or immediate-deletion assurance for this service. Provider retention is separate from Some1 transcript/diagnostic deletion. ElevenLabs may process voice requests and authorised reference audio if that optional integration is enabled for a deployment. Razorpay and its banking/payment partners process payments and mandates when you choose them.
We share the context needed to provide the requested feature, and information needed for support, security, legal obligations and dispute handling. Infrastructure providers may process technical request/device/network logs. Processing can occur in India or other countries under the relevant service arrangements; we do not represent that all platform or AI data stays in India.
Some1 does not sell personal data or use the current product's guest data for advertising profiles. We do not operate a guest-data model-training pipeline. AI providers have their own contractual data handling and security retention; do not assume every provider request has zero retention. Our AI requests use the configured business/API services, and a provider's separate notice also applies to its own account, security and payment processing.
If law requires disclosure, we limit it to the applicable request. A business restructuring may involve necessary records subject to confidentiality, applicable law and notice where required. A new unrelated purpose or material provider/data-use change requires review and the notice or consent required by law.
Owners can permanently close a venue from Settings → Danger zone after closing visits, settling active usage and resolving payment/refund reviews and automatic top-up cancellation. Confirm the exact venue name, type DELETE, choose a reason and acknowledge the notice. The workspace closes immediately while scoped background cleanup removes its operational content, team access, application and unshared uploads. Guests retain their own personal food preferences and served-meal history; another venue or guest account is not deleted. The owner sign-in remains available for other venues or a fresh application. Deletion cannot restore a closed venue.
Guests can choose Delete your account below the QR menu. After open visits are closed, confirming DELETE removes the guest profile, saved food preferences, conversation memory, verified phone and personal dining history across Some1, then removes the guest sign-in identity. Necessary service/payment records are de-identified or restricted where retention is required. Deletion does not erase debts or cancel payments. Background cleanup and identity-provider outages can delay completion; support can review an unfinished request.
Voluntarily deleting a venue permanently ends its Pro access and forfeits remaining included and purchased credits after the explicit deletion acknowledgement. There is no ordinary change-of-mind refund after voluntary deletion; request any unused-credit refund review before deleting. Pro and credits cannot be transferred to another account or venue. This does not limit refunds or remedies required by law. Required invoices, payment/refund/mandate ledgers, consent and deletion evidence, and records needed for disputes remain restricted; provider logs, sent email and backups follow their retention cycles. We do not promise immediate erasure from every provider or backup.
Different records have different lifetimes. The current application schedules conversation threads and their visit summaries for deletion after approximately 24 hours from thread creation, retains only bounded recent context while active, and schedules voice performance diagnostics for removal after seven days. Private uploaded verification files are scheduled for deletion 365 days after upload. Scheduled jobs and provider backups can mean removal is not instantaneous.
These time limits do not apply to the underlying order, invoice, wallet ledger, payment, consent, audit or customer records. Optional preferences remain until changed/disabled or removed through a verified request. Venue content, staff configuration and operating history remain while needed to provide and administer the venue service.
The current product does not apply one automatic expiry to every order, customer record, application metadata or saved draft, lead or financial entry. We assess deletion requests and keep records only while needed for the disclosed purpose, legal accounting/record obligations, security or an active dispute. Where deletion is restricted, we explain the applicable reason. Copies in provider backups and provider-held records follow their own deletion cycles; we do not promise immediate erasure from every backup.
Venue map selection
When you choose to open the embedded venue map, your browser requests map images from OpenStreetMap Foundation. The provider receives your IP address, browser request information and the map areas viewed. Some1 saves the venue coordinates you select in your application draft; moving the pin requires you to confirm its final position. You may enter coordinates manually without opening the map.
Verified contact numbers
Owners verify a phone number during venue onboarding. Guests verify a phone number after their first email sign-in. MSG91 receives the number and verification request to deliver and check a code through SMS or WhatsApp (Meta), according to the delivery channel configured for the verification service or the retry channel you request. Entering a complete supported mobile number may start verification automatically. Email remains the sign-in method; verification repeats when the number changes. We keep the verified number and verification time with your account. Pending verification requests expire after fifteen minutes and are scheduled for deletion; we do not store the verification code.
Authorised staff at venues where you have an approved visit can see your current verified phone number for service, billing and dispute resolution, including after the visit. Staff-printed venue bills may include customer names and verified mobile numbers for billing; the venue is responsible for handing these receipts to the appropriate customer. Other guests and unrelated venues cannot see it. It is not added to food memory or sent to the AI host, and this collection does not authorise marketing. A changed number becomes visible only after successful verification. Account and operational contact records remain subject to the retention and rights described in this policy.
6. Cookies, security and reliability
When you choose Scan QR, browser camera permission is used only to decode your table QR on this device. Camera frames are not uploaded, stored or sent to analytics. Close the camera or leave the page to stop it. Scanning does not sign you out or bypass table approval.
Sign-in and service providers use necessary cookies or similar browser storage for authentication, fraud prevention and payment sessions. The application does not install advertising pixels. Venue operational analytics comes from the venue's own records. At enabled venues, PostHog product analytics starts on to measure usability using random in-memory identifiers, unless disabled through the menu footer’s Settings or browser privacy signals. An on/off preference is saved locally in this browser, separate from any analytics identifier. This is an opt-out setting, not a recorded affirmative consent to analytics. Screen recording and heatmaps are disabled. See Optional product analytics in the data inventory. A guest sign-in click stores the policy version and click time in browser session storage so the agreement can be recorded after authentication. The marker is accepted for fifteen minutes and removed after the agreement is confirmed; if unavailable or expired, a visible Agree & continue notice is shown. Blocking necessary storage can prevent sign-in or payment. Kitchen sound alerts are on by default when browser audio permissions allow; the mute preference is stored locally in that browser and can be changed in Settings.
We use access controls, authenticated staff roles, private document access, encrypted network connections and bounded service permissions. These measures reduce risk but no service is completely secure. Report suspected exposure through our contact page without sending passwords, card details, UPI PINs or full identity documents. We investigate incidents and provide notifications where applicable law requires them.
7. Access, correction, withdrawal and complaints
You can request information about your data, correction of inaccurate details, withdrawal of optional consent, or deletion where applicable. Contact our privacy/grievance contact with the email associated with your account, the venue and a brief description. We may ask for proportionate verification to protect your records; do not send identity documents unless we request a secure method. A venue-directed request may require cooperation with that venue.
Withdrawal stops the relevant future optional use; it does not invalidate earlier lawful processing or remove records we must retain. We acknowledge grievances within 48 hours and aim to resolve them within one month, or an earlier deadline where applicable law requires. We will explain delays and any lawful limit on a request. You may also approach the relevant regulator, consumer forum or authority under the provisions available to you.
This notice is intended to operate with applicable Indian privacy and consumer law, including the Information Technology Act and applicable rules, and the Digital Personal Data Protection Act and Rules as their provisions come into force. Publication of this notice is not a claim that every provision is already in force or a certification of compliance.
8. Children and policy changes
Some1 accounts and purchases are intended for adults aged 18 or older. We do not seek to collect children's data or provide behavioural profiling of children. A parent or guardian who believes a child has supplied personal data should contact us so we can investigate and remove it where required.
We publish an effective date and revision for policy changes. Guests are shown linked Guest Terms and this Privacy & Data Policy beside sign-in. Continuing confirms they are at least 18, accept the terms and acknowledge the privacy/data notice; we record the agreement after authentication. If that sign-in action cannot be recovered, guests review a notice and choose Agree & continue. Venue users continue to use unchecked agreement boxes. We save the policy version, original notice, account identity and acceptance time; a material update to an applicable revision prompts a new agreement. Material new purposes require appropriate notice and consent where required before that use starts. Updating this page does not itself opt you into memory, marketing, AutoPay or an unrelated new feature. Previous published versions remain in our release records and can be requested from support.
