Legal

Privacy Policy for PathXplorer

Last updated: October 26, 2026

Introduction

PathXplorer ("we," "our," or "app") is built privacy-first: no account, no ads, no selling of data — ever. Your tracks, photos and statistics are recorded and stored on your device, and by default they stay there.

Some features do need to send data off your device to work — weather needs your coordinates, group tracking needs your position, an SOS alert needs to reach your contacts. This policy describes exactly what leaves your device, when, to whom, and how you control it.

The short version

Device Permissions

PathXplorer requests certain device permissions to provide its features. You control each of them and can revoke them at any time through your device settings; the app keeps working with reduced features if a permission is denied.

Data Stored on Your Device

PathXplorer stores the following on your device:

Backups you control

Track backup (Settings › More) is optional. When you turn it on, copies of your tracks and photos are saved to a folder you pick on the phone or an SD card, and/or to a folder in your own Google Drive, which requires you to sign in with your Google account. We have no access to that folder.

Separately, Android’s automatic Google backup may store your tracks, addresses, diagnostic log and app settings (including the names, phone numbers and email addresses of your SOS contacts) in your Google account, under Google’s own privacy terms. You can switch it off in your phone’s Google settings. The SOS email password, if you set one, and the anonymous usage counters are never included.

You can delete all of this at any time by clearing the app's data in your device settings or by uninstalling the app. Copies kept in your Google Drive or Google account are yours to delete there.

Features That Send Data Off Your Device

Each feature below sends only the minimum data needed, only while you use it. All connections are encrypted in transit (HTTPS/TLS).

Maps — OpenStreetMap

Map tiles are downloaded from OpenStreetMap servers as you pan and zoom. Standard network requests occur, but no personally identifiable information is sent. You can cache maps for offline use. See the OpenStreetMap Foundation Privacy Policy.

Weather — WeatherAPI.com

Weather is part of the Fun edition. When weather features are available, your current coordinates (latitude and longitude) are sent through our relay server to WeatherAPI.com to retrieve local conditions — at most every 15 minutes while the app is active, less often later in the day. The relay receives your coordinates together with the random device identifier described below, forwards the request and does not keep your requests as a track; no name or account accompanies it, and the weather data received is stored only on your device. Weather is paused in Zero Data mode and refreshes less often in Min Data mode. See WeatherAPI.com's Privacy Policy.

Addresses, Destination Search & Routing — Nominatim and OpenRouteService

When you use the Nearest Address tile, search for a destination, or plan a route, your coordinates (and the search text you type) are sent through our relay server to the OpenStreetMap Nominatim geocoding service and/or OpenRouteService to resolve addresses and compute routes. The relay also receives the random device identifier described below and your edition (Free or Fun), which it uses to apply the daily route limits. These lookups happen only when you use those features, and their results are cached on your device so repeat lookups can be answered offline.

Speed Limits, Nearby Places and Events — our relay server

To show the speed limit of the road you are on, and the Attractions, Events and Fuel chips of the destination screen, the app asks our relay server for the data of your area, which means your coordinates reach it. The relay fetches the answer from open-data and event services (OpenStreetMap, OpenAgenda, Ticketmaster), keeps part of it in a cache so repeat requests cost nothing, does not keep your requests as a track, and passes them to no one except the service that answers them.

Group invitations — our server

