Your choices. Your games.

Playing SlopGames does not require optional analytics. Allow or refuse it using the Privacy control in the library, and change your choice at any time.

Optional website analytics

If you allow it, SlopGames stores a random browser ID for up to 90 days and remembers your choice for 180 days. We measure library visits, visible game cards, saves, search result counts, game launches, supported game starts and finishes, foreground time, broad device class, broad referral category, and categorized technical errors. The server stores a keyed hash of the random ID. These are pseudonymous browser measurements, not a count of identifiable people.

We do not collect your email, name, raw search terms, question answers, full referring URLs, browsing history, precise location, or raw error messages for analytics. We do not use fingerprinting or third-party analytics scripts. A short-lived keyed network identifier limits abuse; raw IP addresses are not stored in our analytics tables. Hosting providers may process network data to deliver and protect the website.

Optional unique network visitor counter

Consent version 2 separately explains an additional purpose: counting distinct consenting network addresses since this counter is activated. Earlier analytics consent does not enroll you. After you accept this choice, and only once network provenance has been verified and collection enabled, the server converts your address to a secret-keyed digest. It does not store the raw address. The minimal deduplication ledger contains keyed address digests, separate keyed deletion handles and references needed to count each address once. It contains no game history or per-visit timestamps.

This ledger is pseudonymous, not anonymous. Its records remain while this counter operates, independently of the 90-day retention of detailed analytics. Keeping them prevents repeat addresses from being counted again after old sessions expire. The public total is not a count of people: shared Wi-Fi and VPN addresses can group visitors, and changing addresses can count the same person again. Only freshly consenting eligible visits contribute; there is no historical backfill. Erasure can reduce the total.

A separate random deletion key is stored in your browser while this counter operates, until you successfully delete your measurements or clear browser storage. Opting out stops new collection but keeps this key so you can still request deletion. “Delete my measurements” removes the ledger contributions linked to that key; an address remains counted if another consenting browser still contributes it. The same address can be counted again if it is later observed with fresh consent after all its earlier contributions were erased. Clearing browser storage loses the ability to find those contributions. When the counter is permanently retired, its ledger becomes eligible for bounded cleanup; the operator must complete the purge. Temporary pauses do not erase the ledger or reset the total.

Game and website measurements differ

For our built-in games we measure starts, ends and foreground running time. Deadfall and Ravenhold send readiness, build ID and run lifecycle signals to SlopGames; measurement still depends on your SlopGames consent. Their current early-access builds do not save runs across reloads. For The Million we currently measure its launch, embedded document load and time its player is visible. Those measurements do not reveal the embedded game’s answers, completion, or actual gameplay time.

Public play totals

Public Plays is a cumulative count of consented, ready-linked game runs since measurement began. It includes normal gameplay by the owner but excludes admin tests and recognized automated traffic. A durable ledger keeps only the game, random run ID and counting time, without an account, browser or network identifier. These anonymous totals remain when detailed analytics expires or is deleted. Totals are best-effort game signals, not verified scores or unique people. The separate network visitor counter starts at its own activation time and currently covers eligible IPv4 visits to slopgames.live. It has no earlier IP history to backfill.

Retention and removal

Detailed website measurements (excluding the separately described counter ledger) become eligible for deletion after 90 days. Bounded cleanup runs when sessions are created or through an explicit owner maintenance action; inactive periods can delay cleanup. Choose “Delete my measurements” in Privacy to delete the retained analytics attached to the current browser ID, remove network counter contributions attached to the separate deletion key, and switch analytics off. Failed deletion keeps keys locally for retry. Short-lived public session receipts also carry the keyed deletion handle and consent version until expiry or deletion; this lets the server authorize and revoke counter contributions. Refusing analytics stops collection and removes the local analytics ID; retained measurements then age out. Deleting browser storage also removes the key needed to find those measurements.

Necessary storage and games

Your privacy choice, saved game list, recent games, sign-in and game progress serve separate website functions. Removing analytics does not remove those. The Million remains an independently hosted SlopGames game with its own browser-profile save cookie and database. Its functional save storage is required to continue that game.

Advertising

No advertising SDK is added by this analytics setup. Future advertising will need its own provider integration and appropriate privacy choices before it starts. Any imported revenue reports are aggregate business records and are kept separately from visitor measurements.

Browser Do Not Track and Global Privacy Control signals keep optional analytics disabled. This policy describes the implemented measurements; it does not cover future services before they are added.