Security & Trust

What stays on your device, what can still reach Apple services

The landing copy, the Security page, and the Privacy Policy describe the same model: trip history stays on your device by default, while explicit iPhone map or address actions can contact Apple services in real time.

● Local

On-device by default

Trip history, saved places, vehicles, reports, and reimbursement settings stay on your device by default.
You review, correct, and export from the encrypted local state you control.
Optional iCloud backup is available on iOS when you turn it on.

● Cloud

Explicit service requests

On iPhone, explicit address lookup, route preview, reverse geocoding, Look Around, and native map rendering can contact Apple mapping services.
Optional telemetry and support conversations are separate from trip history and stay off until you enable or initiate them.
MileTrack does not host trip history on its own servers in the current beta.

Operational details

Trust needs specifics, not just a badge in the footer

These are the operational surfaces users and evaluators usually ask about when deciding whether to trust a mileage tracker with location data.

Retention and deletion

Delete-all and export controls live in the app, while optional iCloud copies remain under your Apple account controls if you enabled backup.

Export and audit trail

PDF, CSV, and XLSX exports preserve country and tax-year context so historical filing evidence remains interpretable.

Local-first storage

Encrypted local storage is the primary data boundary. The product is designed so review, classification, and report generation stay on the device by default.

Honest disclosure

The landing page, Privacy Policy, and in-app copy describe the same Apple-first beta model instead of claiming that every map or address action is fully offline.