Your choice comes first
Optional audience analytics starts only after you choose Allow analytics. Refuse analytics is equally available. You can reopen Analytics choices in the footer and withdraw permission at any time without losing access to the website or game.
BotFight and Brickworld manage their own choice on their own domain. Allowing one does not create a shared player identity or automatically enable the other. Do Not Track or Global Privacy Control takes priority over a saved Allow choice.
Essential browser storage
- BotFight community uses the host-only botfight_actor cookie to recognize the same browser guest, show their own submissions and enforce posting limits. It can last up to one year. It is HttpOnly, Secure on HTTPS and separate from game identity and analytics. Administrators use a separate HttpOnly session cookie lasting 30 minutes. Clearing the guest cookie creates a new guest identity and does not delete earlier messages.
- Brickworld uses its own necessary session cookie for guest or account entry. It can last up to 30 days and is not an advertising or analytics cookie.
- A versioned analytics allow/refuse preference is stored locally in the browser for up to 180 days. It records a choice, not a visitor identifier. Once it expires or storage is cleared, optional analytics requires a fresh choice.
- The Hero’s optional coordinates stay in page memory for the local sunlight calculation. They are not an analytics identifier and are not sent to the collector.
What optional analytics does
Our self-hosted Umami collector uses limited page and interaction events. The frontend communicates directly with that collector; it does not automatically load an analytics SDK or monitoring service. No audience-analytics cookie is required, but browser information and connection data are still processed.
Allowed collection can include cleaned paths and referrers, language, screen size, browser/device information, approximate IP-based location and server-derived daily visit/session identifiers. It excludes search text, messages, email, coordinates, nicknames, account identities and game session tokens.
Cookieless collection is not a promise that no information is collected or that consent rules never apply. We use a separate choice for this optional processing rather than making it a condition of gameplay.
Changing or clearing a choice
Use the footer’s Analytics choices control to change the setting. Refusal or withdrawal stops future optional events; it does not erase earlier records automatically. You can request deletion where a record can be located and applicable law provides it.
Browser storage settings can clear the saved choice and essential game cookie. Clearing a cookie can sign you out or remove a guest’s means of returning to a saved profile, but it does not delete the saved server world. Keep any recovery information provided by the game.
Browser signals, blocked network requests or collector failure can prevent statistics even after allowance. We do not store an offline event queue to send later. Core site and game functions continue if analytics is unavailable.
New tools or purposes
These settings cover the currently described audience statistics only. Advertising, replay, new optional purposes or new providers would require a review, updated notices and any new permission that applies. We do not treat agreement to the Terms as analytics consent.