Essential browser storage
A signed first-party session cookie identifies your browser's claim session. An opaque token in local storage backs up the same session, which can restore a recent delivery if an individual cookie is lost. A separate short-lived visit cookie supports request-security checks. These are functional site identifiers, not public usernames. The session cookie lasts up to 30 days; the visit cookie lasts up to 20 minutes. Local storage remains until you clear it. You can delete this site's data using your browser settings, but doing so may prevent recovery of account details.
Private claim records
A successful claim records its reference, assigned credential details, product, delivery state and creation time on the server. These details are only returned to the matching signed browser session, not to other visitors sharing the connection. Recent delivery records are retained for up to seven days and are removed during routine cleanup. Browser and connection cooldown records are kept for up to 30 days. We do not place account credentials in URLs, public rankings or analytics events. Download and protect your own copy rather than relying on browser recovery indefinitely.
Connection-based abuse protection
The server temporarily uses your connection address to apply request limits and verification checks. Longer-lived claim-limit records use a keyed hash rather than the raw address. IPv6 addresses are grouped by network prefix to reduce trivial address rotation. Because households, organizations, mobile providers and VPNs can share a public connection, separate people may share a cooldown. A hash is still a persistent service identifier; it is used for claim fairness, not to claim that we have verified your real-world identity.
Human verification
We use Cloudflare Turnstile on the claim form. It processes browser and connection information to assess whether a request is automated. Verification runs before an account can be assigned. Its processing is described in Cloudflare's privacy information. Public guides and help pages do not require completing the claim challenge. The verification service does not need the account credentials delivered to you, and our claim checks do not ask for a wallet seed phrase or an authenticator recovery code.
Leaderboard information
The public leaderboard contains masked player names, reported wager totals, the current period and update times. Your private claim details are not linked to displayed players. The server fetches and caches the data approximately hourly. Leaderboard data is served by this website; your browser does not contact the data feed.
Cookies are removable
We do not use an undeletable identifier or attempt to restore site storage after you clear all of it. Clearing only one storage mechanism can leave the session available in its other first-party backup. Removing all stored site data removes those browser-side recovery tokens; a connection cooldown may remain until it expires on the server. You can read the information pages without making a claim. If you do not want the essential storage associated with a claim, do not submit the claim form.
Retention and updates
Retention cleanup runs as part of normal website operation. Security-related records may need investigation if service integrity is affected, but the standard claim and cooldown limits described above are the normal operating retention windows. This policy describes the current website, not the privacy practices of any platform on which an account may be used. Review that platform's privacy policy separately. This page was last updated on 9 November 2026.