QueueBill privacy policy

Who we are

QueueBill is a token billing, Bluetooth receipt printing, and QR tracking product for small food counters. For privacy questions, contact QueueBill at queue.bill.in@gmail.com.

Data QueueBill handles

• Google sign-in data such as display name, email address, Firebase Authentication user ID, and sign-in state used to create and maintain the QueueBill app account identity.
• Store profile data such as business name, logo text, brand color, support phone, social links, Google account email used for setup, and public customer-facing links.
• Counter operation data such as menu items, categories, orders, token numbers, order status, payment method/status, reports, queue state, and print status.
• Device data such as local device ID, local app settings, printer settings, Google sign-in state, and Customer Live Tracking setup status.
• Tracking setup data such as spreadsheet ID, tab ID, read mode, enabled state, account email, last sync status, and last sync time.
• Menu import data, including menu photos or JSON files that you choose to upload or share for menu creation.
• Support data such as the email address and context you choose to send when contacting QueueBill support.

How the data is used

• To run local billing, token printing, queue management, reports, backup/restore, and customer QR tracking.
• To sign vendors in with Google through QueueBill-owned Firebase Auth.
• To create and update one vendor-owned Google Sheet when the vendor chooses Customer Live Tracking.
• To process menu photos into draft menu items when you choose menu import.
• To provide setup, support, troubleshooting, abuse prevention, and service reliability.

Where data is stored and shared

QueueBill is local-first. Store data, menu data, orders, reports, and receipts are stored on the vendor phone unless the vendor exports a backup, contacts support, or turns on optional Customer Live Tracking.

Google sign-in is handled through QueueBill-owned Firebase Auth. Firebase and Google may process account identifiers, IP address, user agent strings, Firebase Android App ID, and request metadata for authentication, security, abuse prevention, and service reliability.

When Customer Live Tracking is enabled, QueueBill creates one vendor-owned Google Sheet. The public status tab contains only limited token-status fields needed by customer QR pages.

The public customer page is hosted as a static page and reads public Sheet rows. QueueBill does not sell user data and does not use third-party advertising SDKs in the Android app.

Google Play Data Safety summary

• Account information such as email, display name, and Firebase user ID is used for account management, app functionality, security, and support.
• Local POS data that stays only on the vendor phone is not collected by QueueBill unless the vendor exports it, sends it to support, or enables optional tracking.
• Customer Live Tracking is optional and writes only public-safe token status rows to a vendor-owned Google Sheet.
• QueueBill does not show ads, sell user data, use an advertising SDK, process in-app payments, or request broad Google Drive, broad Google Sheets, Gmail, SMS, call log, all-files, or background-location access.

Permissions

• Internet access is used for Google sign-in, optional Sheet setup/sync, QR tracking, support, and menu import.
• Bluetooth/Nearby devices access is used to find and connect paired thermal printers.
• Camera, photo picker, or file picker access is used only when you choose menu photo import, JSON import, or backup restore/export workflows.
• Google account authorization is used for sign-in and, only when enabled, file-level Sheet setup for Customer Live Tracking.
• QueueBill does not use location tracking for customer or vendor tracking. Legacy Bluetooth scanning may require location permission on older Android versions.

Public QR tracking data

The public customer tracking page is designed to show only limited token status: public token, token number, store name, status, message, position, updated time, expiry time, and schema version.

QueueBill is designed not to publish customer names, phone numbers, full order item lists, payment method, payment details, bill amount, device ID, private notes, or vendor email on the public tracking Sheet.

Retention and deletion

Local device data can be removed by clearing app data or uninstalling QueueBill. The app also provides Settings -> Privacy -> Request data deletion and Settings -> Data deletion links. Google Sheet data remains in the vendor's Google account unless the vendor deletes the Sheet, revokes access, clears public tracking rows, or asks QueueBill for support with deletion. QueueBill may retain limited support records when required for security, fraud prevention, accounting, dispute handling, or legal compliance.

Security

QueueBill uses HTTPS, Google OAuth, local app storage, and file-level access for the vendor-owned tracking Sheet. Do not send private credentials, payment secrets, private Google files, or sensitive customer data through normal support email unless QueueBill specifically gives you a secure setup process.

Changes

QueueBill may update this policy as the product changes. The latest version will be posted on this page.