Plain-language privacy

Your route data stays with you unless you choose to export it.

RouteLocker is designed to keep driving data local to your device. Trips, locations, notes, settings, and debug information are not sent to the developer automatically.

What RouteLocker stores

Trip logs, saved locations or sites, notes, settings, recent trip history, and any app debug information generated for troubleshooting.

Where that data lives

On your iPhone. The core privacy model is local-first. The app does not quietly upload your route history or saved locations to the developer.

When data leaves the device

Only when you explicitly use an export, backup, restore, or share action. These are user-initiated features, not background collection.

What support receives

Support only receives information you decide to send, such as an email description, an exported file, a backup file you attach, or a debug log you choose to share.

Short version

RouteLocker does not automatically receive your trip data, saved locations, notes, settings, or debug logs. Export files, backups, and log sharing happen only when you trigger them.

Location access

Location permission is required for accurate speed and route-related features. Without active location access, live speed and trip logging may be unavailable or incomplete.

Manual trip entries

When you manually add or edit a trip, RouteLocker marks that entry with an “M”. This keeps edits transparent in your trip history and exported data.