qrwaitStart free

Privacy Policy

Last updated: 1 November 2026

1. Scope

This notice explains how personal data is processed in the QR Wait service (qrwait.app) under Turkish Law No. 6698 on the Protection of Personal Data ("KVKK") and the EU General Data Protection Regulation ("GDPR").

2. Data controller

QR Wait is the controller of account holders' data. Contact: hello@qrwait.app

Businesses that set up queues with QR Wait (account holders) are the controllers of the data of visitors joining their queues; QR Wait acts as a processor, handling that data on the business's behalf solely to run the service.

3. Data of visitors joining a queue

  • Queue entry: group size, accepted numbers of places, queue number, time of joining and being called, interface language, the last time your queue page was open (shown to the attendant together with whether notifications are on, so they can tell whether you'll hear about the call).
  • Device ID: a random identifier that prevents a second number from the same phone and pairs QR Wait on your home screen with your browser. It is not linked to your name or phone number.
  • Location: if the queue uses a location check, used only at the moment you join, to check that you are at the queue's location or near the attendant. While you're in the queue with your queue page open on screen, your location is sent as you move and at least once a minute to show your distance to the queue (or the attendant); the attendant sees this distance. Your location is not stored; only the distance and when it was measured are kept with your queue entry.
  • Notification subscription: your browser's push address, if you allow "it's your turn" notifications. It is also used to deliver the messages the attendant sends to everyone in the queue. If you added QR Wait to your home screen, this address is also stored with your device ID so you get notified in later queues too; which queues you have a number in is kept only so the app can show your number when opened.
  • Attendant note: a short note if the attendant adds you manually.
  • Name: if the business turned it on for the queue, the name you enter when joining (optional or required, up to 30 characters). It shows next to your number on the attendant panel and is deleted with your queue entry. It is also kept in your browser only, to be suggested next time. Visitors are never asked for a phone number or email address.
  • Join form answers and requests: if the business added questions to the queue's join form (such as the reason for your visit), your answers (up to 60 characters each); and, if you use them, when you said "I'm on my way" and how many times you asked for more time. They show on the attendant panel and are deleted with your queue entry. Whether you accepted the queue's rules is checked when you join and not stored.
  • Feedback: if the business asks for it, after you are served you may rate the visit from 1 to 5 and add a note of up to 200 characters. The rating is only counted (per day and per attendant who served you); the note is shown to the business without your name or number and is deleted with your queue entry's retention, at the latest 24 hours after you joined. A low rating may be emailed to the business with the note.
  • Messages: if the business turned on messages for the queue, the short messages you and the attendant exchange on your queue page (up to 300 characters each, at most 50). They show on your queue page and on the attendant panel, and a notification may carry the attendant's message to your phone. They are kept with your queue entry only: not in backups, the daily statistics only count them, and the attendant action log only notes that a message was sent, without its text.
  • Appointments: if the business takes appointments and you book a time, the time, group size, service, a booking code, your interface language and whatever the join form asks (name, answers), plus the reminder's push address if you turn it on. The booking is kept in your browser too, so you can open it again. When you check in, it becomes your queue entry; if the attendant books for you by phone, only what you tell them is stored. Visitors are never asked for a phone number or email address to book.
  • QR Wait app (iPhone): if you use the app, its notification address is a device token from Apple instead of a browser's push address; notifications go through Apple's push service and the token is kept like the push address above. The Live Activity (your number on the lock screen) gets its own token from Apple, kept until your queue entry ends. If you let the app share your distance while it is closed (location access "Always"), your location keeps being sent while you hold a number, as with the queue page open: still only the distance is kept, and it stops when your entry ends. The app has no tracking or advertising and collects nothing else.
  • QR Wait app (Android): if you use the app, its notification address is a token from Google's Firebase Cloud Messaging instead of a browser's push address, kept like the push address above. If you let the app share your distance while it is closed, a notification shows while it does, and it stops when your entry ends; still only the distance is kept. The app has no tracking or advertising and collects nothing else.

4. Data of account holders

  • Account: username, email address, language, the version and time you accepted the terms of use, and how you first reached the site (campaign tag or referring site) and the page you landed on.
  • Usage and our emails: when your email address was verified, when you first opened a queue, ran a test and took a first ticket, how many tickets came from visitors and how many you added yourself, a usage stage worked out from these (for example set up, active, dormant), which of our emails were sent to you and when, the email groups you turned off, and the country and time zone read from your connection at sign-up (the time zone then follows your queues).
  • Password: only an irreversible hash (PBKDF2) is stored. Whether a password appears in known data breaches is checked by sending only the first 5 characters of its hash (k-anonymity); the password or full hash is never sent anywhere.
  • Team members: if an account holder invites people to their account, the invitee's email address (to send the invitation link) and the role offered; once they join, their own username, password hash, role and the queues they may open. What a member does in an attendant panel is logged under their username.
  • Two-step sign-in: if you turn it on, the secret key shared with your authenticator app and one-way hashes of your unused recovery codes.
  • Sign-in browsers: a random ID in an "ad" cookie; a one-way hash of it is stored for the last 10 browsers you signed in from, so we can email you when your account is signed in from a new one. That email names the browser and system read from your browser's user agent; they aren't stored.
  • Queues: queue name, address, location and settings. For queues that check location against the attendant, the last location sent by the attendant panel (only the latest one, for the check). Daily statistics are counts only (how many groups joined, were called, average wait) and contain no visitor information.
  • Usage and payment records: tickets used and remaining, order number, pack and amount. Your card details never reach us; payment is taken by Lemon Squeezy.

5. All visitors

  • Technical data: IP address, browser information and request logs, for security, rate limiting and abuse prevention.
  • Error reports: if a page fails in your browser, the error message, the page address and your browser version are sent to us so we can fix the fault; they are kept like the technical logs.
  • Bot check: Cloudflare Turnstile on the sign-up and password reset forms.
  • Visit source: on your first visit, the campaign tag or the referring site and the page you landed on are kept in your browser's local storage. They leave your browser only if you create an account, and are then stored with it.

6. Purposes and legal bases

  • Providing the queue service, managing accounts, tracking tickets, crediting payments and sending the account emails about them (e.g. tickets running low or used up, tickets added): performance of a contract (KVKK Art. 5/2-c; GDPR Art. 6/1-b).
  • Security, preventing fake sign-ups and abuse, account verification, measuring which marketing channels work: legitimate interests (KVKK Art. 5/2-f; GDPR Art. 6/1-f).
  • Emails about your account and reminders (welcome, verification reminder, help setting up, a note when an active account goes quiet), and working out the account's usage stage for these and for our team's follow-up: legitimate interests (KVKK Art. 5/2-f; GDPR Art. 6/1-f). Every reminder email has a link to turn reminders off.
  • Legal obligations and requests from authorities: legal obligation (KVKK Art. 5/2-ç; GDPR Art. 6/1-c).

7. Recipients and international transfers

  • Cloudflare, Inc. (USA): hosting, storage, email delivery, bot checks, security, cookieless visit statistics (Web Analytics).
  • Lemon Squeezy, LLC (USA): payments and invoicing. Lemon Squeezy is the merchant of record; payment data is subject to its privacy policy.
  • Apple Inc. (USA): delivering notifications and Live Activity updates to the QR Wait iPhone apps (Apple Push Notification service). It receives the app's token and the notification: its title, text and the page it opens, or for a Live Activity your number and its status.
  • Google LLC (USA): delivering notifications to the QR Wait Android apps (Firebase Cloud Messaging). It receives the app's token and the notification: its title, text and the page it opens.
  • Telegram (Telegram FZ-LLC, UAE): our team's internal notices about accounts (sign-ups, usage milestones, a daily summary). They contain the username (the account's public page name), category, sign-up source, language, country, usage stage and counts; never an email address, a phone number or any visitor data.
  • Your browser's push service: if you allow notifications in your browser, they are delivered by the push service your browser uses (for example Google for Chrome, Apple for Safari, Mozilla for Firefox, Microsoft for Edge). It receives only your push address and the notification encrypted end to end, which it can't read.
  • OpenStreetMap Foundation (UK): map tiles and address search in the admin panel.
  • The business running the queue: your entry is shown on its attendant screen.
  • Systems the business connects: if the business sets up webhooks, events about queue entries (number, group size, service, times) are sent to the addresses it chose; your name, join form answers and booking code only if it turned that on for an address. Its API keys let its own systems read the queue and add, call or serve numbers.
  • International transfers: our main sub-processor is Cloudflare, Inc. (USA), which hosts the service. Under the GDPR, transfers to Cloudflare rely on the EU Standard Contractual Clauses in Cloudflare's Data Processing Addendum (GDPR Chapter V). Under KVKK Art. 9, the standard contract will be signed and notified to the Turkish Personal Data Protection Authority together with our first contract with an institutional customer. Your data is never sold or shared for advertising.

