Small stats. No personal profiles.

Optional analytics help us understand visits, rounds, eliminations and replays. They are separate from multiplayer messages.

• A random visitor ID rotates on the next visit after 30 days. A random session ID lives in this tab's session storage and rotates on the next load after 24 hours. These are anonymous browser identifiers, not proof of someone's identity.
• Our Worker converts those IDs to keyed hashes before writing analytics. Each match has a random ID. No nicknames, room codes, chat, raw IP addresses, fingerprint, precise location, full URLs or referrers are written to custom game analytics.
• Optional utm_source, utm_medium and utm_campaign accept short letters/numbers/underscore/hyphen campaign codes. Please never put personal information into campaign codes. Other query fields and click IDs are ignored.
• A small tab-local retry queue holds only these events; we retry them for at most 24 hours and discard expired entries when the game runs again. Server deduplication hashes expire after 7 days. Cloudflare Analytics Engine currently retains its event dataset for 3 months; this game does not export it to another database.
• Multiplayer servers record anonymous match totals and human eliminations without browser IDs. These aggregate game events continue when optional browser analytics are disabled. CPUs are excluded from unique player counts and tracked eliminations.
• The separately provided Cloudflare Web Analytics page beacon is loaded only when optional analytics are enabled. Cloudflare operates the hosting service and receives network requests; this notice describes what the game itself stores, not all infrastructure processing.

Open Privacy on the home menu to turn optional analytics off. This clears analytics IDs and pending events, and reloads the menu. Global Privacy Control and Do Not Track are respected automatically. Game progress, nickname and multiplayer room data are independent of analytics and are not cleared by this setting.

Counts are estimates: blocked requests, cleared browser storage, ID rotation and Cloudflare sampling affect them. The admin dashboard contains aggregate statistics and is password protected.