Cookies & privacy choices

Game and account storage

BrainiLab uses local browser storage to remember guest progress, game history, preferences and session state. Supabase provides authentication storage when a session is created, including a guest session. This storage supports the games and account features rather than marketing.

Optional Meta marketing

Meta Pixel loads only after you accept ad measurement in Manage privacy or choose Accept optional cookies. It measures page visits and completed scored games, and may use the _fbp and _fbc cookies and standard browser, device and page information. BrainiLab sends the game identifier and whether a game was Daily or Anytime; it does not send your email, account ID, answers or score as event parameters. Practice games are excluded.

Your marketing choice is stored as brainilab_marketing_consent_v1 for up to 180 days. You can change it using the button below. Rejecting marketing stops future Meta events and removes the first-party Meta cookies that BrainiLab can access. It does not delete data already received by Meta.

Manage privacy

Optional usage statistics

Google Analytics loads only when you accept usage statistics. It measures page visits, article reading signals, article-to-game clicks, game starts and completions, practice rounds, email registration requests and clicks to our social profiles. It may set _ga cookies. We do not send names, email addresses, account IDs, answers or scores as event parameters, and we remove query strings and URL fragments from page addresses sent to Analytics. Google advertising features are disabled. The statistics choice is separate from Meta ad measurement and is stored as brainilab_statistics_consent_v1 for up to 180 days. Rejecting statistics stops future events and clears accessible first-party Google Analytics cookies; it does not remove data already received by Google.

With statistics enabled, brainilab_growth_entry_v1 remembers a broad arrival channel and the public landing-page path in this browser. It expires after 30 minutes without measured activity and is removed when you reject statistics. It helps connect arrivals to game activity across pages and tabs. It stores no account identifier or search terms. A registration request does not mean a completed account registration.

Advertising

AdSense ownership is verified using a page meta tag and ads.txt. Verification itself does not load the advertising script. When ads are enabled, Google AdSense displays clearly labelled ads in selected spaces outside active games. Google’s consent message provides advertising choices where required, including accepting, declining and managing options. You can revisit these through Ad privacy choices when displayed in the footer. Accepting usage statistics does not accept advertising cookies.

How long browser data stays

Game history and preferences stay in this browser until you clear them or the application updates them; the marketing choice has the expiry described above. Clearing site storage can remove guest progress and sign you out. It does not delete records already stored on the server or close an account.

More information

See the Privacy page for account, rankings and contact information. You can also read Google’s privacy policy and Meta’s privacy policy for information about those providers.

Confirmed accounts and optional arrival attribution

We keep a private, deduplicated record of account confirmation to distinguish new confirmed accounts from anonymous guest profiles and repeat sign-ins. Our Growth dashboard shows aggregate counts and excludes team accounts.

If you accept usage statistics before signing up, this browser temporarily stores the broad arrival source, public landing-page path and registration-request time as brainilab_registration_arrival_v1. This expires after seven days. After confirmation, these values may be associated with your account in our private Supabase database. We do not send that account identifier to Google Analytics. No email, search terms, URL query strings, answers or scores are included in this attribution record.

Rejecting statistics clears the pending browser record. If you are signed in and the service is reachable, it also removes the stored arrival attribution for your current account. Clearing browser storage alone does not remove server records; you can use Contact & corrections for a removal request. Deleting the account removes its confirmation and arrival records. Missing attribution stays unknown and is not inferred.