Privacy Policy

Who we are

Atlas is operated by Troy Smith ("we," "us"). Once Snowbird Labs LLC is registered, this policy will be updated to reflect the entity change. Contact: troy@snowbird-labs.com.

What we collect

Atlas only collects data you explicitly connect. We never buy data, never run third-party trackers, and never collect anything you haven't actively connected.

• Account info from your sign-in provider (email, name, Apple- or Google-issued user ID, profile image URL). Used to sign you in and label your data inside the app.
• Profile fields you choose to set: sex and birthdate. Used solely to look up the right age + sex cohort for percentile-based scoring on health metrics. Never shared.
• Health & fitness data from Apple HealthKit — the metrics and workout types you authorize on the system permission sheet (steps, sleep, heart rate, HRV, weight, workouts, etc.). Read-only; we never write back to HealthKit.
• Data from optional integrations if you connect them — bank and investment account data via Plaid (see below), Monarch Money (financial accounts and transactions), GHIN (golf rounds and handicap), TrackMan / Rapsodo (golf swing metrics), BTWB (CrossFit sessions), PADI (scuba dive logs), GitHub (your daily contribution counts), Hevy (weight-training sets), Hardcover (books on your Currently Reading and Read shelves), and Google Calendar (see below).
• Google Calendar— if you connect it, Atlas reads your primary calendar with Google's read-only calendar.readonlyscope and derives records from it: social interactions (from timed events with other attendees), doctor's appointments (from events a keyword classifier recognizes as medical), and travel-trip suggestions. Event titles and locations are stored on the records Atlas creates — which means calendar text can become part of a health record. Atlas never writes to your calendar, and disconnecting deletes the stored Google refresh token. Records already created stay until you delete them.
• Photos you scan on your device— the iOS app can scan your photo library's dates and locations to suggest trips and restaurant visits. That scan runs entirely on your device — your photos are never uploaded. Only the trips or visits you explicitly confirm are sent to Atlas. Photos you deliberately attach (meal photos, progress photos, trip covers) are uploaded and stored privately.
• Financial data via Plaid — if you link a bank, credit, or investment account, Atlas uses Plaid to retrieve account balances, transactions, and investment holdings from your financial institution. You grant or deny access institution-by-institution in Plaid's own consent flow, and Atlas never sees your bank credentials — only read-only data. By linking an account you also agree to Plaid's End User Privacy Policy. Access tokens are stored encrypted (AES-256-GCM) and are deleted when you disconnect the integration or delete your account.
• Server logs — standard request logs (IP, user-agent, timestamp, status code) retained for up to 30 days for security and abuse-prevention purposes.

Apple HealthKit data — special handling

Apple requires explicit disclosure of how HealthKit data is used. For Atlas:

• HealthKit data is read on your device and uploaded to Atlas's backend (Neon Postgres on Vercel) so it can populate your dashboard across devices and the web.
• We never use HealthKit data to advertise or market to you, share it with advertisers or data brokers, or use it to inform an ad platform.
• We never sell HealthKit data.
• We never use HealthKit data to derive third-party rights (e.g. licensing it for AI training).
• HealthKit data is stored alongside the rest of your account in encrypted-at-rest Postgres. Deleting your account removes every row immediately.

Where it lives

All data is stored in a Neon Postgres database with encryption at rest, hosted on the Vercel platform (US East). Third-party integration credentials (Monarch passwords, GHIN tokens, etc.) are additionally wrapped in AES-256 application-level encryption with a key that is never sent to the browser.

What we do with it

Your data is used to populate yourdashboard. That's the only purpose. We do not:

• Sell your data, ever.
• Share your data with third parties for marketing or analytics.
• Use your data to train AI models.
• Show you ads.

Aggregated, fully de-identified statistics (e.g. "users who connected GHIN played 12 rounds on average last month") may be used internally for product analytics, but never in a form that identifies an individual user.

Sub-processors

Atlas relies on a small set of infrastructure vendors. Each is a data processor only — they hold data on our behalf and cannot use it for their own purposes.

