Privacy
Updated 15 November 2026. This page explains how this Cumtroller installation handles information when you visit, join a queue, or manage a machine.
Your cookie choice
Before acceptance, and if you decline, Cumtroller does not send cookies to your browser. Acceptance is stored in a general site cookie for one year. Declining is remembered in this tab's session storage, not a cookie; a new tab or browser session may ask again.
What cookies contain
- cumtroller_consent: the acceptance version, for one year, across this site.
- queue_identity_{queue ID}: an encrypted random identifier, for 30 days, scoped to that queue's URL. It identifies your server-side queue entry; it does not contain your name, IP address, queue position, API token or machine settings.
- Session and XSRF cookies: session identification and request protection. The session duration for this installation is 120 minutes.
- Remember-me cookie: if you select “Remember me” at sign-in, an authentication cookie keeps you signed in for longer until it expires or is revoked.
Cookies used for identification are encrypted and HttpOnly where applicable; the XSRF token is readable by browser scripts for request protection. Secure transmission depends on the deployment's HTTPS configuration. Cookies are not used here for advertising or analytics.
Without cookies
You can browse public pages and join a queue. A temporary, queue-specific access token is stored in this tab's session storage so the controls and refreshes work without cookies. It expires after 24 hours and is not intended to survive closing the tab. The token grants access to your queue entry; do not share it. If browser storage is unavailable, the token stays only in page memory and refreshing loses access.
Persistent return-to-queue membership, account sign-in and account management need accepted cookies. Appearance preferences may use browser local storage. Clearing site data removes these preferences and temporary tokens.
Queue names, IP addresses and blocks
We store the name you enter, your IP address at joining, a hashed visitor identifier, queue status and timing. Your queue host can see your name, IP address, duplicate-IP highlights and whether you are away. Other visitors are not shown your name or IP address.
Hosts may decline an entry or block an IP across their queues. A block stores the name recorded when blocked, the IP address and the date. Blocks remain until the host removes them or the host's account is deleted; deleting a queue or controller does not remove its host's block list. A shared IP can represent several people.
Queue entries remain in the database until the queue or its controller is deleted, or the entry is replaced when you rejoin. Cookie expiry does not automatically delete server records. Contact your event or queue host about your entry or an IP block.
Leaving and returning
With accepted cookies, closing a waiting page preserves your position. Return using the same queue link in the same browser before your turn. If you are marked away when you reach the front, you are skipped. A five-second grace period protects refreshes. Close detection is best-effort, not a heartbeat timeout.
Leave queue immediately gives up your place; rejoining puts you at the back. Normal turn endings and voluntary departures leave the machine on its last settings.
Accounts, controllers and service providers
Account records include names, email addresses and hashed passwords. Saved shared API tokens are encrypted on the server. The server sends machine commands to the configured FY API to operate the selected machine; visitors do not receive the shared API token.
The hosting provider, load balancer and configured email service may process request logs and account emails. Their retention and any database backups are controlled by the operator of this installation. Contact that operator or your event host for questions or requests about stored information.