Cookies

Cookie Policy

Last updated: May 2026

"Cookies" here means small data Storage items your browser keeps on Playjar's behalf or on behalf of a third party loading inside the page — actual HTTP cookies, localStorage entries, sessionStorage entries, and similar. Below is the complete list and how to turn each off.

From Playjar itself

Playjar doesn't set any first-party cookies. The site is static HTML; there's nothing to remember server-side. Should you ever see a localStorage entry from playjar.cc, it'll be a transient UI preference (e.g. dismissed notification) that you can clear from your browser's storage settings without affecting your ability to play games.

From Cloudflare

Cloudflare may set a __cf_bm cookie for bot management. It's a security cookie, doesn't track identity, and expires within 30 minutes. We use Cloudflare Web Analytics, which is intentionally cookieless.

From Google AdSense

When AdSense scripts run, Google may set a handful of cookies, including:

Manage these directly at Google Ads Settings. Setting personalization off there stops the personalized advertising behavior network-wide for your Google account.

From inside embedded games

Each game on Playjar runs inside an iframe served by a content partner (GameDistribution). That frame is a separate origin and can set its own cookies and storage under its own policy. Cookies from the iframe are blocked under modern browser third-party cookie policies in most cases.

How to refuse cookies, by category

What happens if you block everything

Playjar still works. Games still load and play. Ads will still appear but they'll be less relevant (which is sometimes more honest than the personalized version).

Updates

This policy is dated. If the set of cookies that Playjar or its partners use changes materially, we'll update both the date and the listing above, and post a notice on the home page for 30 days. Questions go to [email protected].