PRIVACY

What we count,
and what we don't.

Seashore Games has no accounts, no sign-in and no cookies. Two kinds of anonymous counting happen, and you can switch the gameplay one off below.

Site traffic

Cloudflare Web Analytics counts page views, referrers, countries and device types. It is cookieless, uses no fingerprinting, and is the same measurement Cloudflare offers every site it hosts.

Gameplay

When you open a sport or play a match, the game records which sport, whether you played or watched, the team size, the graphics setting, how long the match ran, whether it finished or was left, and the final score. These rows go to a database we run ourselves. Each row carries:

Seashore Games stores approximate country, region/state, city, and timezone derived from Cloudflare IP geolocation for aggregate analytics. We do not store visitor IP addresses, latitude/longitude, postal codes, or other precise location information in our analytics database.

Nothing else. No name, no email, no full address of the page you came from, nothing you type. Your saved player, career and settings stay in your browser and are never uploaded — the one exception is the Daily Challenge below, and only if you choose to play it.

How you found us

Seashore Games may store coarse acquisition information, such as campaign labels from UTM parameters and the referring website domain, for aggregate analytics. We do not store full referring URLs, referrer paths or query strings, arbitrary landing-page parameters, or visitor IP addresses in our analytics database.

Daily Challenge

The Daily Challenge is the one part of Seashore Games that publishes anything. Playing it is the choice: if you never open it, nothing described in this section happens, and the rest of your saved player, career and settings stay in this browser as always.

When you finish a Daily Challenge run, the game sends your result for that day’s public leaderboard. Starting one and quitting sends nothing. What is sent and kept:

The leaderboard never shows, and we never publish, an email address, an IP address or anything derived from one, your gameplay-analytics player id, or any text you have typed. To be precise rather than flattering: the server does store a value that identifies your browser as a returning challenge participant — that is how your attempts stay on one row and how your personal best improves. It is a one-way digest of the random id above, it is never returned by the public leaderboard, and it is not linked to anything else we hold. We call the alias anonymous because it reveals nothing about you, not because no identifier exists.

Retention. Participant-level challenge records — that digest, the alias and your best result — are kept for 90 days and then deleted. Non-identifying aggregate statistics for a challenge may be kept longer: the date, the game and format, how many people took part, how many runs were finished, and the leading result. Those aggregates contain no participant identifier and no alias.

Turning gameplay stats off below does not stop you playing or entering the Daily Challenge, and entering the Daily Challenge does not turn gameplay stats back on. They are separate choices. Clearing this browser’s site data removes the random challenge id, so you become a new anonymous participant; entries already on a leaderboard stay there, but you can no longer add to them.

Because the game runs entirely in your browser, leaderboard results are reported by the browser that played them. We check that a result is possible for that day’s challenge, but we cannot prove it was earned. Treat the board as friendly competition rather than a refereed record.

This setting lives in this browser only. Turning it off stops events from being created at all — nothing is queued, nothing is sent. Browsers that send a Global Privacy Control signal are treated as opted out automatically.

← BACK TO THE BEACH