When you share a group invitation, a small picture card (your avatar, your @nickname and the #group name over a city-scale map) is sent to our server so that the link can show a preview.

Live Group Tracking — our server

Group tracking is OFF by default. When you choose to join a group, the following is sent to our server over an encrypted connection: the group name, the nickname you picked, a random device identifier (generated by the app — not tied to your identity), and your live position while sharing is on. This is relayed to the other members of your group so you can see each other on the map.

Group positions are ephemeral. They exist on the server only while you are connected and are deleted when you disconnect or stop sharing. There is no history, no account, and nothing to delete afterwards — leaving the group is the deletion.

Group activity log, 7 days. For abuse prevention and service statistics, the relay records when a device joins or leaves a group (group name, nickname, an app-generated device identifier and country — never a position). After 7 days, the nickname, device identifier and country are erased; only an anonymous count per day remains.

SOS Emergency Alerts — our server

The SOS feature sends an alert only when you deliberately trigger it (press-and-hold plus confirmation — it cannot fire by accident). An alert always carries your name, your phone number, the time, your coordinates, your speed and battery level, and a random device identifier. You choose in advance whether it also includes:

To deliver the alert, the selected content and the email addresses of your chosen emergency contacts (up to three, entered by you) are transmitted to our server, which sends the alert email and then does not use this data for any other purpose. Your contacts' addresses are stored on your device, not on our server. An SOS is sent over any available network, even in Zero Data mode; if Wi-Fi is blocked, the alert automatically retries over your cellular connection (on Android; on iPhone, iOS picks the available network). Once delivered, the alert lives in your contacts' inboxes like any email you might send them.

Server logs

Like any web server, ours keeps ordinary technical logs — time, IP address and the request itself, which can include coordinates — for security and troubleshooting. We do not use them to rebuild your movements.

Google Play services

Newsletter

If you choose to subscribe to the newsletter (in the app or on funapps.biz), your email address and language are stored on our server so that we can send you a confirmation message and the letters themselves. Every message carries an unsubscribe link; unsubscribing stops the mailings. Subscribing is entirely optional and does not create an account.

Anonymous Usage Statistics

To understand which features are used and where new users get stuck, the app sends our server a small summary of the day’s counts only, sent when you open or leave the app (at most every couple of minutes) and replaced each time on our server: how many times the app was opened, how many trips were recorded and for how many minutes, how many destination searches, routes, photos, videos, reports and shares were made, which permissions were requested, granted or refused, and a few settings such as the data mode and the GPS interval. The summary also carries the app version, the Android or iOS version, the device memory size, the language, the country of your mobile network, the day the app was installed, how the app was found (a broad category only, such as “Google Play search” or “advertising campaign”, taken from the Google Play Install Referrer), whether the device is an emulator or a test robot, whether Google services are present, whether battery optimization is switched off for the app, how many dashboard tiles are shown, how many minutes passed between installation and your first use of each feature, and the same random device identifier used for group tracking (generated by the app and not tied to your identity).

This summary never contains a position, a track, an address you searched, a photo or any content. It amounts to a few kilobytes a day at most, is never sent over mobile data in Zero Data mode (it is sent only on an unmetered connection such as Wi-Fi, like the rest of the app in that mode), and is retained in raw form for thirteen months before being reduced to daily totals. You can turn it off at any time with the Anonymous usage statistics switch in Settings › Data; nothing is sent or kept while the switch is off.

Crash Reporting

PathXplorer uses Firebase Crashlytics (a Google service) so we can find and fix crashes. If the app crashes, a report is sent containing technical details (device model, Android or iOS version, app version, what the code was doing) and device identifiers used to group reports. These reports contain no tracks, no photos and no location history. Crash data is handled by Google under the Firebase privacy documentation and retained per its policy.

Separately, the app keeps a diagnostic log on your device. It holds technical events, your approximate last known position (rounded to about 1 km), your device model and your Android or iOS version. It is sent to us only if you explicitly choose to send it — from the Settings menu, or by answering Yes to the question the app may ask after a crash (answering No sends nothing) — typically when we’re helping you troubleshoot.

PathXplorer on iPhone and iPad

The iOS version works the same way and follows this whole policy, with Apple’s services in place of Google’s:

What We Never Do

Your Rights and Choices

Because we hold no account or database about you, there is nothing for you to request a copy of and no account to delete — you already have direct control over all of it.

Children's Privacy

PathXplorer requires no account and collects no profile information, and is suitable for users of all ages. Parents should be aware that the group tracking and SOS features, when deliberately used, share the device's location as described above.

Changes to This Policy

When the app gains features that change how data is handled, this policy will be updated and the "Last updated" date at the top revised. Significant changes will also be highlighted within the app.

Contact Information

If you have questions about this Privacy Policy, please contact:

This privacy policy reflects our commitment to transparency and to giving you control over your data while using PathXplorer.