This Data Processing Agreement (“DPA”) forms part of the Terms and Conditions between WaitQ and the customer (“Customer”). It applies automatically whenever WaitQ processes personal data on Customer’s behalf. No separate signature is needed. If Customer needs a signed copy, email support@waitq.app.
1. Definitions
Terms not defined here have the meaning given in the Terms or in Data Protection Law.
- Data Protection Law means the EU General Data Protection Regulation 2016/679 (“GDPR”), the UK GDPR and the UK Data Protection Act 2018, and any other data protection law that applies to the Processing.
- Personal Data, Processing, Controller, Processor, Data Subject and Supervisory Authority have the meanings given in the GDPR.
- Customer Personal Data means Personal Data that WaitQ processes on Customer’s behalf through the Service.
- Subprocessor means a third party WaitQ engages to process Customer Personal Data.
- Security Incident means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
- Standard Contractual Clauses means the clauses approved by the European Commission in Implementing Decision (EU) 2021/914, and the UK International Data Transfer Addendum where UK law applies.
2. Roles
Customer is the Controller of Customer Personal Data, and WaitQ is its Processor. WaitQ acts as an independent Controller for the account, billing, support, security and website data described in its Privacy Policy. This DPA does not cover that data.
3. Customer’s obligations
Customer is responsible for:
- having a lawful basis to collect Customer Personal Data and to have WaitQ process it;
- giving Data Subjects the notices that Data Protection Law requires;
- obtaining any consent needed to contact End Users by SMS, WhatsApp, email or push notification, and honouring opt-outs;
- configuring check-in forms so they collect only the data Customer needs. Customer must not use the Service to collect special categories of Personal Data under Article 9 GDPR.
4. WaitQ’s obligations
WaitQ will:
- process Customer Personal Data only on Customer’s documented instructions, including for international transfers, unless the law requires otherwise. The Terms, this DPA and Customer’s configuration of the Service are Customer’s complete instructions. WaitQ will tell Customer if it believes an instruction breaches Data Protection Law;
- ensure that everyone authorised to process Customer Personal Data is bound by confidentiality;
- maintain the technical and organisational measures in Annex II;
- assist Customer, taking into account the nature of the Processing, in responding to Data Subject requests and in meeting its obligations under Articles 32 to 36 GDPR;
- pass to Customer any Data Subject request it receives about Customer Personal Data, without responding to it except on Customer’s instructions;
- make available the information reasonably necessary to demonstrate compliance with this DPA.
5. Subprocessors
- Customer gives WaitQ general authorisation to engage Subprocessors. The current list is published at waitq.app/subprocessors.
- WaitQ will notify Customer at least 30 days before adding or replacing a Subprocessor, by email to the account owner and by updating that page.
- Customer may object on reasonable data protection grounds within those 30 days. The parties will discuss the objection in good faith. If they cannot resolve it, Customer may terminate the affected part of the Service.
- WaitQ will impose data protection obligations on each Subprocessor that protect Customer Personal Data to the standard of this DPA. WaitQ remains responsible to Customer for its Subprocessors’ performance of those obligations.
6. International transfers
WaitQ’s database and application are hosted in the United States, and some Subprocessors process data there. Where Processing involves a transfer of Customer Personal Data outside the European Economic Area or the United Kingdom to a country without an adequacy decision, WaitQ ensures the transfer is covered by the Standard Contractual Clauses with the relevant Subprocessor.
7. Security Incidents
WaitQ will notify Customer without undue delay after becoming aware of a Security Incident. The notice will describe, as far as WaitQ then knows:
- the nature of the incident, and the categories and approximate number of Data Subjects and records concerned;
- its likely consequences;
- the measures taken or proposed to address it and limit its effects;
- a contact for further information.
WaitQ will update Customer as more information becomes available. Notice of a Security Incident is not an admission of fault or liability.
8. Audits
WaitQ will answer Customer’s reasonable written questions about its compliance with this DPA, including security questionnaires. Customer agrees that the SOC 2 Type 2 attestations of WaitQ’s infrastructure providers may be used to help demonstrate compliance.
If that information is not enough to show compliance, or a Supervisory Authority requires it, Customer may carry out an audit, or have an independent auditor bound by confidentiality do so. Customer must give at least 30 days’ written notice. Audits are limited to once a year, take place during business hours, are at Customer’s cost, and must not disrupt the Service or expose other customers’ data.
9. Deletion and return
Customer can delete Customer Personal Data in the Service at any time. During the subscription, WaitQ keeps Customer Personal Data until Customer deletes it. Depending on Customer’s plan, the Service shows queue, booking and guest list history for up to 90 days after the relevant visit or booking. That window limits what Customer can view and export. It does not delete data.
When the subscription ends, Customer has 30 days to export Customer Personal Data. WaitQ will then delete it, unless EU or Member State law requires continued storage. Deleted data is removed from backups as they rotate.
10. Liability
Each party’s liability under this DPA is subject to the limitations of liability in the Terms. Nothing in this DPA limits either party’s liability to Data Subjects, or any liability that cannot be limited under Data Protection Law.
11. Duration and order of precedence
This DPA lasts as long as WaitQ processes Customer Personal Data. If documents conflict, the following order applies: the Standard Contractual Clauses, then this DPA, then the Terms.
Annex I: Details of processing
| Item | Details |
| Data Subjects | Customer’s own customers who join a queue, make a booking or appear on a guest list (“End Users”), and Customer’s staff who use the Service (“Authorised Users”) |
| Categories of data | Name; phone number and email address where provided; responses to check-in form fields Customer configures (for example party size or seating preference); queue and booking details (location, list, timestamps, position, status, booking date and time); device push token where push notifications are allowed; message delivery status; marketing consent status and when it last changed |
| Special categories | None. Customer must not configure the Service to collect them |
| Nature of processing | Collection, storage, organisation, display, transmission of notifications, analytics, export and deletion |
| Purpose | Running Customer’s queues, bookings and guest lists; notifying End Users; giving Customer wait and visit analytics |
| Frequency | Continuous, for the length of the subscription |
| Retention | For the length of the subscription, unless Customer deletes data sooner. Deleted after termination as set out in section 9 |
Annex II: Technical and organisational measures
| Area | Measure |
| Encryption in transit | waitq.app, the database, and the email and analytics providers accept only TLS 1.2 or 1.3. HTTP redirects to HTTPS, and HSTS is set for two years, including subdomains. The application reaches the database over HTTPS through Supabase’s client library |
| Encryption at rest | Database data and backups are encrypted with AES-256, with a key unique to the WaitQ project |
| Hosting | Application on Vercel and database on Supabase, both with SOC 2 Type 2 attestations |
| Backups | The database is backed up by Supabase. Backups are encrypted with AES-256 |
| Access | Each Authorised User signs in with an individual account. Passwords are stored only as hashes |
| Data minimisation | Check-in forms collect only the fields Customer configures. End Users need no app or account. Names can be hidden on the public check-in page and the TV display |
| Retention | Customer can delete records at any time. Customer Personal Data is deleted after the 30-day export period that follows termination |
| Analytics | Product analytics run on PostHog’s EU cloud |
| Messaging consent | SMS sent through Twilio honours STOP and HELP replies. A number that has opted out receives no further SMS from the Service. Marketing consent status is recorded with the time it last changed |
| Payments | Card data is handled by Polar as Merchant of Record and never reaches WaitQ |
Annex III: Subprocessors
The current list of Subprocessors, with their purpose and location, is published at waitq.app/subprocessors.