Privacy Policy

Effective August 10, 2026

AtlasTrack provides tools for organizing travel information in shared, map-based workspaces. This policy explains how AtlasTrack collects, uses, and protects information.

Information we collect

• Account information supplied by an identity provider, such as name, email address, profile image, provider identifier, and whether the provider reports the address as verified. If you choose to link sign-ins, AtlasTrack records which verified provider identities belong to the same person and retains short-lived, hashed verification-challenge records.
• Travel and workspace information you submit or import, including itineraries, reservation prices and currencies when explicitly stated, places, travelers, notes, and preferences.
• For Business organizations, Team names, assigned traveler subjects, assigned member viewers or managers, and the organization’s selected travel-visibility policy.
• When you explicitly connect Gmail, AtlasTrack receives your mailbox address, OAuth authorization, Gmail synchronization identifiers, and read-only access to message identifiers, headers, labels, bodies, and supported PDF itinerary attachments needed to locate and process travel confirmations. AtlasTrack extracts itinerary details, explicitly stated reservation prices, and text from supported attachments; it does not access Gmail for unrelated user-facing features.
• When you connect another supported mailbox, AtlasTrack receives the corresponding read-only mailbox and reservation information needed to provide the same itinerary-import feature.
• Technical and security information, such as request logs, device or browser details, error reports, authentication events, and privacy-respecting first-party marketing events.
• Contact details and messages you voluntarily submit through the AtlasTrack contact form.

How we use information

We use information to provide and secure AtlasTrack, synchronize travel workspaces, respond to requested support or product conversations, troubleshoot problems, and improve reliability. Information received from configured identity providers, including GitHub and Google, is used to authenticate you and establish your AtlasTrack account. While your browser session remains active, AtlasTrack may also display your account email and identity-provider profile image in the public AtlasTrack website header. That presentation uses a short-lived, non-authorizing session marker and sends no AtlasTrack credential to the public website. Connected-mailbox data is used only to locate supported travel confirmations, extract itinerary details, keep those itineraries synchronized, prevent duplicate imports, retry recent imports that could not be completed, and provide those visible AtlasTrack features. AtlasTrack does not send, edit, or delete Gmail messages; use raw, derived, aggregated, or anonymized Google user data for advertising, lending, or eligibility decisions; or use that data to develop, train, or improve generalized AI or machine-learning models. AtlasTrack does not create or use aggregated or anonymized Google user-data datasets.

Sharing

We do not sell personal information or Google user data. Render and Supabase process or store Google-derived data as infrastructure providers only as needed to host and operate AtlasTrack. For each connected inbox, you choose whether normalized reservation records are published to your Personal workspace, an organization workspace, or both. In an organization-wide Business view, active members may see organization travel. When an owner or administrator explicitly enables team-restricted visibility, regular members see their own travel and travelers assigned to Teams where they are viewers or managers; owners and administrators retain organization-wide access. Creating a Team alone does not change visibility. These rules do not grant live-location access, which remains separately authorized. Authorized users do not receive the connected mailbox's OAuth credentials or a general view of its messages. Linking a personal and work sign-in does not merge their workspaces or by itself publish personal reservations to an organization. AtlasTrack does not transfer raw, derived, aggregated, or anonymized Google user data to advertisers, data brokers, lenders, or third-party AI or machine-learning model providers. We otherwise disclose information only when you direct us to share it, when necessary to operate a user-facing feature with an identified service provider, or when required by law.

Service providers

Depending on enabled features, AtlasTrack uses providers including Render for application hosting, Supabase for database and authentication services, Stripe for paid-plan Checkout, billing, tax calculation, and payment processing, Mapbox or OpenStreetMap for map data, Mailgun for optional itinerary email processing, and configured identity and travel providers. Stripe receives the billing, payment-method, contact, and tax-location information needed to process a subscription; AtlasTrack does not store full card details.

Retention and deletion

The public-site account marker and its display snapshot expire within 24 hours, are rotated when republished, and are cleared on logout when the browser can reach AtlasTrack. After AtlasTrack successfully parses a Gmail travel confirmation or cancellation, it removes the stored message sender, subject, body, and extracted attachment text from the inbound-processing record. It retains only the limited synchronization and duplicate-prevention identifiers, processing status, mailbox connection information, and derived itinerary records needed to provide the feature. If a Gmail message cannot be completed and remains pending or failed, AtlasTrack retains its message content for retry for no more than 30 days and then removes the sender, subject, body, and extracted attachment text. Original Gmail PDF files are processed in memory and are not retained as mailbox attachments. Disconnecting a mailbox immediately revokes or removes AtlasTrack's stored authorization tokens, clears its synchronization cursor, and stops future mailbox access; previously derived itinerary records remain available until you delete them or permanently delete the account. Account owners may permanently delete an account from the AtlasTrack account menu after recent authentication and exact-name confirmation. Permanent deletion ends active billing and removes the account's travel data, workspaces, integrations, private attachment objects, billing records, and authentication identities owned by that account from active systems. AtlasTrack's production operating requirement is for protected backup copies to be isolated from ordinary access and age out within 30 days unless longer retention is legally required. Provider retention and deletion-aware restore controls must be verified for each production deployment, and deleted data must not be intentionally restored to active service. Limited non-Google records may be retained longer where required by law or reasonably necessary for fraud prevention, accounting, or dispute resolution. Canceling a paid subscription is different: it returns the account to Free after the paid period and retains account data. Contact requests are retained only as needed to respond and maintain appropriate business records. You may also request access, correction, export, or deletion through the verified contact channel below.

Google API data

AtlasTrack's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Human access to connected-mailbox content is prohibited except with the user's explicit consent for support, when necessary for security, or when required by law.

Security

AtlasTrack uses organization-scoped authorization, optional Team-restricted traveler access, workspace data boundaries, encrypted network connections, managed infrastructure, and security monitoring. No method of storage or transmission is completely secure. See the AtlasTrack security overview for current safeguards and deployment responsibilities.

Your choices

To stop mailbox access without deleting imported trips, open AtlasTrack Settings, find Connected inboxes, and choose Disconnect beside the mailbox. You may also revoke AtlasTrack from your Google Account's third-party connections page. To remove imported itinerary records, delete the applicable trips in AtlasTrack or use Account > Delete account to remove all active account data and integrations. You may also stop other travel sources, use browser privacy signals that disable optional first-party marketing analytics, or request access, correction, export, or deletion through the contact channel below.

Children

AtlasTrack is not directed to children under 13, and we do not knowingly collect their personal information.

Changes

We may update this policy as AtlasTrack evolves. The effective date above identifies the latest revision.

Contact

Questions and privacy requests may be submitted through the verified AtlasTrack contact form.