A little about privacy.
We collect first-party usage statistics: home and discovery page visits, game page openings, Play selections, ready screens, pages reporting a runtime error, game starts, active play time, ended runs and completed playthroughs. Instrumented adventures also report the chapter, area and scene being shown, named interaction targets, puzzle attempts and outcomes, hints, meaningful story steps and known game errors. Entry observations include the released build identifier, but no error message, URL, or stack trace. This helps us find confusing or broken moments and decide what to improve. Discovery visits identify the published page using a fixed page name, without its query string. We do not record your screen, typed input or clipboard.
A random identifier stored in your browser helps estimate distinct visitors and players. It does not contain your name or email. Clearing storage changes that identifier; visitor totals describe browsers, not identified people. We also record a browser-session identifier, basic browser and operating-system families, device type, and signals such as a browser reporting automated control. A keyed hash of the connection IP helps compare networks. Combining that with basic device information gives a possible device grouping, not a verified person. Shared networks and similar devices can look alike.
Raw connection IP addresses are kept separately for seven days after their latest recorded activity and are visible only in the protected owner dashboard. Browser-linked visits, play sessions and scene summaries expire after 180 days; detailed event timelines expire after 30 days. Daily totals and grouped campaign/source summaries, without browser or IP identifiers, have no automatic expiry. Database cleanup can take a little longer, but expired raw IPs are hidden from the dashboard immediately. We use these records to filter our own testing and suspected automation.
We record a referring website’s hostname and bounded campaign labels such as source, medium and campaign name. We do not collect the full referring URL or arbitrary URL query strings. Campaign labels may stay in this tab’s session storage for 30 minutes to connect an arrival to later game activity. We do not use advertising trackers, canvas or font fingerprints, or share analytics with an advertising network.
Active time excludes hidden tabs and recognized game pauses. A sudden close, lost connection or blocked collection can leave a run incomplete or lose diagnostic detail. Chapter One full playthroughs count its completion screen. Each current arcade game has a defined challenge. We count an ended attempt separately from completing that challenge. Older endless games and golf retain their original historical meanings.
If you earn a top-five arcade score, you may choose a name of up to six characters. That name and score are public. Don’t enter private information you do not want other players to see. Scores come from browser gameplay with server checks; this is a casual leaderboard. Entries remain until displaced.
Your saved story progress, sound preference and arcade personal bests remain in your browser. Personal bests are separate from public leaderboard entries and do not sync between devices. A pending Chapter One completion report may also be saved there until the server confirms it or its four-hour run window expires, allowing a short interruption to recover without duplicating the finish. The web server keeps operational request logs. Owner sign-in uses a secure session cookie and is separate from playing.
You can clear the site’s browser storage using your browser’s site settings. Doing so also removes locally saved story progress.