Game analytics

Public games can be launched without signing in. We count qualifying detail views and valid launch requests; these do not prove that a game loaded or was played.

Visitor identification and account association are optional and off by default. If enabled, a random HTTP-only first-party cookie lasts 30 days. We store its digest, not the cookie value. Switching it off removes the cookie and stops future identification. Previous minimized records expire under the retention policy.

Raw events normally expire after 90 days; daily aggregate counts normally expire after 730 days. These periods are configurable. Estimates cover consenting visitors only and can undercount or count the same person more than once. Older reporting may show summed visitor-day estimates.

No third-party analytics cookies, advertising identifiers, browser fingerprint, precise location, raw IP or full destination URL are stored in analytics. Developers see counts for their organizations; authorized platform administrators see aggregate reports. Optional account associations are cleared when an account becomes inactive.

A qualifying view is a visible detail page remaining open for one second, deduplicated for ten minutes in that tab where browser storage is available. Requests from browsers remain untrusted. Contact the platform operator for deletion/export requests; identity verification and a scoped operations procedure are required. Production privacy and consent acceptance remains a release gate.