Your board stays under your control
Minesweeper Coach performs solver and daily-game calculations in your browser. During ordinary browser use, it does not upload a board, cell values, coordinates, screenshots, filenames, or free text.
Last updated: September 7, 2026.
Local progress
Daily completion dates, elapsed time, hint count, attempt count, and streak are stored in this browser’s Local Storage under a versioned key. Clear this site’s browser data, or use the reset action shown when stored data cannot be read, to delete it.
Analytics boundary
Cloudflare Web Analytics measures page visits and web performance without cookies. Google Analytics 4 uses first-party analytics storage for automatic page views and receives typed, low-cardinality product events from an explicit allow-list. These events contain coarse device/referrer classes, preset names, result status, rule type, latency buckets, daily puzzle ID, returning flags, and bucketed completion counts.
Google Signals and advertising personalization remain disabled. Board state, exact cell coordinates, screenshots, free text, and Local Storage contents are never included in analytics events. Site-tool analytics contains only the fixed tool name, whether it is a read or write tool, and success or error.
Optional Site tools
When you open the Solver in a compatible ChatGPT built-in browser and enable Site tools, that browser can ask you to approve tools that read or change the same visible board. An approved read can share the visible board and solver result with the agent. An approved write changes only the in-page board; it cannot access hidden mines or invent the clue revealed in your separate game. Browsers without WebMCP support receive the ordinary site with no Site tools.
External requests
The site downloads its application, styles, and daily puzzle JSON from its own origin. In production, the browser also loads Cloudflare’s Web Analytics beacon and Google’s analytics script, then sends page-performance measurements to Cloudflare and the allow-listed product events to Google Analytics. Network services can receive standard request metadata such as IP address and user agent. Solver computation remains local; board data is shared only when you approve a compatible Site-tool invocation.
The project contains no LLM, Vision API, paid API, account system, or database.
Advertising status and future disclosure
The site does not currently serve advertising. It publishes an AdSense account-verification meta tag and an ads.txt authorized-seller record. These public text markers do not load an ad, set advertising storage, or send a request to an advertising service.
If Google AdSense is enabled after site review, third-party vendors including Google may place or read cookies or other local storage, and may use web beacons, IP addresses, or other identifiers to serve and measure ads, prevent fraud and abuse, and—where permitted and consented—personalize advertising. Google and its partners may use advertising cookies to select ads based on visits to this site or other sites. Read how Google uses information from partner sites.
You can control personalized advertising in Google Ads Settings. Before any additional third-party ad vendor is enabled, its identity, purpose, privacy information, and available opt-out controls will be disclosed through this page or the consent interface.
Consent for European advertising
Before serving personalized ads to visitors in the European Economic Area, the United Kingdom, or Switzerland, Minesweeper Coach will publish a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. The message will identify the selected advertising vendors and purposes and request consent for cookies or other local storage where legally required, and for collecting, sharing, and using personal data for ads personalization.
AdSense ad code will remain disabled until the site-specific consent message is published and verified. The current site therefore has no advertising-consent control because it makes no advertising request.
Retention measurement
Local completion history can identify a returning browser and emit a coarse return event without sending that history. Google Analytics can use its first-party analytics identifier to distinguish browsers and sessions; the site does not provide an account ID or other user identifier.