• Vercel — application hosting, serverless functions, edge logging.
• Neon — managed Postgres database.
• Anthropic (reached through the Vercel AI Gateway) — AI inference for every Atlas feature that uses a model. What gets sent depends on the feature you use:
  • Coach — your chat messages, plus whichever summaries the Coach reads to answer you (activity, recovery, body, finance, golf, travel, goals, timeline). Money figures are only read when you ask a money question.
  • Meal parsing — the meal text or food photo you submit. Photos are sent to the model and discarded; they are never stored.
  • "Log to Atlas" screenshots — the screenshot you share, whatever it contains, so it can be classified and turned into draft records you confirm.
  • Daily check-in answers, profile bio generation, and the optional Action Plan generator — the specific text or summary stats each of those features builds.
  Nothing is sent to a model unless you use one of these features. Requests are made with zero data retention and are not used for model training.
• Sentry — error monitoring for the web app, the backend, and the iOS app. Receives crash and error reports: stack traces, the request or screen involved, and your account identifier so a report can be tied to a session. Not a copy of your health or financial records.
• Resend— transactional email delivery. Receives your email address and the contents of the messages Atlas sends you, which for the weekly progress email includes that week's summary figures.
• Apple Push Notification service (APNs)— delivery of iOS push notifications. Receives your device token and the notification text, which can include a metric in the body (for example "7,800 of 10,000 steps"). Turn any channel off in Settings → Notifications and nothing for it is sent.
• Notion and GitHub — issue tracking for feedback you choose to send (the in-app feedback form, the shake gesture, or the contact form). Receives what you wrote plus your account identifier so we can follow up. Nothing is filed unless you submit feedback.

If you connect an integration (Plaid, Google Calendar, GitHub, Hardcover, Hevy, GHIN, TrackMan, Rapsodo, PADI, Beyond the Whiteboard), Atlas exchanges data with that provider on your instruction, under their privacy policy. Disconnecting one stops the exchange. Scanning a barcode or searching packaged foods sends that barcode or search term — nothing else — to Open Food Facts.

Connecting Atlas to Claude

Atlas ships an optional connector that lets Claude read and log your Atlas data from a Claude chat. It is off until you add it and sign in to authorize it, and it holds an access token you can revoke at any time from Settings → Security.

While connected, Claude can request the same summaries the Coach reads (activity, recovery, body, nutrition, finance, golf) and can log records on your behalf — food, water, caffeine, alcohol, weight, mindful minutes, mood, workouts, sleep, golf rounds, and goal changes. Claude's connector interface asks you to confirm each write. Whatever the connector returns is handled under Anthropic's privacy policy for your Claude account, not this one.

Cookies + analytics

Atlas sets a session cookie via NextAuth so signing in persists across page loads. Vercel Analytics provides aggregate traffic counts; it is cookieless and does not track individual users. No third-party advertising or social-media trackers run on Atlas.

Your rights

You can, at any time:

• Disconnect any integration from Settings → Integrations. Removing an integration immediately deletes its stored credentials.
• Export everything — Settings → Account → Download account data. The download is a JSON file containing every row keyed to your user ID.
• Delete your account — Settings → Account → Danger zone → Delete account. Deletion is immediate; every row keyed to your user ID is removed via cascade. Backups are retained up to 30 days for disaster-recovery purposes and are never used for any other purpose.

If you are an EU/UK resident, you also have the rights granted by GDPR (access, rectification, erasure, restriction, portability, objection). Email us to exercise any of these rights, or use the export and delete affordances above.

Children

Atlas is not directed to children under 13. We do not knowingly collect data from anyone under 13. If you believe a child has signed up, contact us and we will delete the account.

Security

We use industry-standard practices: TLS 1.2+ in transit, encryption at rest at the database layer, AES-256 application-layer encryption for integration credentials, OAuth bearer tokens that expire and can be revoked, and no third-party access to production data. No system is perfectly secure; if we ever experience a breach affecting your data, we will notify you within 72 hours of confirming the breach.

International users

Atlas is hosted in the United States. By using the service from outside the US, you consent to your data being processed in the US. Where required by law (GDPR), we use Standard Contractual Clauses with our sub-processors to cover transfers.

Changes to this policy

We'll update this page when material things change and bump the "Last updated" date at the top. Substantive changes will be communicated via email to active users at least 14 days before taking effect.