Skip to content
ADVANTAGE COUNT
Start hereAnalyzerFeaturesLearnMethodologyContact
Menu
Start hereAnalyzerFeaturesLearnMethodologyContactOpen account
Open account
LEGAL · v1 PRIVATE BETA

Cookies & browser storage

Last updated: 14 September 2026 · Notice version 2

This notice covers advantagecount.com and app.advantagecount.com. It supplements our Privacy Notice, which explains account data, providers, international processing and your rights. Questions: advantagecount@hotmail.com.

Cookies are small values your browser can send with web requests. Local storage keeps application records on your device; it is not automatically sent with each request. Both matter for your privacy.

1. Account cookies

These cookies are set on app.advantagecount.com. Names containing an ellipsis vary by project or sign-in attempt. Large values may be split into numbered cookies such as .0 and .1.

Cookies used by the account portal
Cookie and servicePurposeHow long it stays
Sign-in session
sb-…-auth-tokenAdvantage Count / Supabase
Keeps you signed in and lets the server verify your account. Contains authentication information, not analyzer history.Set for up to 400 days and renewed when the session is updated. Successful sign-out clears the session cookies. The browser may remove them sooner.
Sign-in verification
sb-…-auth-token-code-verifierAdvantage Count / Supabase
Links an email or Google sign-in attempt to the browser that started it. Additional sb-…-auth-token-flow-…-code-verifier and sb-…-auth-token-flows-code-verifier entries support pending attempts.Cleared as sign-in attempts are consumed or cleaned up. An abandoned entry can remain for up to 400 days unless you or the browser remove it sooner.
Analyzer file access
__Secure-ac-release-0_35_0Advantage Count
Authorizes loading protected analyzer files after account access is checked. Sent only for the analyzer release path and unavailable to page scripts.Up to 6 hours from issue, or until the access end time if sooner. Reissued when you open the analyzer; cleared by the portal sign-out route.

A cookie's storage lifetime does not promise that your session or beta access remains valid for that long. Access is checked separately. Closing the browser alone does not necessarily sign you out.

2. Records kept in your browser

Using the analyzer saves your work locally on app.advantagecount.com. Records are separated by account in the same browser profile. They do not automatically move to another device. Account separation is not encryption against someone with access to your device.

Local storage used by the analyzer and trainers
RecordPurposeHow long it stays
History, settings and trainingac.account.v1.…Sessions, rulesets, trainer progress, bet settings, card state and recovery copies.Until replaced or removed by the application, you or the browser. No automatic age-based expiry.
Account and restore recordsac.portal.account.v1.…Selects your current records and any retained copy from before a restore.Persists with your local data. Sign-out or expired access does not erase it.
Active-tab coordinationAccount record ending in ac.liveState.writer.v1Works with browser locks to prevent conflicting saves from analyzer tabs.Normally cleared when the active tab retires. An interrupted browser can leave a stale record until it is replaced or site data is cleared.
Earlier local recordsEarlier ac.* records and ac.portal.legacy-owner.v1Preserves older data and records which account chose to import it. Earlier records are imported only after your explicit choice.Original records may remain after import until you clear site data. Starting empty does not erase them.
Names of analyzer records

The account prefix is followed by one of these names. Older versions may have saved the same names without an account prefix.

  • ac.sessions, ac.rulesets, ac.trainer, ac.countTrainer.v1
  • ac.betRamp.v1, ac.betRamp.confirmed.v1, ac.actualBet.v1, ac.dynamicBankroll.v1
  • ac.liveState.v1 through ac.liveState.v9, ac.liveState.lastGood.v9, ac.liveState.status.v1, ac.liveState.writer.v1

3. Security checks and external services

Cloudflare delivers and protects both sites. Email sign-in also uses Cloudflare Turnstile, which processes browser and device signals to check for automated abuse. See the Turnstile Privacy Addendum.

Security cookies depend on the protection applied to a request. Cloudflare documents cf_clearance for challenge clearance and __cf_bm for supported bot protection. The latter expires after 30 minutes of inactivity when used. A clearance cookie's duration depends on the site's security settings. These are conditional examples, not a claim that both are set on every visit. See Cloudflare's cookie information.

Turnstile normally returns a verification token. It can additionally set a clearance cookie when pre-clearance is enabled. We are still confirming the complete set and exact expiry of cookies issued by the live security configuration; the account-cookie table above does not replace that check.

If you choose Google sign-in or open a social-network link, that service may use its own cookies under its own privacy policy. Downloaded analyzer backups are separate files under your control.

Invited payment testers can also open Stripe-hosted test checkout and subscription-management pages. Stripe may use its own cookies and security storage on those pages; see Stripe's cookie policy. Test checkout uses no real charges. Payment-test analyzer records stay in a separate local account namespace in this browser.

4. Your choices and deletion

We have not added advertising or audience-measurement cookies to the current beta. Reading this notice or accepting the Terms does not give consent to optional tracking. If optional tools requiring consent are introduced, you will be able to accept or refuse them before they operate and later withdraw your choice.

  1. Keep a copy first. In Account, choose Download my data, even if analyzer access has expired. If present, Download pre-restore backup saves the earlier recovery copy. Payment testers can separately choose Download test data in Payment testing, including after test access ends. Close other analyzer tabs if prompted.
  2. End your session. Use Sign out and check that it succeeds. Signing out does not delete local history.
  3. Remove browser records. Close Advantage Count tabs, open your browser's site-data settings, and remove data for app.advantagecount.com and advantagecount.com. This can remove records for every Advantage Count account using that browser profile.
  4. Remove separate copies if needed. Delete downloaded backups and repeat site-data removal on other browsers or devices. Deleting an online account through support does not remotely erase those copies.

Blocking required cookies can prevent sign-in or access checks. Blocking local storage prevents reliable saving and can stop the analyzer from opening. Clearing site data can permanently remove records we cannot recover. The public website remains available without an Advantage Count account.

For account deletion or another privacy request, contact advantagecount@hotmail.com. Read the Privacy Notice and Terms of Use for the current beta service.

Advantage Count

Independent blackjack analysis and practice. Manual inputs. No guarantee of winnings.

HomeAnalyzerCount TrainerDecision TrainerFeaturesLearning guidesMethodologyContactPrivacyCookiesTermsOpen account
© 2026 Advantage Count