IFTA Miles Privacy Policy
Last updated October 25, 2026
IFTA Miles is provided by Apponance Inc. This policy covers the IFTA Miles app (com.apponance.ifta) on iOS and Android and the IFTA Miles web app at ifta.milelog.io. Contact us at admin@apponance.com.
1. Your records and location
IFTA Miles records the trips, trucks, fuel purchases, receipts, carrier details, notes and corrections you enter. When you start GPS recording, the app records precise location and timestamps, including while the screen is locked or the app is in the background during that trip. Location supports route maps and mileage allocation by state or province. If you turn on “Detect trips automatically” in Settings → Recording (off by default), the app asks for “Always” location permission so it can notice when your truck leaves a stop and start recording; location is then monitored between trips until you turn that setting off. Camera and selected-photo access let you attach receipt originals.
2. Account and cloud backup
Records are stored on your device. An account is required to use IFTA Miles: you sign in with Google or Apple, and we use Firebase Authentication for your account identifier, name and email supplied by that provider. Firebase Firestore and Cloud Storage store your account’s records, original GPS tracks and receipt images so they can be restored on another device. Cloud evidence is private to your account and transferred over encrypted connections. Signing out clears the app’s account data on the phone only after backup verification; it does not delete your cloud account.
The IFTA Miles web app at ifta.milelog.io uses the same account. After you sign in with Google or Apple it keeps you signed in with a secure session cookie for up to 14 days, and shows the trips, fuel purchases, receipt images, reports and carrier profile (name, address, IFTA account, USDOT number and base jurisdiction, which the app backs up to your account) that your account has synced. On the web you can mark trips reviewed and download worksheet and mileage files; everything else is edited in the app. The web app uses no analytics or advertising tools; our servers keep standard request logs (page address, time, IP address and browser type) as described below.
3. Maps and route estimates
Maps and address lookup use the platform’s map and geocoding services (Apple on iOS, Google on Android). Route-assisted manual entry sends the selected route coordinates to Apponance’s routing service at osrm.finabase.io to calculate an estimate. These estimates are separate from recorded GPS evidence. These services receive the queries needed to return maps, addresses or routes.
On the web, trip routes are drawn with Google Maps: your browser loads Google map data for the area of the route shown.
4. Purchases, diagnostics and support
Apple and Google process subscription payments. The app uses purchase identifiers and entitlement information to provide paid features; we do not receive your full card details. Firebase Crashlytics and Apponance app-health reporting receive crash, device, version and performance diagnostics to help us fix problems. Contact Us sends the name, email and message you provide, with app version, platform, IP address and user agent, to Apponance support.
If you turn on email reports in Settings, Apponance sends you a monthly or quarterly summary of your recorded activity (never tax figures) at your verified account email through Amazon Web Services (Amazon SES), from the sender noreply@milelog.io; every report carries an unsubscribe link and you can turn reports off in Settings at any time.
5. How information is used
IFTA Miles has no advertising SDK, does not sell personal data, and disables Firebase Analytics collection. We use the information described above to operate the app, restore your records, support purchases, respond to support requests and maintain reliability. Our service providers process data for those purposes; data may be processed outside your country. Google Firebase and Google Cloud provide authentication, database, file storage, functions and crash reporting; see Firebase privacy information.
Where the GDPR or UK GDPR applies, we rely on performance of a contract for accounts, sync, purchases and support; consent for device permissions; legitimate interests for reliability, security and abuse prevention; and legal obligations where records must be kept.
6. Retention and account deletion
Your account records remain until you delete your account. Deleting an individual record moves it to history or Trash; its original evidence is retained with your account for your audit trail. Delete Account permanently removes the account’s Firestore records, GPS objects, receipt objects and Firebase sign-in identity. Failed deletion steps are retried automatically. A minimal technical deletion marker (account identifier and deletion timestamps) is retained indefinitely to prevent old devices or credentials from recreating deleted data; it contains no trip, receipt or profile content.
We delete account content from our servers promptly; email requests are normally completed within 7 days. Backups and logs age out afterwards. Contact Us messages are kept while we handle your request and for our support records afterwards; you can ask us to delete them at any time. Firebase crash data is retained for its standard 90-day period and server request logs for 30 days. Records we are legally required to keep, including applicable payment records, are retained only for the period the law requires, then deleted. Apple and Google retain their own payment records under their policies.
7. Your choices and requests
You can export your records, change device permissions, or request access, correction or deletion through admin@apponance.com. We respond within 30 days and may ask you to confirm your identity. See Delete your IFTA Miles account for in-app and email instructions. Exported files and backups you save outside IFTA Miles remain under your control. Uninstalling the app does not delete a cloud account. Deleting your account does not cancel a subscription; manage it in Apple or Google subscription settings.
You may also complain to your local data protection authority. We will update this policy when our practices change.