The short version
We use three kinds of storage: what the site needs to work, the bot check that keeps the public forms usable, and Google Analytics to count how pages are used. No advertising cookies, no ad targeting, and we never sell or rent your data.
Analytics runs without asking first. There is no on-site switch to turn it off — if you do not want it, the browser controls below are the way to refuse.
What we store
Theme preference — choosing light or dark mode saves a playset-theme
value in your browser’s local storage. It never leaves your browser.
Privacy notice — dismissing the notice strip on a game site saves a
playset.privacy-notice value so it stops appearing. It records only that the
notice was seen. It is not a consent record, because nothing on the site waits
for it.
Signing in — signing in sets a session cookie on account.playset.pro, and
each game site you sign in to sets its own session cookie for that site. These
are strictly necessary for staying signed in, and signing out clears them. A
non-identifying hint cookie, playset_has_session, is also set so pages can
render your signed-in header without a round trip; it carries no identifier and
grants no access to anything.
The bot check
Cloudflare Turnstile runs on the public forms where a script pretending to be a person would do real damage:
- on account.playset.pro — sign-in, sign-up, password-reset and the resend-verification form;
- on the game sites — the report form at
/report, which is how you tell us a card value is wrong, report a deck or a profile, or say that a page is broken.
Its widget is loaded from challenges.cloudflare.com — a third-party script,
and the only one besides the analytics tag below — and it may set a short-lived
cookie on Cloudflare’s own domain to remember that you have already passed, so
you are not challenged again on the next form.
It is strictly necessary in the plain sense of the phrase: without it those
forms can be hammered by scripts, which is how accounts get taken over and how
a report queue becomes useless. There is no switch for it, and blocking
challenges.cloudflare.com will stop those forms from submitting. It reports
only pass or fail to us, is not used to count, profile or advertise, and runs
on nothing but the forms named above — playset.pro has no forms and does not
load it at all.
Analytics
Game sites in the network run Google Analytics 4. The measurement script is
loaded from googletagmanager.com, which makes it a third-party script, and it
sets first-party cookies in your browser — typically _ga and a
_ga_-prefixed cookie for the property, which persist for up to two years.
It is used to count page views, referrers and broad audience information so we can tell which pages are worth writing more of. We do not use it to build advertising audiences or to personalise ads.
It runs on your first page view, before you interact with the notice. We tell you it is there rather than asking permission first. That is a deliberate choice on our part, and this page exists to make it visible rather than discoverable.
Google processes this data as our analytics provider, under its own terms, and may process it outside your country. Retention is governed by the property’s own configuration in Google Analytics.
playset.pro itself — this site — carries no analytics, no bot check, and no third-party origin of any kind: the fonts are served from this domain and the share images are our own files. The only script it runs is a few lines, inline, that restore your theme choice before the page paints. Every page here is complete without it.
Refusing analytics
Because there is no on-site opt-out, refusing means using your browser:
- Block or clear cookies for the site in your browser’s settings. Clearing also signs you out and resets the theme to its default.
- Google’s opt-out browser add-on, which stops Google Analytics reporting from any site you visit.
- A content blocker or a browser that blocks trackers by default, which
will stop the script loading. Nothing on our sites depends on the analytics
tag, so everything keeps working. The bot check is the exception and is not
analytics: block
challenges.cloudflare.comand the forms it guards stop submitting.
We do not detect, penalise, or work around any of these.
Questions
Write to [email protected].