© 2026 WaitQ® All rights reserved. WaitQ is a registered trademark of Azor Studio®.
WaitQ is operated by Azor Studio. This Privacy Policy explains how we collect, use, share, and protect personal data when you use the Service, and what choices and rights you have.
Scope and key concepts
This policy applies to:
- Visitors to our website
- Users who create and use WaitQ accounts (“Account Users”)
- Individuals who join a queue, make a booking or are added to a guest list operated by one of our business customers (“End Users”)
Because WaitQ is a B2B product that can also be used by individuals, our GDPR role depends on context:
- WaitQ as controller: We act as a controller when we process personal data for our own purposes, such as operating our website, administering accounts, providing support, securing the Service, and measuring product performance.
- WaitQ as processor (most waitlists): When a business uses WaitQ to run queues, bookings or guest lists for its own customers, that business typically determines why and how End User personal data is used. In that scenario, the business is the controller and WaitQ is the processor processing personal data on the business's behalf. Our Data Processing Agreement at waitq.app/dpa applies to every business customer and forms part of our Terms.
If you are an End User (you joined a waitlist), the business you interacted with is the primary controller for your waitlist data and will have its own privacy notice and policies.
If you purchase a paid plan, payment processing is handled by Polar (Polar Software Inc.) acting as Merchant of Record and/or through Polar’s payment partners. Polar may collect and process additional personal data for payments, tax/VAT, invoicing, fraud prevention, and regulatory compliance. This payment processing is not under our control and is governed by Polar’s own privacy policy and terms.
Personal data we collect
We collect personal data in the categories below. Some data is collected directly from you; other data is collected automatically when you use the Service; and some data is provided by our business customers when End Users join their waitlists.
Account and customer support data (Account Users):
- Name, email address, phone number (optional)
- Company/organization name
- Authentication data (e.g., password hash, login/session tokens)
- Support communications (emails, chat messages) and information you provide during troubleshooting
Queue, booking and guest list data (End Users; Customer Data)
Depending on what the business requests and what you submit:
- Name, phone number (optional), email address (optional)
- Queue and booking metadata (venue/list identifier, timestamps, position/status, group size, booking date and time, message delivery status)
- Any fields the business configures (e.g., seating preferences), if enabled by that business
- Device push token, if the End User allows push notifications
Usage, device, and log data:
- IP address and approximate location derived from IP
- Device/browser type and settings
- Pages viewed, features used, events/actions taken, timestamps
- Referrer URLs and basic diagnostics/performance data
- Security/audit logs (e.g., sign-in events, admin actions)
Analytics data:
We use product and website analytics tools to understand how the Service is used and to improve performance and user experience.
Our product analytics run in the European Union and measure how Account Users use the WaitQ dashboard. We design our analytics events to leave out End User names, contact details and message content. Website analytics measure use of our website and product, and load only after you accept analytics cookies.
Messaging and notification data:
When a business uses messaging features:
- SMS is delivered through specialist SMS providers in the European Union or the United States, depending on the destination country
- WhatsApp messages are delivered through the WhatsApp Business Platform
- Email is delivered through our email delivery provider
- Push notifications are delivered through the native push service of the End User’s device or browser
To deliver messages, these providers process End User contact details (e.g., phone number, email or push token) and message metadata (e.g., delivery status, timestamps). The business customer is responsible for ensuring they have the right to contact End Users and for complying with applicable marketing/telecom rules.
Billing and payment data (Polar as Merchant of Record):
If you purchase a paid plan:
- Polar may collect and process billing and payment-related data (e.g., name, billing address, tax/VAT details, payment method details, transaction identifiers, invoices/receipts, and fraud-prevention signals) as an independent controller.
- WaitQ typically receives limited data from Polar necessary to provision and manage access (e.g., subscription status, plan, purchase timestamps, and transaction/subscription identifiers).
How we use personal data
We use personal data for the purposes below:
Provide and operate the Service:
- Create and manage accounts
- Provide queue/waitlist functionality and status pages
- Enable integrations and basic platform operations
Send service communications and notifications:
- Operational emails (security alerts, account notices)
- Queue-related notifications (SMS/email), when enabled by a business customer
Support and customer service:
- Respond to requests
- Troubleshoot issues and resolve incidents
Security and abuse prevention:
- Protect accounts and prevent fraud, misuse, or unauthorized access
- Maintain audit logs and investigate security events
Analytics and improvement:
- Understand product usage, performance, and reliability
- Improve features, usability, and operational stability
Legal compliance and enforcement:
- Comply with legal obligations
- Enforce our Terms of Service and protect our rights
Legal bases (EEA/UK GDPR)
Where GDPR applies, our legal bases may include:
- Contract: to provide the Service to customers and Account Users;
- Legitimate interests: to secure, maintain, and improve the Service; prevent abuse; and perform basic analytics (balanced against user rights);
- Consent: where required (e.g., non-essential cookies/analytics in certain jurisdictions, certain marketing communications);
- Legal obligation: to meet accounting/tax record keeping and respond to lawful requests.
- End User messaging: In most cases, the business customer (controller) is responsible for determining the lawful basis and obtaining any necessary consent to contact End Users by SMS/email.
Cookies and similar technologies
We may use cookies and similar technologies for:
- Essential functions (authentication, security, session management)
- Analytics, where enabled
We present a cookie banner before any non-essential cookie or analytics tool loads. You can withdraw consent at any time through the same settings mechanism used to give it.
Data retention
We keep personal data only as long as necessary for the purposes described above, unless a longer retention period is required by law. Our standard retention periods are:
| Data category | Typical retention period |
| End User waitlist/queue data | For as long as the business customer’s subscription is active, unless the business customer deletes it earlier. Deleted after the export period described in our Terms, unless a longer period is required for legal, security, dispute, or enforcement reasons. |
| Account profile and organization data | While the account is active, then for a reasonable period after closure to support account recovery, dispute handling, security, tax, and compliance obligations. |
| Support communications | For as long as needed to respond to the request and maintain reasonable support, security, and business records. |
| Security, audit, and abuse-prevention logs | For a reasonable period needed to protect the Service, investigate misuse, and maintain platform integrity. |
| Analytics and usage data | For as long as needed to understand product usage and improve reliability, or until deleted/anonymized under our analytics tooling configuration. |
| Billing, subscription, invoice, and tax records | As required by applicable accounting, tax, anti-fraud, and legal obligations. Payment details are primarily handled by Polar as Merchant of Record. |
| Marketing and contact preferences | Until you unsubscribe, withdraw consent, or the data is no longer needed for the purpose collected, subject to suppression lists needed to honor opt-outs. |
Backups and logs may retain copies for a limited additional period before they are overwritten or deleted through normal backup rotation.
How we share personal data
We share personal data only as needed to operate the Service and for the purposes described.
With business customers (controllers): If you are an End User joining a waitlist, your data is shared with the business operating that waitlist. That business determines how your waitlist data is used.
With service providers (processors/sub-processors): We use trusted vendors to provide parts of the Service. Depending on your usage, this may include:
- Cloud hosting, database, authentication and file storage
- SMS, WhatsApp and email delivery
- Push notification delivery
- Product analytics, and website analytics after cookie consent
- Profile pictures shown in the dashboard
These providers process personal data under contractual protections appropriate to their role.
Our current subprocessors and their processing locations are listed at waitq.app/subprocessors.
With AI assistants a business connects: If a business connects WaitQ to an AI assistant such as Claude or ChatGPT, we send that assistant the data it needs to answer the business's requests. See "Connecting WaitQ to AI assistants" below.
Connecting WaitQ to AI assistants (Claude, ChatGPT)
A business admin can connect a WaitQ business to an AI assistant, such as Anthropic's Claude or OpenAI's ChatGPT, through the WaitQ connector. The assistant can then read that business's lists and bookings, and add or cancel guests, pick-up orders and bookings, when an authorized user asks it to in a chat.
Who decides. The business chooses to connect an assistant and decides what to ask it. For End User data, the business remains the controller and WaitQ acts as its processor. The assistant's provider receives the data because the business asked for it, and handles it under the business's own agreement and the provider's terms and privacy policy (for example, Anthropic's or OpenAI's). Anthropic and OpenAI are not WaitQ subprocessors.
What the assistant can receive. Only what is needed to answer a request, and only for the connected business:
- About End Users on a waitlist or pick-up order list: name, phone number, email address, party size, status (for example waiting or called), queue position, ticket or order number, chosen services, answers to the list's own questions, and the times they joined and were called.
- About End Users with a booking, including a day's bookings on a list: name, phone number, email address, party size, status, start and end time, notes, chosen services and answers to the list's own questions.
- About End Users on a guest list: name, phone number, email address, party size, date, status and check-in time, category, tags, notes and answers to the list's own questions.
- About the business's customers, when looked up by phone or email: name, phone number and email address.
- About the business: location names and time zones, list and guest list names, settings and event times, booking services with their durations and prices, and open booking times.
The connector does not share marketing consent records, internal customer IDs, payment details, visit history or data from other businesses.
What the assistant can send. When asked to add a guest, a pick-up order or a booking, the assistant sends the details the user gives it (name, phone number, email address, party size, booking time or guest list date, order number, chosen services, notes, category and tags, answers to the list's questions and, only if the guest agreed, marketing consent), and how the guest should be notified. WaitQ stores them like any other entry, order or booking, and sends the guest the list's usual message on the chosen channel, as it does for entries staff add. When asked to cancel an entry, order or booking or to remove a guest from a guest list, the assistant sends its ID, and WaitQ cancels or deletes it as staff would.
What WaitQ keeps about the connection. The WaitQ user who connected, the business, the assistant's name and sign-in address, when the connection was made and last used, and one-way hashes of its access tokens. We also record which connector tools are used, without guest details, to improve the Service.
Retention. Access tokens expire after one hour and refresh tokens after 30 days of no use. A disconnected or expired connection is deleted 30 days later. Unused sign-in registrations and authorization codes are deleted after one day. Data the assistant received is kept by its provider under the provider's terms; WaitQ cannot delete it.
How to disconnect. In WaitQ, go to Integrations, click Configure on the Claude or ChatGPT card and click Disconnect next to the app. The connection stops working immediately. You can also remove WaitQ from the assistant's settings. A connection also stops when the admin who made it loses admin access, or when the business moves to a plan without integrations.
Payments (Polar as independent controller)
For paid subscriptions, checkout and payment processing are handled by Polar. We may share minimal identifiers necessary to create/maintain your subscription, and Polar may share back subscription and purchase status so we can provision access. Polar’s collection and processing of payment-related personal data is governed by Polar’s own privacy policy and terms.
Legal and safety
We may disclose information if we believe it is reasonably necessary to:
- Comply with law, regulation, or legal process
- Protect the rights, safety, and security of WaitQ, our users, End Users, or the public
- Prevent fraud or abuse
Business transfers
If we are involved in a merger, acquisition, restructuring, or sale of assets, personal data may be transferred as part of that transaction, subject to appropriate safeguards.
International data transfers
Our application and database are hosted in the United States (US East). Some messaging providers also process data in the United States. Product analytics run in the European Union. Transfers of personal data from the European Economic Area to the United States are covered by the European Commission’s Standard Contractual Clauses. Each provider’s location is listed at waitq.app/subprocessors.
Because Polar operates its own payments platform and may use payment processors, payment-related personal data may be processed in multiple jurisdictions under Polar’s policies.
Security
We protect personal data in transit with TLS 1.2 or higher and at rest, including backups, with AES-256 encryption. Our hosting and database providers hold SOC 2 Type 2 attestations. The measures are described at waitq.app/security. No method of transmission or storage is completely secure, and you are responsible for keeping your credentials secure.
Your rights and choices
Depending on your location, you may have rights to:
- Access your personal data
- Correct inaccurate or incomplete data
- Request deletion (in certain cases)
- Restrict or object to processing (in certain cases)
- Data portability (where applicable)
- Withdraw consent (where processing is based on consent)
How to exercise rights: please send an email to support@waitq.app with your request. We will respond within one month of receiving your request. Where a request is complex, we may extend this by up to two additional months, and we will tell you if we do.
End Users (waitlists run by businesses)
If you joined a queue, made a booking or were added to a guest list run by a business, that business is typically the controller. We may refer your request to that business, or support them in fulfilling it, depending on the request and applicable law.
Complaints
If you are in the EEA/UK, you have the right to lodge a complaint with the supervisory authority in your country of residence, workplace, or where the alleged infringement occurred. In Portugal, that authority is the CNPD (Comissão Nacional de Proteção de Dados), at cnpd.pt.
Children
The Service is not directed to anyone under 16, and we do not knowingly collect personal data from children. If you believe a child has provided personal data, contact us so we can take appropriate action.
Privacy contact
For any privacy question or request about your personal data, email support@waitq.app.
Business access, exports, and marketing consent records
Depending on the Customer’s plan, authorized business users can view and export End User customer activity associated with queues and reservations for a history window of up to 90 days after the relevant queue join or reservation. This product-access window does not by itself determine when data is deleted. Actual retention may be shorter if the Customer deletes data earlier, or longer where reasonably necessary for legal, security, dispute, enforcement, or opt-out compliance purposes, as described above.
When an End User affirmatively opts in to marketing through a WaitQ-powered form, WaitQ stores the current marketing-consent status and the timestamp when that status was last updated on behalf of the business Customer. This helps the Customer administer consent, honor withdrawals, and maintain a compliance and audit record. WaitQ does not maintain a complete history of every consent event. The business Customer remains responsible for its marketing communications, lawful basis, notices, and honoring withdrawal requests.
Changes to this policy
We will update the “Last updated” date when this policy changes. If a change affects how we use personal data you have already given us, we will tell account owners by email before it takes effect.