Atlas privacy · Inspectable data boundary

Your research history is not an advertising product.

Atlas stores the minimum needed to run your research desk, keeps payment-card custody with Stripe and uses no third-party ad trackers on research pages.

Inspect the data record Review security proof
Ad profile
None
Card storage
Stripe
Hardware access
Disabled

Minimum-data contract active

Privacy custody map
Your browser

Theme, consent and essential session state remain tied to operating the Atlas experience, not advertising.

What Atlas keeps

Only the record needed to run, secure and return your research.

The data model is operational: requests, delivery, account security and archive continuity. It is not an advertising identity graph.

01 · Research request

Structured metadata

Template, ticker, output style, tier, source state and timestamps support limits, history and failure diagnosis.

02 · Delivery record

Honest receipt state

Requested, queued, sent, failed or unsubscribed states prove what Atlas did instead of pretending delivery.

03 · Account security

Protected identity

One-way password hashes and enabled passkey or authenticator security records protect access. Plaintext passwords are never stored.

Separation by design

Payment custody and other FreedomCore products stay outside.

Atlas Pro grants Atlas scope only. Research history is not shared across Maverick, SHADOW, Arena or Pumphouse paid surfaces.

Stripe handles payment custody

Stripe operates checkout and stores card details as a PCI DSS Level 1 service provider.

  • Atlas receives signed subscription confirmation
  • Atlas stores entitlement state
  • Atlas never stores the card number

Atlas history stays in Atlas

Other FreedomCore products do not receive Atlas research history merely because they share a wider product family.

  • Atlas access unlocks Atlas only
  • No cross-product research-history access
  • Separate product boundaries remain explicit
Inspect the contract

Open the exact privacy control you want to verify.

These controls preserve the complete meaning of the Atlas privacy record while keeping the page readable on a phone.

01Research requests

Atlas logs enough request metadata to enforce usage caps, keep your research history, debug failures, and prove delivery state. The shape is structured: template, ticker, output style, tier, source state, and timestamps. Your research history is yours; it exists so the desk can show it back to you.

02Email delivery

Email delivery requires a confirmed address. Receipt rows track requested → queued → sent / failed / unsubscribed states, so Atlas never pretends an email was delivered when it was not. One-tap resend uses the same audited rail.

03Account and billing identity

Atlas stores one-way password hashes for password accounts and security records for passkeys or authenticator setup where enabled. It never stores plaintext passwords.

Checkout and card storage are handled by Stripe. Atlas receives cryptographically signed subscription confirmations and stores the entitlement state needed to provide access, never the card number.

04Cookies and analytics
  • Essential cookies and storage support login sessions, CSRF protection, account security, report handoff, consent state, and the fc-theme day/night preference.
  • Traffic analytics are self-hosted on FreedomCore infrastructure at traffic.freedomcore.io. Atlas uses no Google Analytics, ad networks or third-party ad trackers on research pages.
05Hardware permissions

Hardware permissions including camera, microphone, geolocation, USB and sensors are disabled site-wide at the header level. Atlas never asks for them.

06Verification and contact

The security posture protecting this data, including A+ TLS, A+ headers, hash-locked scripts and strict content security, was hardened with Claude Fable 5-assisted review and is independently re-testable: read the security review.

Privacy questions and data requests: support@freedomcore.io.

Research only. No advice, brokerage execution or guaranteed returns.

Read Atlas terms