Last updated: 13 March 2026
Privacy Policy
MileTrack ("we", "us", "our") is operated by Asset Track Sp. z o.o. MileTrack is designed as a local-first mileage tracker: in the current beta, trip history, saved places, vehicles, reports, and most processing stay on your device by default.
This policy explains which data stays on your device, which actions can still contact Apple or other service providers, and which optional controls you can enable or disable.
Quick summary
The landing page, Security page, and in-app privacy controls follow the same model: MileTrack does not host trip history on its own servers in the current beta, but some explicit or optional features can still send data off-device.
On-device by default
- Trip history, saved places, vehicle setup, reports, and reimbursement settings stay on your device by default.
- Optional iCloud backup can sync this data across your iOS devices when you enable it.
- Monthly exports can be archived locally without relying on a hosted dashboard.
Explicit service requests and optional services
- On iPhone, explicit address lookup, route preview, reverse geocoding, Look Around, and map rendering can contact Apple mapping services in real time.
- Crash diagnostics and optional analytics are processed separately from trip history and remain off by default unless you enable telemetry.
- Support emails and website operations can use standard service providers, but MileTrack does not host trip history on its own servers in the current beta.
Operational controls
- Encrypted local storage and in-app export/delete controls remain the primary privacy boundary.
- If you enable iCloud backup, copies in your Apple account follow Apple account controls and retention.
- Website analytics remain consent-based, and the legal pages document every off-device path that still exists.
1. Data controller
Asset Track Sp. z o.o. is the data controller for the limited off-device processing described in this policy.
- Email: [email protected]
- Website: miletrack.app
2. Product model in the current beta
- No hosted MileTrack account is required for the current beta product flow.
- Trip history, saved places, vehicles, reports, and settings are stored locally on your device by default.
- Optional iCloud backup can sync data through your Apple account when you enable it on iOS.
- Optional telemetry is off by default and can be enabled later in the app.
- On iPhone, explicit address lookup, route preview, reverse geocoding, Look Around, and native map rendering can contact Apple mapping services in real time.
3. Data categories
3.1 On-device app data
MileTrack can store the following data locally on your device:
- Trip history, timestamps, classifications, and distance calculations
- Saved places such as home, office, and custom geofences
- Vehicle details, reimbursement settings, country profiles, and report snapshots
- Generated exports you explicitly save or share
3.2 Permissions and sensor data
When you grant the relevant device permissions, the app can use:
- Location data for trip detection and trip review
- Motion/activity signals to improve start and stop detection
- Notification permissions for reminders and health alerts
These signals are used locally for the core trip-detection workflow. Automatic trip detection does not send raw trip traces to a MileTrack backend by default.
3.3 Explicit Apple mapping requests on iPhone
When you explicitly use map or address features on iPhone, your device can contact Apple mapping services in real time for:
- Address lookup
- Route preview for manual or edited trips
- Reverse geocoding after moving a pin or resolving a current location
- Look Around verification where Apple provides coverage
- Native map tile and map rendering requests
MileTrack does not operate a separate map backend in the active beta runtime. These Apple service requests happen only when you explicitly use those map or address features.
3.4 Optional iCloud backup and sync
If you enable iCloud backup/sync on iOS, app data can be synchronized through your Apple account using Apple infrastructure. This feature is optional and disabled until you turn it on.
3.5 Optional diagnostics and analytics
If you enable telemetry in the app, we can process limited anonymous diagnostics and usage events to improve reliability. This telemetry is designed not to include raw addresses, notes, report payloads, or full route geometry.
3.6 Website data
The website can process:
- Essential browser storage for cookie preferences
- Optional consent-based website analytics
- Email/support communications you send to us
4. Legal bases for processing
| Purpose | Legal basis |
|---|---|
| Provide the app’s local mileage tracking and export workflow | Performance of contract (Art. 6(1)(b)) |
| Use device location and motion permissions for trip detection | Your consent through device/app permissions (Art. 6(1)(a)) |
| Use optional iCloud backup | Your explicit action/consent (Art. 6(1)(a)) |
| Process optional telemetry and website analytics | Your consent where required (Art. 6(1)(a)) |
| Handle support requests and product security follow-up | Legitimate interest (Art. 6(1)(f)) |
5. How we use data
- Detect, classify, review, and export trips on-device
- Resolve explicit address, route preview, and place-verification actions through Apple mapping services on iPhone
- Synchronize data through iCloud only when you enable backup on iOS
- Investigate crashes and improve reliability only when telemetry is enabled
- Operate the website, respond to support requests, and meet legal obligations
6. Sharing and recipients
We do not sell personal data and we do not host trip history on our own servers in the current beta.
Limited data can still reach the following recipients when you use optional or explicit features:
- Apple — for iCloud backup/sync and for explicit map/address requests on iPhone
- Analytics/diagnostics providers — only if you enable telemetry or website analytics
- Email/support providers — when you contact us
- Legal authorities — when required by law or valid legal process
7. Storage, security, and retention
- Local app storage is designed to use encrypted SQLite on device
- Temporary export files are deleted after share flows unless you explicitly save them elsewhere
- Local data remains on your device until you delete it, reset the app, remove the app, or remove related backups
- If you enable iCloud backup, copies in your Apple account are governed by Apple account controls and retention
- Optional telemetry and website analytics are retained only for operational and product-improvement purposes
8. Your controls and rights
You can use the app itself to exercise many privacy controls directly:
- Pause tracking
- Enable or disable iCloud backup
- Enable or disable anonymous telemetry
- Export all app data
- Delete all app data
Depending on your jurisdiction, you may also have rights to access, rectify, erase, restrict, or object to the limited off-device processing described here. Contact [email protected] if you want help with those requests.
9. Cookies and website analytics
The MileTrack website uses a consent banner and stores your choice in browser storage.
- Essential storage: always enabled for core site behavior and consent preferences
- Optional analytics: loaded only when you consent
- No ad-tech profiling: we do not run ad targeting or cross-site advertising trackers
10. International transfers
Support, analytics, or diagnostics providers may process limited operational data outside your country depending on the provider you interact with. Where required, we rely on appropriate contractual or legal safeguards for those transfers.
11. Changes to this policy
We may update this Privacy Policy as the beta evolves. If a change materially alters the data flows described here, we will update the website and in-app disclosures together.
12. Contact
If you have questions about this policy, contact us:
- Email: [email protected]
- General enquiries: [email protected]