← Back to home
Short version: BasalMind uses exactly one cookie to remember that you accepted this notice. Anonymous play creates no identifiers in your browser. Sign-in stores a session token in local storage — not a cookie — and only after you authenticate.

What is a cookie?

A cookie is a small text file stored in your browser by a website you visit. Most commercial sites plant dozens of cookies for analytics, advertising, and cross-site tracking. BasalMind does none of that.

The one cookie we use

Local storage

We do not write anything to local storage during anonymous play. No player ID, tracking code, or identifier is created until you sign in.

After you sign in with Google, your session token is stored in local storage to keep you logged in across page loads. It is cleared when you sign out. It contains no personal data beyond the session reference — your account data lives on our server, not in your browser.

What we do not use

We do not use analytics cookies (Google Analytics, Mixpanel, etc.), advertising or retargeting cookies, cross-site tracking cookies, fingerprinting scripts, or third-party social media embeds that set cookies.

How to remove the cookie

To remove the cookie_consent cookie, clear cookies for this site in your browser settings:

Most browsers: Settings → Privacy → Cookies → See all cookies → remove basalmind.com

Removing the cookie will reset the consent banner. It will not affect your ability to use the site.

Your rights

Under GDPR (EU/UK) and CCPA (California), you have the right to know what data is collected about you and to request its deletion or export.

The cookie_consent cookie contains no personal data. If you have signed in, your account data (email, gamer ID, gameplay records) is subject to the full data rights described in our Privacy Policy, including the right to a signed deletion certificate you can independently verify.

To exercise your rights: sign in and visit /data-rights, or email [email protected].

Changes to this policy

If we add a new cookie we will update this page before it is active and note the change in the effective date above.