Privacy Policy

Information we use

• Queue tickets: When you join a queue, we store the name you enter, the business, ticket number, status, and join/call/completion times. If a business has enabled SMS and you opt in, we also store your phone number, consent, and delivery status.
• Business accounts: We use your email address, verification status, and a Firebase account identifier to sign you in. Firebase handles your password, verification email, and reset email. We store your business names, categories, queue settings, and ticket history.
• Notifications: If you enable alerts, we store a browser push subscription or an app push token linked to your ticket or business account. A phone notification may include a ticket number or business name. You can decline notification permission and still use the queue.
• On your device: The apps store the current ticket key or business sign-in session in secure device storage. The website may remember a ticket link and your notification choice in your browser. Camera access is used only to scan a queue QR code when you choose to scan.
• Support and operation: If you email support, we receive the address and information you send. Our hosting and delivery providers may process technical data, such as network requests and IP addresses, to operate and secure the service.

How we use and share information

We use this information to create and manage queues, display live ticket status, send requested account emails and alerts, support users, and protect the service. The business running a queue can see the names and status of its customers' tickets. Do not put medical details or other sensitive information in a ticket name.

Cloudflare hosts the site and queue database; Google Firebase handles business email authentication; Expo and the phone platform deliver app notifications. If SMS is later enabled for a queue, the phone number and alert are sent through the configured SMS provider. These providers process information to supply their respective services. The current Turnly apps contain no advertising SDK.

Retention and deletion

Ticket records remain in the business's queue history after a visit ends or a customer leaves the line. Leaving removes that ticket's push subscriptions, but does not erase the ticket record. Archiving a business hides its queue and keeps its history so it can be restored.

Business owners can use Delete account and data in Turnly Business after finishing or removing active tickets. This removes the account, its queues, ticket history, and associated push subscriptions from Turnly's live database and requests deletion of the Firebase login. If that last step fails, contact support to complete the request. Copies in provider backups or operational records may remain under those providers' retention practices. We do not currently run an automatic scheduled purge of completed ticket history.

Customers can leave an active line in the app or on their ticket page, turn off notifications in device settings, and ask us to delete a ticket by contacting support with its ticket link. Business owners can contact support to request access, correction, or deletion help. We may need to verify a request before acting on it.

Contact

For privacy or data requests, email turnlyhelpdesk@outlook.com. You can also visit Turnly Support. We will update this page if Turnly's data practices change.