Privacy | Richest Queue

Richest Queue is currently operated by an individual sole trader established in the United Kingdom and trading as Richest Queue. We use information needed to run General Admission, credits, earned ranking, passwordless account access, payments, support, moderation and measurement.

Public entry information

Your public entry may include ticket number, name or brand, pitch, destination link, project country, categories, logo or image, interaction totals, days at the rope, screen bookings and earned RQ Rank / Momentum information. Public tracking identifiers can include a search term, GitHub repository or organisation URL, YouTube channel, App Store URL or Google Play URL.

First-party measurement

Richest Queue may measure whether an entry was meaningfully shown, whether its ticket was opened and whether a visitor followed its outbound link. These signals are used to understand response, calculate Momentum and report the effect of paid attention. We may use privacy-safe browser-generated identifiers together with limited request information to reduce obvious duplicate or manipulated measurement.

External public signals

Where applicable, Richest Queue may collect public metrics associated with an entrant's tracking identity from supported providers and public services, including search-interest, development, video and app-store sources. These are measurements about the public project identity, not private analytics accounts supplied by entrants.

Project assessment

The email supplied at purchase is private and is used for receipts, account access, essential service messages, support and ticket recovery. Richest Queue does not require an account password. This browser holds a private ownership key. A short-lived, single-use email link opens a confirmation step on another device; confirming there signs in that device without signing out your other devices. Only the newest issued link works.

Account email and passwordless sign-in

The email supplied at purchase is private and is used for receipts, account access, essential service messages, support and ticket recovery. Richest Queue does not require an account password. Access on a device may be authenticated with a private browser ownership token. Access on another device may use a short-lived, single-use link sent to the account email.

For security, sign-in and recovery responses may not reveal whether a particular email is registered. Authentication tokens are not displayed publicly.

Payments, billing location and tax

Card details are handled by the payment provider and Richest Queue does not store full card credentials. Where needed to calculate or evidence applicable tax, the payment provider may collect billing address or other customer-location information separately from the public project country. Supported crypto payments may be verified on the relevant blockchain/payment rail. We do not store wallet seed phrases or private keys.

Upvotes and abuse prevention

Voting uses a server-issued browser cookie to recognize repeat votes. Measured response uses a separate browser-generated identifier. To reduce repeat voting or measurement abuse, Richest Queue combines these identifiers with limited network and browser information such as IP address and user-agent data to create a one-way identifier. Signals may be rate-limited, invalidated or reviewed where activity appears automated or abusive.

Owner reports

Owner reports may combine credits bought, earned and spent, bids, bookings, Richest Queue response metrics and earned-score movement. Losing bids are never shown publicly. These reports are visible to the owner unless a metric is separately presented on a public ticket or public evidence view.

The Pot

The public Pot value is derived from successful base payment values. Tax collected for a tax authority is not treated as Pot funding and does not expose additional buyer information.

Service providers and transfers

We use service providers where necessary to operate payments, hosting, email, security, analytics and public-signal measurement. Some providers may process data outside the United Kingdom. Where data-protection law requires safeguards for an international transfer, we rely on the safeguards applicable to the relevant provider and transfer.

Aggregate site measurement

We count page views, Radar project clicks, join interest, successful checkout creation and confirmed purchases using limited source and campaign labels. These marketing counts are separate from ranking evidence. We also count how many visitors are on the site now and how many came today, from the same privacy-safe measurement token, kept for eight days and shown only as totals. They do not use an additional tracking cookie or visitor identifier, and do not store raw referrer URLs or search queries. Optional browser events respect Global Privacy Control and Do Not Track. Daily marketing aggregates and checkout attribution are retained for 90 days; payment references used to prevent duplicate conversion counts follow transaction retention.

Retention

Public queue, rope and ranking history may be persistent. Transaction, account, measurement-abuse, support and moderation information may be retained where reasonably necessary to operate the service, prevent abuse, resolve disputes, maintain accounting records or meet legal obligations.

Your rights

Depending on applicable data-protection law, you may have rights concerning access, correction, deletion, restriction, objection or portability of personal data. These rights can be subject to lawful exceptions, including records we must retain for transactions, disputes, fraud prevention or legal obligations.

To delete your account data, write to us from the email you bought with. We remove that email and every sign-in from the account, and your messages to us. The public Ticket, its number and the payment records stay: the Ticket is a public record and the payments are accounting.

Last updated: 17 September 2026.