This Privacy Policy explains how BiteSlot ("we", "us", "our"), based in Ahmedabad, Gujarat, India, handles data in the BiteSlot Captain mobile application for Android (package com.biteslot.pos, the "App"). It supplements our main Privacy Policy and Data Processing Addendum, and is published under India's Information Technology Act, 2000 and the Digital Personal Data Protection Act, 2023 ("DPDP Act"). Where the two differ regarding the App, this policy governs.
1. Who uses the App
BiteSlot Captain is a business tool used by the staff ("Operators") of a restaurant that holds a BiteSlot account ("the Restaurant"). It turns a phone or tablet into a waiter-ordering and point-of-sale terminal. The App is intended for users aged 18 and over and is not directed at children. We do not knowingly collect personal data from children.
2. Controller and processor roles
For data that the Restaurant records about its own diners through the App — an End-Customer's name, phone number and delivery address ("End-Customer Data") — the Restaurant is the data fiduciary (controller) and BiteSlot is its processor, acting only on the Restaurant's instructions under our Data Processing Addendum. For Operator sign-in and diagnostic data, BiteSlot is the data fiduciary. If you are an End-Customer, please direct privacy requests to the Restaurant first; we will assist it in responding.
3. What the App collects
Account and identity. An Operator's email address and password (used to sign in via our secure API), a 4-digit operator PIN, and the device activation (licence) that binds the terminal to a Restaurant and branch. The PIN is stored on the device only as a keyed cryptographic hash (HMAC) — never as a plaintext PIN. The sign-in token, device identifier and activation record are held in the device's encrypted operating-system keystore.
A device identifier. A random identifier the App generates for this installation. This is not your phone's hardware ID, IMEI, MAC address or advertising ID. It is used to keep the terminal activated and to label diagnostics.
End-Customer Data (entered by Operators). Customer name, an optional phone number (used to look up returning customers), and — for delivery orders — a delivery address and optional landmark. This is used to produce bills and receipts and to fulfil delivery orders.
Operational data. Orders, items, kitchen tickets (KOT), bills, payment method and amounts (including cash-on-delivery), tables, menu, shifts and collection totals. This is stored on the device so the App works offline, and synced to our servers.
Diagnostics and usage. Crash and error reports, performance signals, and in-app screen and interaction data, used to keep the App reliable and to improve it.
4. Analytics and session replay (Microsoft Clarity)
In production builds, the App uses Microsoft Clarity to understand how Operators use the App and to diagnose problems. This includes session replay of on-screen interactions. We have engineered strong privacy safeguards around it:
- Clarity is configured with Strict masking, and the App additionally masks every field that could contain credentials, payment amounts or End-Customer Data, so those values are never recorded.
- Only non-identifying business identifiers (device, operator, restaurant and branch IDs, and the app version) are attached to a session as tags. We never attach customer names, phone numbers, amounts, PINs or tokens.
- Clarity is disabled in development builds and runs only on the released app.
Microsoft processes this data as our service provider. See Microsoft's privacy statement for how it handles the data it receives.
5. Permissions the App requests
- Internet & network state — to communicate with BiteSlot servers and to detect when the device is offline.
- Bluetooth (connect & scan) — used solely to discover and print to a portable thermal receipt/KOT printer. Bluetooth scanning is declared with the
neverForLocationflag; the App never derives, uses or collects your physical location.
The App does not request access to your location, camera, microphone, contacts, SMS, or your photos and files.
6. How we use data
- To operate the App: authenticate Operators, keep the terminal activated, and take and sync orders, bills and KOTs.
- To print bills, receipts and kitchen tickets.
- To keep the App reliable and secure — crash and error diagnostics, abuse prevention and troubleshooting.
- To understand and improve how the App is used (analytics).
- To comply with law and enforce our agreements.
We rely on your consent and on the legitimate uses recognised by the DPDP Act. We do not sell personal data and we do not use it for third-party advertising.
7. How data is shared
We share data only with the service providers needed to run the App:
- Cloud hosting and infrastructure (primarily in India) — stores and syncs your operational data.
- Microsoft Clarity — analytics and session replay, as described in Section 4.
- Google Play — delivers in-app updates. No personal data is shared for this.
Subscription renewal payments are completed by Razorpay in your device's web browser; the App itself does not collect or store card or bank details. We may disclose data where required by law, or to a successor entity in a business reorganisation (in which case this policy continues to apply).
8. Where data is stored and how we protect it
Data is transmitted over TLS/HTTPS and hosted primarily on servers located in India. Operator credentials and tokens are held in the device's encrypted OS keystore, and on-device operational data is kept in the App's private storage. We apply access controls and least-privilege administration, rate limiting and abuse protection, audit logging and regular encrypted backups. No system is perfectly secure; if we become aware of a personal-data breach affecting you, we will notify you and the authorities as required by the DPDP Act.
9. How long we keep data
On-device data is cleared when the terminal is deactivated or signed out, or when the App is uninstalled. Server-side operational and account data follow the retention tiers set out in our main Privacy Policy — broadly, while your subscription is active, with a defined post-cancellation export-and-deletion window, except for invoices and financial records that law requires us to keep.
10. Your rights and how to delete your data
Under the DPDP Act you may access a summary of your personal data, correct or update it, request its erasure, nominate someone to exercise your rights, and withdraw consent at any time.
To request deletion of your data, see our App Data Deletion page or email hello@biteslot.com. If you are an End-Customer of a Restaurant, please contact that Restaurant first (it is the data fiduciary for your data); we will assist it. If you are not satisfied with our response, you may complain to the Data Protection Board of India.
11. Changes to this policy
We may update this policy from time to time. We will post the updated version here with a new "Last updated" date and, for material changes, notify account holders by email or in-app notice.
12. Grievance Officer and contact
Grievance Officer — BiteSlot
Email: hello@biteslot.com
Phone: +91 81407 57973
Address: SF/16, Surdhara Complex, Nikol Gam Rd, Khodiar Nagar, Ahmedabad, Gujarat 382350
We acknowledge privacy grievances within 72 hours and aim to resolve them within the timelines prescribed by applicable law.