Privacy Policy

WaitQ ("WaitQ", "we", "us", or "our") provides a comprehensive restaurant technology platform comprising cloud POS software, customer waitlist and queue management, table management, Kitchen Order Tickets (KOT), billing and payments processing, captain mobile applications, and desktop print bridge integrations.

This Privacy Policy applies to all users of our services, including restaurant business owners, staff, captains, administrators, and customers interacting with WaitQ queue systems or online dining tools.

We collect only data necessary to operate our restaurant SaaS platform and deliver reliable ordering, queue management, billing, and communication services:

A. Restaurant Account & Staff Information

When a restaurant registers for WaitQ, we collect restaurant owner and staff details including account name, staff phone numbers, email addresses, login credentials, assigned role permissions (e.g., Cashier, Captain, Admin), and outlet identifiers.

B. Customer Queue & Dining Information

When restaurant guests join a waitlist or queue, we collect customer queue details including customer name, party size, seating preferences, and customer phone number collected with explicit consent for sending SMS or WhatsApp queue status updates.

C. Restaurant Operational & POS Data

To manage floor operations, we process operational records created by the restaurant, including table states, active and completed orders, Kitchen Order Tickets (KOT), item modifications, discounts, due payment logs, billing history, thermal print job queues, and staff transaction logs.

D. Payment Information

SaaS subscription payments and customer digital bill payments are processed through secure third-party payment gateways (such as Razorpay). WaitQ does not collect or store full credit/debit card numbers, CVVs, PINs, bank account passwords, or sensitive UPI credentials. Payment gateway transactions are handled according to payment industry security standards.

E. Application & Integration Data

When using the desktop print bridge or mobile captain application, system event logs (such as local printer connection status, offline sync timestamps, app version, device OS version, and network state) are processed to maintain system reliability.

We process collected data for the following legitimate business and operational purposes:

• Providing, operating, and maintaining the WaitQ restaurant management platform.
• Managing customer waitlists, table assignments, and floor availability.
• Processing orders, generating KOTs, issuing bills, and handling receipt printing.
• Sending automated customer notifications via SMS or WhatsApp regarding queue status, table readiness, or receipt links.
• Processing SaaS subscription mandates and verifying subscription status via Razorpay.
• Facilitating offline data synchronization between mobile captain apps, desktop print bridge, and cloud servers.
• Delivering customer support, diagnosing technical failures, and investigating system bugs.
• Enforcing multi-tenant security, preventing unauthorized access, and guarding against fraudulent activity.
• Complying with applicable accounting, legal, tax, and regulatory obligations.

Restaurant operators are responsible for providing appropriate privacy notices and obtaining necessary customer consent before adding guest details into the WaitQ waitlist system or initiating automated SMS/WhatsApp notifications.

Our documented data retention policies balance operational necessity with customer privacy:

• Customer Queue Phone Numbers: Phone numbers collected solely for queue management and waitlist updates are automatically purged 30 days post-visit, unless explicitly added or retained by the restaurant operator within their customer relationship records.
• Restaurant Operational Records: Restaurant order history, bill records, transaction logs, and tax invoices are retained for the duration of the restaurant's active subscription and for a statutory period thereafter to fulfill accounting, tax, and dispute resolution requirements.
• Account Deletion: Upon restaurant tenant account deletion, operational data is purged within 14 calendar days as outlined in our Data Deletion policy.

We do not sell, rent, or trade personal data to third parties. We share information only with trusted infrastructure and service providers necessary to deliver the WaitQ platform:

WaitQ implements technical, physical, and organizational security measures designed to safeguard your information, including:

• Supabase authentication with encrypted password hashing and secure token handling.
• Multi-tenant Row-Level Security (RLS) ensuring strict isolation of database records between distinct restaurant accounts.
• Role-based access controls restricting captain, cashier, and manager permissions.
• HTTPS encryption in transit across all web, desktop, mobile API, and payment endpoints.
• Subscription-gated admin access verifying valid payment mandates before dashboard entry.

While we maintain robust administrative and technical protections, no electronic transmission over the internet or storage architecture can be guaranteed 100% immune from security compromise.

Depending on your jurisdiction, you or your restaurant customers may have rights regarding personal information, including:

• The right to request access to the personal data we hold about you.
• The right to request correction of inaccurate or incomplete information.
• The right to request deletion of personal information (subject to legal retention duties).
• The right to object to or opt out of non-essential communications.

To exercise these rights, restaurant administrators or end-users can contact us at waitlist14@gmail.com.

WaitQ uses strictly necessary cookies and browser local storage mechanisms essential for core platform operation:

• Authentication Cookies: Storing secure auth sessions and access tokens.
• Local Storage: Preserving active UI theme preferences, desktop print bridge connection credentials, and offline queue state for mobile captains.

We do not track users across third-party websites for advertising purposes.

WaitQ cloud services and database infrastructure (e.g. Supabase, Upstash) are hosted in secure data centers. If you access WaitQ from outside the hosting region, your data may be transferred, stored, and processed internationally in accordance with this Privacy Policy and applicable data protection standard contractual clauses.

WaitQ is a business-to-business restaurant management tool intended for use by commercial restaurant operators and adult personnel. We do not knowingly collect personal information from individuals under 18 years of age.

We may update this Privacy Policy from time to time to reflect product enhancements, legal requirements, or operational changes. The updated version will be indicated by a revised "Effective Date" at the top of this page.

For questions or concerns regarding this Privacy Policy or our privacy practices, please contact us: