Privacy policy

RouteLocker does not collect your data.

RouteLocker does not collect, upload, sell, rent, or share your saved locations, trip history, trip notes, or usage information. Information leaves the device only if you choose to export it or share a location yourself.

What stays on the device

Your RouteLocker data stays local.

Saved locations, coordinates, trip history, notes, preferences, and backup-related information stay on your device during normal app use.

What can leave the device

Only user-initiated sharing or export.

If you export data or share a location, that transfer happens because you chose it. RouteLocker does not send that information anywhere automatically.

What RouteLocker does not collect

  • Saved locations or their coordinates
  • Trip history
  • Trip notes
  • Backup files
  • Usage analytics or advertising identifiers

When data leaves the device

Data only leaves the device if you use an export feature or share a saved location through a method you selected.

Support requests

If you contact support, you choose what details to send. The app does not automatically attach your saved data to support requests.

1. No account required

You do not need an account to use RouteLocker.

There is no account system that stores your saved locations, trip history, or notes on a RouteLocker server.

2. No analytics collection

Normal app use does not generate analytics collection for us.

RouteLocker does not collect behavioral analytics about your routes, destinations, or trip activity.

3. Backups are under your control

Backup and restore happen because you choose them.

Backup, import-and-merge, and full restore are user actions. They are not background syncing features.

4. Shared locations

Sharing a location is optional and manual.

If you share a saved location, that information is sent only through the method you selected at that time.

5. Policy updates

This page should change only if the app’s data behavior changes.

If RouteLocker ever changes how it handles data, this privacy policy should be updated to match before or alongside that change.