1. Information We Collect
The information QueueBuzz collects depends directly on how you use our services:
- From Hosts (Businesses): We collect account information such as your email address, business name, address, phone number, and a custom URL slug for your queue page. If you upload a profile photo or cover banner, those images are stored on our servers. Payment data (such as subscription status and billing cycle) is handled through our payment partner, Dodo Payments; we do not store your full card or banking details. We also collect notification preferences you configure in your account settings.
- From Customers (Guests): We collect only the information necessary to place you in a queue: your name or initials, and — if the Host has enabled it or you choose to opt in — a phone number or email address for queue status notifications. If the Host has enabled geo-fencing, we request your device's location coordinates at the moment of joining solely to verify proximity to the venue; this data is not stored beyond the join attempt. If you grant permission for push notifications, we collect a Firebase Cloud Messaging (FCM) device token to deliver alerts about your queue status. No account creation or app download is required.
2. How We Use Your Information
We use the collected information strictly for the functional operation of the QueueBuzz platform:
- To create, manage, and display digital waitlists in real time.
- To send queue status notifications via web push (FCM), browser audio/haptic alerts, and — if provided — SMS or email.
- To verify a Customer's physical location when a Host has enabled geo-fencing for their queue.
- To provide Hosts with queue analytics such as average wait times, guest load, and historical queue data (subject to the Host's subscription plan).
- To display custom branding (profile photo and cover banner) on the Host's queue join page.
- To process and manage Premium subscription payments through Dodo Payments.
- To provide customer support and troubleshoot technical issues.
3. Firebase and Push Notifications
QueueBuzz uses Firebase (Google LLC) for authentication and push notifications. When a Host signs in via Magic Link or Google Sign-In, Firebase processes authentication on our behalf. When a Customer or Host opts into push notifications, a Firebase Cloud Messaging (FCM) token is generated and stored against their queue session or account to deliver relevant alerts. FCM tokens are subject to Google's Privacy Policy. You can revoke push notification permissions at any time via your browser settings.
4. Cookies and Local Storage
We use standard web technologies such as cookies and browser local storage strictly to maintain your session. For Hosts, this keeps you logged into your dashboard across page visits. For Customers, it remembers your active queue session so you do not lose your position if you close and reopen the page. We do not use third-party tracking cookies or cross-site profiling tools.
5. Data Sharing and Disclosure
QueueBuzz does not sell your personal data. We share information only with the following trusted third-party service providers, solely to keep our platform operational:
- Firebase (Google LLC) — authentication and push notification delivery.
- Dodo Payments — secure processing of subscription payments for Host accounts.
- Brevo (formerly Sendinblue) — transactional email delivery for notifications and system messages.
- Cloud infrastructure provider — secure hosting of application data and uploaded images.
In the event of a legal request, we may disclose your information if required by applicable law or a valid court order.
6. Data Retention
Customer data (names, optional contact details, and FCM tokens) is associated with a specific queue session. Queue history retention is governed by the Host's subscription plan — on lower tiers, records are automatically anonymized or deleted after a set number of days; on higher tiers, data may be retained longer and is exportable. Geo-location data is used only at join time and is not persisted. Host data (account details, uploaded images, and settings) is retained as long as the account remains active. Upon a confirmed account deletion request, all Host data is permanently deleted from our systems.
7. Security Measures
We store data on secure, industry-standard encrypted servers. Host authentication is handled entirely via Firebase, which means QueueBuzz never stores passwords. Uploaded images pass through a server-side validation and resizing pipeline before storage. Access to production data is tightly restricted and monitored. However, no method of electronic data transmission or storage is 100% secure, and we cannot guarantee absolute security.
8. Your Individual Rights
You have the right to access, correct, or request deletion of your personal data held by us. Hosts can update or delete account details directly from the Settings page in their dashboard; account deletion can be initiated via the Danger Zone section in Settings. Customers who have participated in a queue may contact us to request access to or erasure of their past queue entry data — we may coordinate such requests with the relevant Host where appropriate.
9. Contact Us
If you have questions, feedback, or concerns about this policy and how your personal information is handled at QueueBuzz, please contact our privacy compliance team at privacy@queuebuzz.com.