8. Retention

  • Queue entry: until the attendant marks you as arrived or removes you, you leave the queue, or the business resets the queue (unless the business turned it off, the queue resets itself at the end of the day); the push subscription is deleted with it. When the attendant removes you, the entry is kept for 1 more minute so a mistake can be undone. The push address and ticket list linked to your device are deleted after 30 days without use. Whatever the queue's settings, an entry, including the name and join form answers, is deleted at the latest 24 hours after joining. A feedback note is deleted on the same schedule; the rating stays only as a count.
  • Appointment: until it is checked in (from then on like a queue entry) or cancelled; a cancellation deletes your name, answers and push address at once. The name and answers of a booking that isn't checked in are deleted 2 hours after its time, and the booking itself at the latest 24 hours after its time.
  • Messages: with the queue entry, so at the latest 24 hours after joining; the action log keeps only that a message was sent.
  • Account: until the account is deleted. Accounts whose email isn't verified within 7 days are deleted automatically. After an account is deleted, its username is reserved for 1 year so printed QR codes don't lead to someone else, and a one-way hash (SHA-256) of its email address is kept for 1 year so free tickets aren't granted again to a re-created account.
  • Verification and password reset links: 3 days and 1 hour; deleted once used.
  • Invitations and team members: an invitation link for 7 days, until it is used or withdrawn; a member's sign-in until an owner removes it, the member leaves, or the account is deleted.
  • Webhooks and API keys: a business's webhook addresses, signing secrets and API keys (only a one-way hash of each key) until it deletes them; deliveries waiting to be retried for at most about 9 hours; the delivery log (time, event, address and the answer's status, no contents) for the last 50 deliveries.
  • Attendant action log: what was done in the attendant panels (ticket numbers, the name of the attendant link or team member, the time), for 30 days and at most 5,000 actions per queue. Per-attendant statistics are counted from it.
  • Failed login counters: at most 1 day. Technical logs: for the provider's log period, usually a few days.

9. Cookies and browser storage

  • Essential: your session key, device ID and queue number are kept in your browser's local storage; the service can't work without them. The device ID is also kept in a "d" cookie (readable only by the server, valid on all QR Wait addresses). If you choose a language, it's kept in a "lang" cookie so businesses' addresses open in the same language. Signing in to the admin panel sets an "ad" cookie (readable only by the server) that recognises the browser for the new sign-in email.

10. Your rights

Under KVKK Art. 11 and the GDPR you have the right to access, rectify and erase your data, restrict or object to processing, receive your data in a portable format, and seek compensation for damages.

Send requests to hello@qrwait.app; we reply within 30 days. Account holders can delete their account themselves in the admin panel. Visitor requests about a queue are forwarded to the business that controls it. You may also complain to the Turkish Personal Data Protection Authority or the data protection authority of the country where you are.

11. Security

All connections are encrypted (HTTPS). Passwords are stored irreversibly, login attempts are limited, and email links are single-use with only their hashes stored.

12. Changes

We may update this notice; account holders are informed of significant changes by email. See the Terms of Use for the rules of the service.