Who is responsible for this app?
Developer identity: Vytaras Sukys, Lithuania.
Privacy contact: [email protected]
Information Atlasson handles on your devices
- Location and walk history. When you explicitly start a walk on iPhone, Atlasson records accepted location fixes, including latitude and longitude, timestamps, accuracy, and available speed and heading. Recording can continue while the app is in the background during an active walk; iPhone recording requires Always location access. Pausing or stopping recording controls whether a walk is active. The fixes are first written to a protected native SQLite inbox and then committed to Atlasson's local SQLite data store.
- Exploration records. Atlasson stores walk sessions and points, derived trail and distance statistics, revealed map cells, and physical country and region visits locally so it can show your exploration history.
- Apple Watch walks. If you start a walk in the optional Watch app, it stores walk points and session details on the Watch and transfers completed walk batches to the paired iPhone using Apple's WatchConnectivity. The Watch keeps its completed copy until the iPhone acknowledges receipt. If the devices are not connected, transfer and deletion instructions can be delayed. The Watch uses an outdoor workout session for an explicitly started walk and requests no HealthKit read permissions.
- Apple Health distance. On iPhone, Atlasson requests read-only access to Apple Health walking and running distance for Journey progress. It stores daily distance totals and Journey allocation/progress data in local SQLite; it does not request permission to write those distance records. Erasing Atlasson data does not delete source records from Apple Health. The app source reviewed does not send HealthKit samples or derived Journey totals to a developer server.
- Preferences and diagnostics. Preferences and some lifecycle/permission markers are stored locally. Atlasson also keeps a bounded set of local reliability diagnostics. The diagnostics are structured events and do not include coordinates, historical routes, or raw HealthKit samples.
The iPhone and Apple Watch app uses local SQLite and local preference storage. The app source review found no Atlasson account service, advertising integration, in-app analytics integration, crash-reporting service, social feature, or developer-operated cloud sync endpoint. This statement is about the app itself; the Atlasson website uses consent-controlled Google Analytics as described below. This does not mean that no information leaves your device: online map requests are described below.
Map requests and third-party processing
The map uses MapLibre Native and requests its Liberty style and map resources from OpenFreeMap, including style, vector and raster tiles, sprites, and glyphs. Map requests identify the map resources being viewed; tile selection includes zoom and tile coordinates. When the map follows your device location, the requested map area may correspond to where you are. These requests are sent to OpenFreeMap's service and may pass through its delivery infrastructure, including Cloudflare according to OpenFreeMap's published policy. This is a disclosure of map-view requests, not an upload of Atlasson's saved GPS trail or HealthKit history.
OpenFreeMap's published privacy policy says it collects anonymized server logs with browser type, referring/exit pages, date/time stamps, and operating system, and retains those logs indefinitely. It says IP addresses are not included in regular logs, but that IP logging may be enabled during a security incident or misuse investigation for up to 30 days. It also says Cloudflare may be used and may collect information under Cloudflare's own privacy policy. The OpenFreeMap policy was last updated February 26, 2025, and was reviewed for this policy on October 3, 2026.
That published policy does not specify whether map tile paths or tile coordinates from Atlasson's native app requests appear in the retained logs, nor does it establish the precise request fields or retention practices for Cloudflare delivery. Atlasson has not verified those details with OpenFreeMap or Cloudflare. This policy makes no claim that map requests are unretained, anonymous in all contexts, unlinkable, or limited to real-time processing. Standard network service metadata is also handled by the systems delivering those requests.
Atlasson does not send a recorded route as a route upload. Nevertheless, tile requests can reveal the places and zoom levels being viewed. You can avoid map requests by not loading the online map, but map features need an internet connection to fetch map resources.
Website analytics and cookies
The Atlasson website uses Cookiebot to manage cookie consent and Google Analytics 4 to measure website usage. The Google Analytics measurement ID is G-2RPBH8YTK6. Cookiebot is configured in automatic blocking mode to control non-essential analytics according to your cookie choice.
If you consent, Google Analytics may process information about visits to the website such as pages viewed, approximate location derived from network information, device and browser information, interaction data, and identifiers used by Google Analytics. Google processes this information under its own terms and privacy documentation. You can refuse or withdraw statistics-cookie consent through the Cookiebot consent controls.
Website analytics is separate from the Atlasson iPhone and Apple Watch app. Atlasson does not use this website analytics configuration to upload your saved GPS trails, Apple Health data, Journey progress, or other locally stored app exploration history.
Exporting and importing backups
Settings > Data > Export backup creates a JSON file. It contains raw GPS/session history, including coordinates and timestamps, exploration records, and Health-derived daily Journey distance totals and allocation data. It does not include raw HealthKit samples. The file also contains selected preferences and sync metadata. Treat it as sensitive. Atlasson does not add file-level encryption to the JSON; the temporary export file receives iOS file protection while it is being prepared.
iOS presents a share sheet and you choose the destination, such as Files, AirDrop, or another available app or service. Exporting does not erase the data kept by Atlasson. After you save or share a copy, the destination and any service you choose handle that copy under their own terms; Atlasson cannot control or erase copies saved outside the app.
Import backup lets you choose a JSON file through the iOS Files picker and restores it to an empty Atlasson data store. Imported walk history and Journey totals become local app data. Do not import a backup you do not trust.
Erasing information
Settings > Data > Erase all data asks for confirmation, coordinates stopping and draining an active recording, and then removes user-derived Atlasson records from the iPhone, including session points, exploration history, Journey totals and allocations, and related local state. It also resets the native location inbox and requests an erase of Watch walk data. If an Apple Watch is offline, it may not receive that request until it reconnects, so its local copy can remain until then.
Static bundled country and region reference geography, preferences, and permission markers are retained by the in-app erase. Erasing Atlasson data does not erase Apple Health records, exported backup copies, or copies held by destinations you selected. Location and other app data may also remain in operating-system or user-managed device backups; this policy does not claim a verified retention schedule for those backups or for local MapLibre caches.
Atlasson has no published fixed retention period for local records: user-derived app records remain on the device until you erase them or remove the app's stored data. Separate Watch copies and externally saved backup copies follow the conditions described above.
Changes and requests
This policy is effective October 3, 2026. For privacy questions or requests, contact [email protected].