Privacy Policy

We use privacy-minimised, first-party counts to understand daily page views, estimated daily visitors and download-button activity. Changing, scope-specific one-way daily identifiers are used for visitor estimates; raw IP addresses, full user-agent strings, query strings and referrer URLs are not stored in the analytics tables. Daily identifiers older than 35 days are cleared during subsequent site activity.

The Players counter starts from the value saved by the site owner and adds one when a new browser first opens that game page. A random HttpOnly first-party token is kept for up to 400 days so refreshing or returning from the same browser does not add again. Only a game-specific one-way token hash is stored for each visited game; the raw token, IP address and full browser string are not stored in that counter table, and hashes saved for different games cannot be matched to one another. These per-game hash records remain with the counter until the starting value is changed or the game is deleted. Clearing or refusing browser data can cause a later visit to count again. Browser Do Not Track and Global Privacy Control signals are respected, and administrator, recognized automated, prefetch and quality-assurance traffic is excluded.

If the owner connects Google Analytics or Google Ads, those optional Google tags load only after a visitor chooses Allow analytics in the consent prompt. You can decline and continue using the site, or reopen Analytics choices in the footer later. Google then processes data under its own policies.

If you contact us, we use the details you provide only to respond. We do not ask for game account passwords, OTPs or payment credentials. Third-party websites have their own privacy practices, so review their policies before submitting personal information. Contact us if you need to request access to or deletion of information you submitted directly to this website.