Updated 17 October 2026

Privacy

Ohm Sleuth Daily currently runs without player accounts, email collection or advertising. It uses Cloudflare Web Analytics for aggregate website usage and performance statistics. It stores limited gameplay information so you can resume the daily mission and use the tutorial.

In your browser

The game keeps a random daily-session identifier in localStorage so refreshing or reopening the same browser can retrieve today’s progress. No daily score, measurement history or gameplay snapshot is saved there. The identifier is replaced when a new daily session begins; the old identifier no longer retrieves progress after the daily reset. Clearing site data removes the link to your current game. This storage is used only to provide game resumption, not advertising or analytics.

The former optional browser-progress save and its preference are removed when this version loads. Tutorial session identifiers, steps and completed actions use sessionStorage, which normally lasts for the tab’s browsing session. The app does not set cookies. There are no accounts, email addresses or cross-device player profiles.

On the game server

The shared calendar retains its random seed, start date, circuit order and current daily assignment. In a separate temporary database, the server saves today’s anonymous gameplay progress: environment settings, probe positions, unique measurements, incorrect guesses, spending counts, completion/replacement state, the latest 50 notebook entries and internal request identifiers. Waveform arrays are not saved to disk.

Player progress expires at the next midnight in America/Chicago, when the next mission becomes available. There is no extra 24- or 48-hour retention period. The running server checks rollover approximately every half second and purges expired records before serving a new daily date. If it was offline, it performs that purge at startup before accepting requests. Expired data is overwritten in SQLite’s freed records and the player database is compacted; it is not retained as a daily history.

RAM caches remain limited to 64 workbench sessions, with idle entries evicted after 30 minutes and old sessions removed at the daily reset. In-flight work is discarded when it finishes if the day has changed, and cannot save yesterday’s progress again. Today’s stored progress can restore an evicted session or survive a server restart. Tutorial sessions are RAM-only and must be restarted if lost.

Session identifiers should be treated as private: someone who obtains yours could access that session. Player databases must be excluded from calendar backups. Host snapshots or third-party logs have separate retention settings; the public deployment’s policy must account for them.

Sharing your score

Copy score writes the daily mission number, date, cost and measurement/incorrect-flag counts to your clipboard when you request it. The text contains no solution or session identifier. Nothing is posted to a social network automatically; you choose where to paste it.

Technical logs and hosting

The app records request methods, recognized route names and response status codes, omitting query strings, arbitrary paths, request bodies and client IP addresses from its access logs. Error diagnostics may also be recorded. These logs are handled by the server’s system journal; their retention is controlled by the host rather than the daily gameplay reset.

Cloudflare provides the public connection, HTTPS and security services. It processes connection information such as IP addresses and HTTP request metadata to deliver and protect the site. This processing is separate from the game’s temporary progress database. See Cloudflare’s privacy policy.

Web Analytics

Cloudflare Web Analytics measures aggregate visits, page views, referring sites, browser/device categories and page performance. Its browser script sends usage and performance measurements to Cloudflare. It does not use cookies or browser storage for analytics or fingerprint visitors. We do not send game session identifiers, guesses, scores or puzzle solutions to this analytics service, and do not use it to create player profiles.

Analytics is stored by Cloudflare, not in the game’s player database, and is not deleted by the game’s daily reset. See Cloudflare Web Analytics documentation for details. Browser content blockers may prevent these measurements.

Other services

Game scripts, images and libraries are served from the game’s own server; Cloudflare supplies the analytics script. Links on the licenses page lead to external projects only when you choose to follow them; those sites have their own privacy practices.

Your choices

You can stop playing and clear the game’s browser site data at any time. Server sessions then remain subject to the cleanup described above. Clearing browser storage does not erase existing technical logs. The server operator controls the local technical logs; Cloudflare processes its service data separately.

If accounts, email login, player statistics or advertisements are added, this notice and the data-handling controls will need to be updated before those features launch.

Opened this page from a game? Close this tab to return to that game without reloading it.