Cookie Policy

Last updated: 31 July 2026

This describes exactly what ChudGames stores in your browser. It is short because we store almost nothing.

We set one cookie

That is the entire list. There is no analytics cookie, no advertising cookie set by us, and no preference cookie — the site’s settings are stored in your browser’s local storage instead and never sent to us.

What is in it

A random identifier and nothing else. It carries no email, no user id, no role, and no signed claims — it is a lookup key for a session record on our side, which means signing out actually invalidates it rather than merely forgetting it.

Its attributes: HttpOnly (JavaScript cannot read it), Secure (HTTPS only), SameSite=Lax, the __Host- prefix, and no Domain attribute — so it is sent only to the exact host that set it, and browsers forbid any other subdomain from setting or overwriting it. That is a deliberate security boundary: game code runs on a different origin and must never be able to read or replace your session.

Games and cookies

Games run in a sandboxed frame on their own separate origin, one per game. Browsers partition storage by origin, so:

• a game cannot read your ChudGames session;
• a game cannot read another game’s storage;
• storage a game creates belongs to that game alone.

Some games save progress locally in their own storage. Clearing site data for that game’s origin clears it.

Advertising

Ads are served by Google. The ad script may set its own cookies subject to consent, and our consent signals default to denied — including ad_storage, ad_user_data and ad_personalization. We do not set advertising cookies ourselves.

Games that require a particular browser security mode load with no ad script at all.

Refusing cookies

Blocking chud_session means you cannot sign in. Everything else — browsing and playing — works without it, because playing does not require an account.

Changes

We will say what changed and when.