Legal

Cookie policy

Last updated August 2026

Overshove uses a small number of cookies and local storage entries. Most are essential to keep you signed in, keep the app working offline, remember your preferences, and protect the service. We do not run advertising trackers, retargeting pixels or third-party behavioural ad cookies.

Facing an empty chair, two face-down cards lie beside a white chip stack on dark poker felt

Which cookies and storage does Overshove use?

Overshove uses storage for five clear jobs: authentication, sync, offline work, preferences and basic product measurement. The table below explains what each type does and whether you can turn it off. Exact key names may change as the product develops, but using storage for a new purpose would require this policy to be updated.

Cookies and local storage used by Overshove
Type	Purpose	Can you turn it off?
Authentication cookie	Keeps your account session active after login, so you do not have to sign in on every page.	No, not while using the logged-in app.
Local app storage	Stores queued session edits and settings so the app can recover if the connection drops.	No, offline support depends on it.
Preference storage	Remembers display choices such as theme, currency symbol and dismissed product notices.	Yes, by clearing site data, but it resets the choices.
Technical error monitoring	The current app sends no crash reports to any third party.	Not applicable: no third-party crash reporting is used.
Optional usage analytics	If you choose Allow in Settings, Usage analytics, Overshove stores three first-party milestones in its own database through Supabase: account created, first session logged and first useful result viewed, with account ID, build and time. It never includes poker records, notes, venues, exact results or anything about gambling harm.	Yes. It stays off until you choose Allow. Choosing Do not allow stops new collection and deletes unsent events.
Public website analytics	Google Analytics and Microsoft Clarity help us understand visits and improve the site. They stay off until you accept analytics, and no form values are sent.	Yes, choose Reject in the website consent banner.

Overshove does not use advertising trackers, cross-site retargeting cookies or brokered audience pixels.

Essential storage

Sign-in sessions, your settings, and local data that lets the app work offline are essential. Turning them off would break the core product: you would be signed out, queued sessions could not sync cleanly, and the app would forget the preferences that make the log usable on your device.

Technical error monitoring

The current app sends no crash reports to any third party.

Which analytics tools does Overshove use?

Overshove uses analytics to check whether the app and website work, not to build an advertising profile. Google Analytics and Microsoft Clarity stay off on the public website unless you accept analytics in the consent banner.

In the app, optional usage analytics are first party and stay off until you choose Allow in Settings, Usage analytics. They record only three milestones in Overshove's own database through Supabase: account created, first session logged and first useful result viewed, with account ID, build and time. Choosing Do not allow stops new collection and deletes unsent events. The app analytics do not send session replay, heatmaps or broad autocapture. Private session contents, notes, venues, exact results, form values and anything about gambling harm are not sent as analytics properties.

How do you control cookies and analytics?

Use your browser settings to manage cookies, the website consent banner to control website analytics, and your account settings to control product analytics. Rejecting analytics or withdrawing consent stops new optional collection. Clearing site storage removes your saved website consent choice, signs you out and resets local preferences. If you have unsynced changes, open Overshove online and let it sync before clearing storage or those local-only changes may be lost.