Who this policy covers
This policy applies to QwikPass websites, restaurant workspaces, guest queue passes, invoices, online-order pages and related support. A restaurant using QwikPass controls the business and customer information it enters. YK Builds operates the QwikPass platform and processes that information to provide the service.
Information we process
- Organization and restaurant information: business names, outlet locations, menus, prices, taxes, invoice settings, operating hours and plan details.
- Owner and staff information: name where provided, email address, authentication identifiers, role, Outlet assignments, security events and access changes.
- Guest and transaction information: private queue identifiers, optional name and phone number, order items, payment method confirmation, invoice details and preparation status.
- Device and service information: limited browser, network, diagnostic and security data needed to operate, protect and troubleshoot QwikPass.
- Messages: delivery identifiers and status events for transactional email, WhatsApp or SMS. QwikPass does not use an invoice or queue phone number for marketing without separate consent.
Why we use information
We use information to authenticate authorized users, isolate Organization and Outlet access, operate queues and orders, generate private invoices, deliver requested transactional notifications, calculate usage, prevent abuse, provide support and improve reliability. We do not sell personal information.
Service providers and payment boundaries
QwikPass uses service providers to run the product, including Google Cloud and Firebase for backend, authentication and data services; Netlify for the public web application; Zoho for transactional email; Meta WhatsApp Cloud API for opted-in WhatsApp messages; and Razorpay for QwikPass subscriptions and restaurant-connected online payments. These providers process information under their own terms and privacy practices.
Restaurant customer payments settle to the restaurant’s connected payment account where that feature is enabled. QwikPass stores provider references and transaction status, not card numbers, CVV or banking credentials.
Retention and deletion
We keep information only while needed to provide and secure the service, meet legitimate business obligations, resolve disputes and comply with applicable accounting, tax or legal retention requirements. Security and audit records may be retained separately from active workspace data. A restaurant may request closure of its QwikPass Organization; some invoices and transaction records may need to remain immutable for a legally required period.
Security and choices
QwikPass uses authenticated, role-scoped access for protected workspaces, private capability links for guest records, encryption in transit, provider-managed encryption at rest, audit trails and optional authenticator MFA. No internet service can guarantee absolute security.
Guests can join a digital queue without providing a name, phone number or account. Phone numbers are optional at the counter unless a guest requests digital delivery or a restaurant explains a separate loyalty purpose. Browser notifications and WhatsApp updates require the user’s choice or consent.
Access, correction and questions
Restaurant owners can correct operational information in their workspace. Staff should contact their Organization owner about role or account data. For privacy questions, access or deletion requests, email security@qwikpass.in. We may verify identity and authority before acting on a request.
Updates
We may update this policy as QwikPass changes. Material updates will be identified by a revised effective date and, where appropriate, communicated to Organization owners.