BetAtlas Cookie Policy
Effective date: 2026-05-22 Last updated: 2026-05-22
1. About this policy
This Cookie Policy explains how 4 BETTOR INSIGHT LLC ("BetAtlas," "we," "us," "our") uses cookies and similar technologies in connection with:
The BetAtlas mobile application (iOS and Android);
Our legal and marketing website at 4bettorinsight.com and the pages hosted under it (including this page, Privacy, Terms, and EULA); and
The in-app embedded browser we use to let you sign into your sportsbook accounts.
This policy supplements our Privacy Policy. Where this policy uses defined terms without defining them, they have the meaning given in the Privacy Policy.
2. What are cookies and similar technologies?
A cookie is a small text file that a website or app places on your device so the site or service can recognize the device on a return visit. Cookies can be session cookies (deleted when the browser is closed) or persistent cookies (kept until they expire or are deleted).
"Similar technologies" are other mechanisms that achieve a comparable effect, including:
Local storage and IndexedDB in a browser, used to keep state between visits;
SDK-managed local storage on a mobile device, used by software development kits (e.g. AdMob) embedded in our app;
Mobile advertising identifiers — the IDFA on iOS and the Android Advertising ID (AAID) on Android — which work like cookies for purposes of ad attribution and frequency capping;
Pixel tags and web beacons, which can be used to count visits and measure campaign performance.
For brevity, in this policy we use "cookies" to refer to all of the technologies above unless we say otherwise.
3. Where we use cookies
3.1 Inside the BetAtlas mobile application
The BetAtlas mobile application itself is a native Flutter app, not a web browser. Browser-style cookies are therefore not used to power the core dashboard, account, or analytics surfaces. We rely instead on encrypted local storage on your device to keep you signed in and to cache data the app has already loaded.
Two specific features in the mobile app do interact with cookies:
Embedded sportsbook sign-in browser. When you connect a sportsbook using the "cookie connection" flow, the app opens an in-app browser that loads the sportsbook's own login page. The sportsbook places its own cookies in that browser as it would in any desktop browser. When you successfully log in, we capture the resulting session cookies for that sportsbook only, encrypt them with AES-256-GCM, and store them so we can later restore your session and sync your bet history on your behalf. See the Privacy Policy, Section 3.1, for full details. We do not capture cookies for any third party other than the sportsbook you chose to connect.
Google AdMob (free tier only). On the free tier, the AdMob SDK uses your mobile advertising identifier (IDFA or AAID) and similar local-storage entries to request ads, cap how often you see the same ad, and detect ad fraud. Pro subscribers do not see ads, and AdMob is not initialized for Pro accounts. On iOS we ask for your permission via the App Tracking Transparency prompt before allowing AdMob to use the IDFA for personalized ads; you can decline that prompt or change your choice in iOS Settings → Privacy & Security → Tracking, in which case AdMob serves non-personalized ads instead. On Android, you can reset your AAID or opt out of personalized ads in Settings → Privacy → Ads.
3.2 On the BetAtlas legal and marketing website
The legal pages at 4bettorinsight.com are static HTML hosted on Firebase Hosting. We use a minimal set of cookies there:
A strictly necessary session cookie set by Firebase Hosting's edge cache for load-balancing and security.
No analytics, advertising, or social-media cookies are set by default. We do not embed Google Analytics, Meta Pixel, or any other tracking pixel on these pages.
If we add analytics or advertising cookies to the marketing site in the future, we will update this Cookie Policy first and — where the law requires it — present a consent banner that lets you accept or reject each category before the cookies are set.
3.3 Third-party services accessed via the app
When you use a feature that involves a third party (for example, "Sign in with Google" or "Sign in with Apple," or a sportsbook log-in), the third party may set its own cookies in its own login page. Those cookies are governed by the third party's policy, not ours. Links to those policies are listed in the appendix to the Privacy Policy.
4. Cookies we use
The following table summarizes the categories of cookies and similar technologies in use today. Exact names and lifetimes are listed where they are stable; vendor-managed entries may rotate over time.
4.1 Strictly necessary
| Where | Purpose | Lifetime |
|---|---|---|
| Mobile app — encrypted local storage | Persist your access and refresh JWTs so you stay signed in | Until you sign out or rotate credentials |
| Mobile app — encrypted local storage | Persist UI preferences (theme, time-zone, last-viewed sportsbook) | Until you clear app data or uninstall |
| Sportsbook in-app browser | Sportsbook session cookies needed to sync your bet history | Set and rotated by the sportsbook; we retain encrypted copies until you disconnect the sportsbook |
| Marketing site | Firebase Hosting edge-cache session cookie | Short-lived session |
Strictly necessary cookies are not optional — without them, core features such as staying signed in or syncing your sportsbook will not work.
4.2 Functional
| Where | Purpose | Lifetime |
|---|---|---|
| Mobile app — secure keystore | Optional biometric (Face ID / Touch ID / fingerprint) unlock token | Until you disable biometrics or sign out |
| Mobile app — encrypted local storage | AI Analytics chat history (last ~20 turns) stored only on your device | Until you clear app data or uninstall |
4.3 Advertising (free tier only)
| Where | Purpose | Lifetime |
|---|---|---|
| Mobile device — IDFA (iOS) / AAID (Android) | Ad selection, frequency capping, attribution, and fraud detection used by Google AdMob | Persistent until you reset the identifier in OS settings |
| AdMob SDK — local storage | Ad request state, rate-limiting, and fraud signals | Vendor-managed; cleared when you clear app data |
We do not deploy any advertising cookies on the legal or marketing website.
4.4 Analytics
We do not currently set first-party analytics cookies. Our backend captures basic server-side request logs (HTTP method, path, timestamp, status) for up to 30 days for operational diagnostics; those logs are described in the Privacy Policy, Section 3.2, and do not depend on a cookie.
5. Your choices
You can control the cookies and similar technologies we use in the following ways:
iOS App Tracking Transparency. Decline the prompt the first time you launch BetAtlas on a new device, or change your choice later in Settings → Privacy & Security → Tracking. Declining means AdMob serves non-personalized ads using a randomized identifier.
Android advertising controls. In Settings → Privacy → Ads, you can reset your AAID or opt out of personalized ads entirely.
Remove ads. Upgrade to BetAtlas Pro to turn off advertising cookies and identifiers in the mobile app. Pro accounts do not initialize the AdMob SDK.
Disconnect a sportsbook. Inside Account Settings, disconnect any sportsbook to delete the encrypted session cookies we hold for it.
Clear app data. Use your operating system's app-management tools to clear BetAtlas's local storage. You will need to sign in again afterwards.
Browser controls. On the legal and marketing website, you can block or delete cookies through your browser's settings; doing so will not affect the mobile application.
We honor recognized Global Privacy Control ("GPC") signals on the marketing site as a request to opt out of any future "sale" or "sharing" of personal information as defined by the CCPA / CPRA. We do not sell or share personal information today.
6. International users
If you are in the European Economic Area, the United Kingdom, or Switzerland, you have additional rights under GDPR / UK GDPR over how we process information associated with cookies that are not strictly necessary, as described in the Privacy Policy, Section 8.3. Where law requires consent before non-essential cookies are set, we will obtain that consent (for example, through the App Tracking Transparency prompt on iOS) before the cookie is set.
7. Changes to this policy
We may update this Cookie Policy from time to time. The "Effective date" at the top of this page will always reflect the latest version. Material changes will be communicated via email or in-app notification before they take effect.
8. Contact
For questions about this Cookie Policy or how we use cookies:
4 BETTOR INSIGHT LLC 10716 Wynspire Rd Highlands Ranch, CO 80130