Privacy

QueueKat is operated by Ascent Software Design, LLC. We help event organizers manage queues and notify attendees. This notice explains what information we collect, how we use it, who can see it, and how long we keep it.

What we collect

• Account information: your email address, optional display name, account settings, and organization memberships. Your display name can be a nickname and can be changed or cleared.
• Authentication information: a protected password if you set one, sign-in and session records, and, if you enable them, passkey registration information, authenticator setup information, and recovery-code records.
• Notification information: optional phone numbers, Telegram chat IDs, and Discord user IDs; your channel preferences; verification and consent records; and message-delivery attempts, outcomes, and errors.
• Queue activity: the events and arrival windows you join, bookings, party names and membership, admission offers and responses, cancellations, and admission records. We record when these actions occur and, where relevant, which staff member performed them.
• Operational information: server logs, service-performance measurements, and diagnostic records used to operate and troubleshoot QueueKat.

We do not ask attendees for a legal name, postal address, date of birth, or payment method. You do not need a password to sign in using an emailed link.

How we use your information

We use your information to:

• Create and secure your account.
• Manage your place in a queue, party bookings, and admission.
• Send account and event messages through your selected channels.
• Help staff answer questions about queue activity and admission decisions.
• Provide organizers with event analytics and reports.
• Monitor service performance, diagnose failures, and maintain backups.

We do not sell your personal information or share it for marketing. We do not use advertising networks or advertising trackers.

Who sees what

• You can see your own queue places, arrival windows, and passes.
• Event staff can see attendees in their organization's queues, including email addresses and optional display names, queue activity, and admission history.
• Your party can see your display name if you set one. People opening a party join link can see the party name and its leader's display name, if set. These shared labels do not substitute your email address for a missing display name.
• QueueKat's operator processes account, queue, and operational information to provide and support the service.
• Service providers process information for hosting, backups, monitoring, and message delivery, as described below.

What the organizer sees

Joining an organizer's queue shares your email address with that organizer's event staff. They can also see your display name, queue position, arrival window, admission offers and responses, and whether and when you entered.

Organizers cannot see your password, sign-in links, session tokens, or optional phone number, Telegram chat ID, or Discord user ID. They can see notification delivery status, but not those destination addresses. Staff access is limited to their own organization's events, not other organizers' queues.

Organizers are responsible for how they use the attendee information available to them. Our terms of use set their obligations.

Event analytics and reports

QueueKat provides built-in analytics to organization owners and administrators. Event activity reports summarize bookings, waitlist entries, admission offers and responses, cancellations, admissions, scan refusals, and admission rates over time.

These reports use recorded queue activity, including visit transitions and scan records. Counts include repeat activity and individual party members; they are not a count of unique attendees or people currently inside.

Owners and administrators can download a full-history CSV of per-minute event activity counts. That CSV does not contain attendee names, email addresses, or individual attendee records. Event staff can still see individual records through their authorized queue-management views.

Service providers

We use service providers to operate QueueKat. These include:

Provider privacy notices: Vultr, Microsoft, Grafana, AWS, Twilio, Telegram, and Discord.

Email is required for an account. SMS, Telegram, and Discord are optional; disabling a channel stops QueueKat sending messages through it. Operational monitoring is separate from organizer-facing event analytics.

Text messages

SMS requires you to enter a phone number and agree to the consent wording in your settings. We record when you agreed and which wording you accepted.

• Verification: we send a six-digit code to confirm the number is yours. Other messages start only after you verify it.
• Messages: account and queue messages, including signup confirmation, admission offers, summons, and arrival reminders. We do not send marketing.
• Frequency: message frequency varies with the queues you join. Message and data rates may apply.
• Stopping: reply STOP to stop texts to that number, START to resume, or HELP for help. You can also disable SMS in your settings.
• Delivery: Twilio delivers messages and reports delivery status. Mobile numbers and text-messaging consent are not shared with third parties or affiliates for their marketing or promotional purposes.
• Records: we keep the number, consent and verification records, opt-out status, and message-delivery records.

The door scanner and your camera

The staff scanner uses the staff member's camera to read an attendee's pass. Camera frames are decoded in the browser. No camera images are uploaded to QueueKat or stored by QueueKat. The server receives the decoded pass text to process admission.

The camera runs after staff start it on the scanner page. Stopping the camera releases it.

Your pass

We generate the signed QR pass token when needed rather than storing the token itself. We keep the underlying pass and admission records. This is separate from the camera images, which we do not collect.

Queue history

Queue history includes visits, scans recording admission, and visit transitions recording changes to a queue place. Scan and transition records are append-only. They help explain admission decisions and support organizer reports.

Queue history remains after an event ends or you leave a queue. Leaving gives up your place; it does not erase the record of your participation.

How long we keep information

• Account information: until you delete your account or ask us to close it.
• Queue history and organizer reports: retained with the event for operational history and reporting.
• Authentication records: sign-in links and sessions have limited validity. Logging out ends the current session; account deletion removes the account's sign-in and authentication records.
• Notification records: retained to record consent, verification, and delivery activity. Account deletion removes the account's notification addresses and message-delivery records from the active database.
• Operational copies: logs, monitoring data, backups, and diagnostic copies are retained for no more than 30 days.

Deleting information from the active database does not immediately remove it from existing backups. Backup copies expire within the 30-day retention period. Copies already held by an organizer or message provider are outside your QueueKat account and are subject to that recipient's handling of them.

Getting your data out, and getting rid of it

You can delete your account in Delete this account. Sign in and confirm with your email address. Once any required handover is complete, deletion takes effect immediately and cannot be undone.

Deletion removes your email address, display name, password, passkeys, authenticator and recovery-code records, sign-in tokens, notification addresses, message-delivery records, and organization and party memberships from the active account. Any queue place you still hold is released first.

Queue history is anonymized rather than deleted: the account is replaced with a randomly labeled former-attendee record. Visit, transition, and admission history remains. Deletion does not erase organizers' existing copies or rewrite past backups.

You must hand over responsibilities before deleting an account if you are the last owner of an organization, lead a party with other members, or coordinate a group with other active attendees. A sole organization owner can instead delete the organization first.

There is no self-service button for getting a copy of your data. Email charlie@queue-kat.com to request a copy or help closing your account. We respond in writing.

Cookies

We use a session cookie and, if you choose it, a remember-me cookie to keep you signed in. We do not use advertising or third-party analytics cookies.

Security

We use HTTPS, protected password storage, expiring credentials, and organization-based access controls. Emailed sign-in links and organization invitation tokens are stored in protected form. Passkey private keys remain with your authenticator; QueueKat stores registration information used to verify sign-ins.

No security measure can guarantee complete protection.

Children

The minimum age is defined in the terms of use. If we learn that an account belongs to someone below that age, we close it using the deletion process described above, including anonymization of retained queue history.

Governing law

This notice is governed by the law of the Commonwealth of Virginia and applicable United States federal law.

Changes

This notice has a version and effective date. Material changes receive a new major version and a summary; wording changes and corrections receive a new minor version. We notify affected users of changes to how we handle information they have already provided. This notice describes our practices and does not require you to accept it again.

Contact

For privacy questions, data copies, or deletion requests, email charlie@queue-kat.com. We respond in writing.