Cookies and storage
1. What the product uses
PokerView uses session cookies and also local browser storage. They are different mechanisms: both are described here because they both preserve state on the device.
The homepage statistics widget queries aggregated totals via a public request without credentials; that query does not create cookies or local storage. Like any web request, it may be part of the technical infrastructure logs described on the privacy page.
2. Functional inventory
| Use | Mechanism | Observed Purpose |
|---|---|---|
| Supabase Session | Essential cookies | Maintain and renew authentication. |
| Theme and interface | Local storage | Remember theme, onboarding, notices and changelog version viewed. |
| Flows in progress | Local or session storage | Retrieve session drafts, presets, MTT templates, alerts and the latest summary. |
| Diagnostics choice | Local storage | Remember if Sentry in the browser is allowed or disabled. |
| Sentry in browser | SDK Network and Storage | With permission only: errors, traces, Web Vitals and masked Replay. |
Drafts can include data from the current session. Don't use a shared device without signing out and clearing site data.
3. Optional diagnostics
Without permission, the browser's Sentry integration does not initialize. Allowing it activates error capture, a performance sample, Web Vitals and Replay. Replay masks text and blocks media, but is still optional telemetry.
Optional diagnostics: undecided
You can change your choice at any time. Turning it off stops new capture in the browser; a send that has already started may finish, and events sent with permission are not deleted.
4. How to clear local state
Browser controls allow you to delete cookies and site data. Doing so will log you out, forget preferences, and may delete unsynced drafts. PokerView does not integrate advertising cookies or commercial profiles in the audited code.
Last technical revision of the content: July 18, 2026.