Privacy Policy for GPS Logger

Last updated: June 12, 2026

GPS Logger is a private GPS track recording app published by NorthforceApps. This policy explains what data the app handles, how it is used, and what choices you have.

Contact: northforceapps [at] protonmail [dot] com

Summary

GPS Logger records location tracks when you start a recording, or when you enable auto-start after reboot and your phone restarts. You can also import GPX files that you choose. Track data is stored on your device so you can view your history, see your route on a map, and export GPX or KML files. The app does not sell your personal data or share it with third parties.

Data the App Handles

Location Data

When you start a recording, GPS Logger collects precise location data, including latitude, longitude, timestamp, altitude, speed, bearing, and accuracy. When you import a GPX file, the app reads the track points in that file. This data is used to create your track history, calculate distance and speed, show your route, and export route files.

GPS Logger requests background location access so recording can continue when the app is not visible, the screen is off, or you switch to another app. If you enable auto-start after reboot, background location also lets the app start a new recording after your phone restarts or powers back on. Location recording stops when you stop the track.

Track History

The app stores track names, start and end times, duration, distance, point count, maximum speed, and related track points in the app database on your device.

App Settings

The app stores settings on your device, such as tracking mode, display preferences, auto-start after reboot, live-sharing destination, share code, self-hosted server URL, optional API key, and Pro/lifetime feature settings.

Where Your Location Data Goes

Optional Live Sharing (App Cloud)

If you enable live sharing to the App Cloud, GPS Logger transmits your current position so admitted app users with your share code can follow you on a live map. The transmitted data includes latitude, longitude, timestamp, speed, bearing, accuracy, and an anonymous account identifier.

Your current position is overwritten in place while sharing is active — only the current App Cloud position is stored. An anonymous account identifier remains associated with your share code to prevent another user from taking control of that code after your live position is removed. The app uses anonymous Firebase Authentication to identify the broadcaster and each follower app install, enforce your active follower limit (1–20 app installs), and let you reset the share code to revoke access.

App Cloud currently runs on Google Firebase, which acts as our service provider for this feature. Firebase is used only to relay the live position you choose to share and to enforce share-code ownership and follower limits. We do not sell or share your location data with third parties.

Data is encrypted in transit (HTTPS/TLS). Your current position and transient follower-presence records are removed when you stop broadcasting. If you reset your share code, the old App Cloud share record is deleted and existing followers lose access immediately. As a privacy safeguard, any position left behind by a device that does not disconnect cleanly is automatically and permanently deleted within 7 days. The anonymous share-code ownership identifier remains associated with your current code to prevent hijacking.

Optional Self-Hosted Sharing (Your Own Server)

If you enable the lifetime "Your own server" option and enter a server URL, GPS Logger sends your current live position directly to that URL as a small JSON object while sharing is active. This data bypasses our cloud infrastructure entirely; it is routed solely to the destination you provide, and we have no oversight, access, or liability for how that server stores or processes it. The payload may include a share code, latitude, longitude, timestamp, speed, bearing, and accuracy. If you enter an API key, it is sent as an X-Api-Key request header.

You are responsible for the server URL you configure. If you do not configure self-hosted sharing, GPS Logger does not use this feature.

Purchases

GPS Logger uses Google Play Billing for Pro subscriptions and a lifetime unlock. Purchase processing is handled by Google Play. The app receives purchase status so it can unlock paid features, but it does not receive your full payment card details.

Analytics and Diagnostics

GPS Logger includes Firebase Analytics and Firebase Crashlytics. These services may collect app-instance identifiers, device or other identifiers, app interactions, in-app purchase events, approximate location derived from masked IP address, crash logs, and diagnostic information. This data is used to understand app usage, diagnose crashes, improve performance, and maintain app quality.

The app may also log events such as track started, track stopped, track exported, upgrade tapped, and upgrade completed. These events do not intentionally include your precise GPS coordinates.

Analytics and crash reporting are on by default but optional. You can turn them off at any time in Settings → About → "Share usage & crash data"; doing so disables both Firebase Analytics and Crashlytics collection on your device.

Maps

GPS Logger uses Google Maps components to display routes. Google Maps and Google Play services may process technical data needed to provide map functionality under Google's applicable terms and privacy practices.

How Data Is Used

GPS Logger uses data to:

  • Record GPS tracks that you start.
  • Show current and saved routes in the app.
  • Calculate track statistics such as distance, duration, speed, and point count.
  • Import GPX files that you select and export tracks as GPX or KML files.
  • Provide optional live sharing when enabled by you.
  • Provide optional self-hosted upload when configured by you.
  • Unlock and verify Pro/lifetime purchases through Google Play.
  • Improve reliability, diagnose crashes, and understand basic app usage.

Sharing and Disclosure

GPS Logger does not sell your personal data or share it with third parties.

Data may be transmitted only in these cases:

  • You choose to export or share a GPX or KML file through Android's share sheet.
  • You enable App Cloud live sharing, which relays your current location through Firebase, our service provider, to admitted app users who know your share code.
  • You enable self-hosted sharing and provide a server URL.
  • Google Play processes purchase information for Pro/lifetime unlocks.
  • Firebase Analytics and Crashlytics process analytics, crash, diagnostic, and identifier data as service providers for app quality.
  • Google Maps and Google Play services process data needed to display maps, provide location-related services, and process purchases.
  • Data may be disclosed if required by law or to protect legal rights, safety, or security.

Data Storage and Retention

Track history and settings are stored on your device. Tracks remain stored until you delete them, uninstall the app, or clear the app's data. Export files are created in the app cache for sharing and may be removed by the app or the Android system.

Android backup may back up app settings depending on your device settings and Google account backup settings. GPS Logger excludes the local track database and live-share device identity from Android cloud backup. You can manage Android backup in your device settings.

For App Cloud live sharing, your current position is overwritten as you move; no history trail is retained. Your position and transient follower-presence records are removed when you stop broadcasting. Resetting your share code deletes the old App Cloud share record and revokes existing followers. Any position left by an unclean disconnect is automatically and permanently deleted within 7 days. An anonymous share-code ownership identifier remains stored for your current code to prevent code hijacking.

Firebase Analytics, Crashlytics, Google Play, Google Maps, and any self-hosted server you configure may have their own retention practices for the service-provider processing they perform.

Your Choices

You can:

  • Start and stop recording at any time.
  • Pause and resume an active recording.
  • Deny location permissions, although recording will not work without location access.
  • Delete saved tracks in the app.
  • Turn off live sharing.
  • Turn off anonymous analytics and crash reporting in Settings → About.
  • Reset your share code to delete the old App Cloud share record and revoke existing followers.
  • Disable or leave blank the self-hosted upload server URL.
  • Clear app data or uninstall the app to remove locally stored app data from your device.
  • Manage Android backup and app permissions in your device settings.

Children's Privacy

GPS Logger is not directed to children. Do not use the app to collect or share another person's location without appropriate permission.

Security

GPS Logger uses Android app storage for local data. Data transmitted to Firebase, Google services, Google Play, and self-hosted upload URLs is encrypted in transit by those services or protocols. Release builds require HTTPS for self-hosted upload URLs.

No method of storage or transmission is completely secure.

Changes to This Policy

This policy may be updated when the app or its data practices change. The updated policy will show a new "Last updated" date.

Contact

For privacy questions, contact NorthforceApps at the support address above.