1 · Information we collect
Only what the service needs.
You can visit public information pages without an account. Using the atlas, paid access, alerts, or newsletter creates the records described below.
Account and billing
Identity without passwords or card storage.
We store your verified email address, optional display name, Supabase user ID, account status, onboarding state, consent choices, and entitlement. Stripe collects payment details; we retain Stripe customer/subscription IDs, plan, status, trial, renewal, and cancellation projections—not card numbers.
Your research
Saves and notes belong to you.
We store saved homes, plain-text notes, tags, read state, saved searches, alert preferences and delivery state, support requests, content reports, and account export/deletion state. Other customers cannot read these rows, and the administrator support view does not expose private notes.
Newsletter
Marketing consent is separate.
If you request the newsletter, we store your normalized email, consent text version and time, confirmation and unsubscribe state, delivery events, and a provider contact ID. Creating an atlas account does not subscribe you.
Technical records
Security and reliability signals.
The service processes session cookies, request and workflow identifiers, approximate device/browser class, timestamps, rate-limit keys, security events, and privacy-minimized error diagnostics. We do not put emails, private notes, raw searches, exact map coordinates, request bodies, or payment details into product analytics.