Cookie Policy
Beat 65 does not currently use advertising or cross-site analytics cookies. This page explains the essential browser storage used to run the game and keep accounts signed in.
1. What this policy covers
Browsers can store small pieces of information through cookies, local storage, IndexedDB, and similar technologies. This policy uses “browser storage” as a collective term for those technologies.
2. Storage Beat 65 uses
- Firebase Authentication storage keeps your guest or connected account signed in and securely refreshes authentication credentials.
- Active-game storage remembers the identifier of an unfinished game so it can be restored after a reload or browser restart.
- Daily-game storage remembers a completed daily result on the device and helps provide a consistent daily experience.
- Infrastructure security may use short-lived or essential mechanisms needed for request routing, fraud prevention, and service reliability.
3. What we do not currently use
Beat 65 does not currently place advertising cookies, sell cookie-derived profiles, or use third-party cookies for cross-site behavioral advertising. If we introduce optional analytics or marketing technologies, we will update this policy and request consent where applicable.
4. Google sign-in
When you choose Google sign-in, Google may use cookies and storage on Google-controlled domains to authenticate your account. Google controls those technologies under its own policies; Beat 65 does not receive your Google password.
5. Managing browser storage
You can clear or block browser storage using your browser settings. Because the storage described above is necessary for authentication and game continuity, blocking or deleting it may sign you out, create a new guest identity, or remove the ability to restore an unfinished game on that device.
6. Changes and contact
We may update this policy when our use of browser technologies changes. Questions can be sent to tom@sailmcp.com.