Current cookie status
The current application does not intentionally set advertising, personalization, analytics, account, or shopping cookies. The PHP pages do not start a user session for ordinary browsing. Final infrastructure behavior must be checked again after production configuration because a proxy, consent platform, advertising provider, or security service could change the inventory.
Favorites and recent games
The keys coolmath:favorites and coolmath:recent are local-storage values in the current browser profile. They contain game slugs selected or opened on that device. The values stay local, are not synchronized, do not identify an account, and may be lost when browser data is cleared. A one-time same-browser migration preserves data under former development keys.
First-party measurement
The production-only /collect/ loader requests a same-site endpoint once per page load with browser language, local time, time zone, and referrer. It does not set or read an analytics cookie in the current implementation and does not access favorite or recent-game values. Localhost is excluded so development traffic is not sent.
Browser controls
Browser settings can display and delete site data or block scripts and storage. Blocking local storage prevents saved and recent-game preferences. Blocking scripts also stops games and production measurement. Server request logs can still be created when a page is requested because they are part of delivering and protecting the service rather than browser storage.
Future consent controls
Before advertising, cross-site tracking, fingerprinting, advanced analytics, or another non-essential storage technology is introduced, coolmath must document the provider, purpose, data, retention, legal basis or consent requirement, and withdrawal method for applicable regions. No placeholder publisher ID or consent claim is published.
Inventory updates
This page should be reviewed after changes to hosting, analytics, advertising, embeds, forms, accounts, games, or content-delivery services. A substantive change receives an updated effective date and corresponding Privacy Notice revision.