Last updated: June 23, 2026

Privacy Policy for Atmos

Atmos (“the App”, “we”, “us”, “our”) is developed by Shantnu Kumar (“Developer”). This Privacy Policy explains what data the App and its backend service (collectively, the “Service”) collect, how it is used, who it is shared with, and how you can control or delete it.

By using Atmos, you agree to the practices described in this policy.

Atmos is an independent, open-source project developed by a solo developer, not a company. The full source code — including the trip-detection, Gmail-parsing, and data-handling logic described in this policy — is publicly available at github.com/dipu989/atmos-mobile (app) and github.com/dipu989/atmos-core (backend) for anyone who wants to verify these practices directly.

1. Information We Collect

1.1 Account Information

When you register, we collect your email address and password (or, if you sign in with Google, your Google account ID, name, email, and profile photo), your display name, and a profile photo if you choose to upload one (stored via Firebase Storage).

1.2 Location & Motion Data

To detect trips automatically, the App collects, with your explicit permission, precise GPS location while a trip is being detected or actively tracked, motion/activity signals (walking, cycling, in-vehicle) classified by your device's OS, and trip route waypoints used to calculate distance and transport mode. Location tracking only runs while detecting or recording an active trip — we do not track your location continuously in the background outside of that window.

1.3 Trip & Activity Data

Transport mode, distance, duration, and timestamps for each trip you log; your home and work addresses if set in commute preferences; and address search queries you type when looking up a pickup/drop location.

1.4 Gmail-Derived Trip Data (Optional Feature)

If you choose to connect your Gmail account, the App requests read-only access (gmail.readonly scope) to your inbox, solely to detect ride-hailing and travel receipts (e.g. Uber, Rapido, flight bookings) and log them as trips automatically.

  • We search only for emails from known ride-hailing/travel senders — we do not read your general inbox content.
  • The subject line and a stripped, plain-text version of the matching email's body (HTML tags, scripts, and styles removed) are sent to a third-party AI service (Groq) to extract structured trip details: pickup/drop address, distance, fare, provider, and time.
  • The raw email body and Groq's response are never stored. They are processed in memory and discarded immediately after the structured fields are extracted and saved as a trip.
  • We retain a lightweight log per processed email containing only the Gmail message ID, subject line, Gmail's short snippet (~100 characters), and a parse status — used for de-duplication and troubleshooting, not the email body.
  • You can disconnect Gmail access at any time from Profile settings; this revokes our access token and stops further email scanning.

1.5 Device & Diagnostic Information

Push notification token (Firebase Cloud Messaging) and basic device metadata (OS, app version) for crash diagnostics.

1.6 Local On-Device Storage

The App keeps a local cache of your trips on your device using an embedded SQLite database, so trip detection works offline before syncing to our servers. This local cache is deleted if you uninstall the App.

2. How We Use Your Data

We use the information above to:

  • Detect, classify, and log your trips automatically
  • Calculate your carbon emissions (CO₂e) and show trends, streaks, and insights
  • Resolve addresses to map coordinates and provide place-search suggestions
  • Send push notifications about detected trips and new insights
  • Maintain your account, preferences, and goals
  • Diagnose crashes and improve app reliability

We do not use your data for advertising, and we do not sell your personal data to third parties.

3. Third-Party Services We Use

ServiceWhat we sendWhy
Firebase Cloud Messaging (Google)Push token; trip/insight metadataPush notifications
Firebase Storage (Google)Your profile photo, if uploadedAvatar hosting
Google Sign-In / OAuth UserinfoOAuth access tokenAuthenticate you and fetch profile
Google Maps Geocoding & Places APISearched/extracted addressesAddress → coordinates, autocomplete
Groq (AI inference)Subject + stripped body of ride-receipt emails (Gmail users only)Extract structured trip details

We do not share your personal data with advertisers, data brokers, or any party not listed above.

4. Data Security

  • All data in transit between the App and our servers is encrypted via TLS.
  • Account credentials and authentication tokens are stored using platform-secure storage (Android encrypted preferences / iOS Keychain-backed storage).
  • Gmail OAuth tokens are stored encrypted and used only for the read-only scan described in §1.4.

5. Data Retention & Your Rights

You have the right to:

  • Access your data — export your trip history as CSV from Profile
  • Correct your data — edit or delete individual trips at any time
  • Delete your account — in-app via Profile → Account → Delete Account. Your account enters a 7-day grace period during which you can log back in to cancel the deletion. After 7 days, your profile, preferences, trip history, and Gmail connection are permanently and irreversibly erased.
  • Disconnect Gmail — independently of account deletion, via Profile → Gmail
  • Withdraw location/motion permission — at any time via device settings, which disables automatic trip detection only

6. Children's Privacy

Atmos is not directed at children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child has provided us data, contact us and we will delete it.

7. Changes to This Policy

We may update this policy from time to time. Material changes will be reflected by updating the “Last updated” date above, and significant changes will be communicated in-app.

8. Contact Us

For privacy questions, data requests, or concerns:

Developer: Shantnu Kumar
Email: connect2shantnu@gmail.com