Privacy Policy

This policy explains how Atlas Trail Maps ("Atlas," "we," "us," or "our") handles information when you use the Atlas website, mobile app, account services, and public share links. Practices depend on the platform, permissions, and features you use.

For privacy questions or requests, email privacy@digivision.dev. The Terms of Service explain the conditions for using Atlas.

• Account information: name, email address, account identifier, and authentication records. If you sign in with a third-party provider, we receive the profile information it supplies, which may include a profile image. Email/password accounts store a password hash rather than a readable password.
• Map and field content: places, coordinates, routes, recorded locations, areas, folders, names, notes, descriptions, saved map documents, offline-pack information, and preferences that you save or sync.
• Location information: precise or approximate coordinates, timestamps, and available location details such as altitude, accuracy, speed, and heading. Recorded points may also include battery level.
• Service and security information: IP addresses, browser or device information, session records, request logs, errors, performance timings, and identifiers used for authentication, rate limiting, or app updates.
• Communications: information you send when you contact us, including your email address and the content of your request.

Information synced to your account is associated with your account identifier. Data stored only on your device is handled differently, as explained in the mobile section below.

We use information to authenticate accounts, provide maps and search, save and synchronize your content and preferences, record journeys you choose to record, serve shared content, deliver app updates, respond to requests, and maintain the security and reliability of Atlas. Website analytics help us understand use of the website and improve its features.

We do not sell your personal information or use your recorded journeys for cross-app targeted advertising. A private account does not mean every operation stays on your device: account sync, online map services, and website analytics involve network requests.

Location and background recording

The mobile app requests location access to show your position and support field mapping. When you start trip recording and grant background permission, Atlas can record location while the app is in the background. You can stop recording in Atlas and change precise, approximate, or background location permissions in your device settings. Revoking permission stops future access; it does not delete previously recorded or synced points.

Local storage and account sync

Atlas stores field data, preferences, and downloaded maps locally so supported features can work offline. When signed in and connected, Atlas sends queued recorded locations, saved map objects, and account preferences to our server for synchronization. Signing out does not automatically erase local field data, and offline changes may upload when you sign in and reconnect. These requests use transport encryption; account sync is not a promise of end-to-end encryption.

Camera and photos

Camera and photo-library access let you attach field photos to saved places. Field photo attachments in the current mobile app are stored locally; their image files are not uploaded by the field-data sync feature. Related place coordinates and notes can still sync. A profile image supplied by an account sign-in provider is separate from these local field photos. Device backups and exports you choose may contain local photos or other field data.

Updates and diagnostics

Atlas uses Expo's EAS Update service to check for and download compatible app updates. Update requests can include platform and runtime information, a randomized installation token, update identifiers, and fatal-error information used to diagnose failed launches. Expo processes this information to provide the update service. See Expo's privacy policy.

Online requests and sharing

Online maps, searches, routing, and downloads contact map-service providers. Exporting or sharing content sends it to the destination you choose. A share link creates a server-side snapshot, even when its source content was created locally. The Google Analytics and PostHog integrations described below are website integrations; the current mobile app does not include those analytics SDKs.

The website uses cookies and browser storage for sign-in sessions, preferences, and analytics. It integrates Google Analytics and PostHog to measure page views and website interactions. Depending on provider settings, analytics may include visited URLs and query parameters, interactions, IP address, browser and device information, and cookie or browser identifiers.

On the production website, PostHog associates signed-in activity with your account ID, name, and email address. Website analytics therefore should not be assumed to be anonymous. Avoid putting private information in URL query parameters.

You can restrict cookies and site storage through your browser and use browser tools to block analytics requests. Blocking necessary storage may affect sign-in or saved preferences. These browser choices do not remove information already received. Contact us about access or deletion requests. See Google's privacy policy and PostHog's privacy policy.

Atlas uses external services for hosting, data storage, authentication, rate limiting, app updates, website analytics, and map functionality. Providers receive the information needed for their service and handle it under their applicable terms and privacy practices.

Map, terrain, imagery, trail, weather, and other data requests can reveal your IP address and the geographic area being viewed or downloaded. Place searches send the search text and may send coordinates used to prioritize nearby results to Esri's ArcGIS geocoding service. Configured online routing services can receive route coordinates. These requests are separate from your account's saved location history.

Map sources vary by selected layer and configuration. Review the attribution shown for a source and Esri's privacy information for ArcGIS services. Third-party sign-in providers also handle the authentication interaction under their own privacy policies.

Saved account content is not made public simply by saving it. When you create or distribute a public share link, anyone who has the link can access the information included in its snapshot, which may contain precise coordinates, descriptions, or route details. Recipients may copy or redistribute it. A link is not an access restriction based on the recipient's identity.

We also disclose information to service providers to operate Atlas, when you direct us to do so, when necessary to comply with law or protect rights and safety, or as part of a business transfer subject to applicable privacy obligations. Contact us if you need help disabling a share link. Disabling access cannot retrieve copies others have already saved.

We retain account and synced content to provide your account and saved workspace until it is deleted or no longer needed for those purposes. Security records, diagnostics, support communications, and provider logs may have separate retention periods based on their purpose and provider settings. Deleting an item from the visible workspace may mark it as deleted while synchronization records or backups still contain a copy.

To request deletion of your account and associated server-side information, email privacy@digivision.dev from your account email address. We may verify ownership before acting. Requests cover associated content and shared snapshots, subject to information we must retain for legal, security, or dispute-resolution reasons. Backup copies may remain until replaced or removed through the applicable backup lifecycle.

Signing out, uninstalling the app, and revoking permissions do not themselves delete your server-side account. Account deletion also does not remotely erase files stored on your devices, device backups, or copies you exported or shared. Manage local copies separately and contact us if you need help.

You can stop trip recording, change device permissions, choose whether to use online features or share content, and manage browser storage. Some features require an account, network access, or the relevant permission.

Depending on where you live, you may have rights to access, correct, obtain a copy of, delete, restrict, or object to processing of your personal information, withdraw consent where processing relies on it, or complain to a privacy regulator. Send requests to privacy@digivision.dev. We assess requests under applicable law and may need to verify your identity. Withdrawal does not affect processing already lawfully performed.

Atlas uses measures such as authenticated account access, transport encryption, and rate limiting to protect information. No system, transmission, or storage method is completely secure. Protect your credentials and device, and share sensitive locations carefully.

Atlas and its service providers may process information in countries other than your own, where privacy laws can differ. Where required, applicable transfer safeguards and privacy obligations govern that processing.

Atlas is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided information to Atlas, contact privacy@digivision.dev so we can investigate and address it. Additional age or parental-consent requirements may apply where you live.

We may update this policy as Atlas changes. We will update the date on this page and provide additional notice or request consent when required by applicable law.

For questions about this policy or your information, contact privacy@digivision.dev.