# Privacy Policy *Last Updated: 6th July 2026* We are committed to protecting your privacy and upholding strict data minimisation principles. As a local-first application, **we do not operate developer-hosted backend servers to store your journey logs**. Your personal and financial data remains under your absolute control. --- ## 1. Information We Process We purposefully restrict data tracking. The information processed by the application is divided into what stays on your device and what is handled via external integrations: * **Authentication Data:** We utilise Firebase Authentication and Google Sign-In to securely manage your identity and secure user-scoped application spaces. This processing is handled directly via Firebase and Google systems. * **Journey and Vehicle Data (Local Only):** All recorded journeys, start/end locations, postcodes, odometer overrides, vehicle registration marks, and tax variables are saved entirely within your device's secure local SQLite storage. * **Geographical Location Data:** To calculate distances and render maps, the Service processes location data. * *Real-time Tracking:* If you explicitly use background or One Tap Track location tracking features, the application accesses your device's geographical location coordinates. This stays on-device in your SQLite file. * *Postcode & Address Lookups:* When you search or add a postcode or address, the request query is forwarded to geocoding.maps.co in order to return latitude and longitude coordinates. No personal identifiers or user credentials are submitted with these lookup queries. The Service is available worldwide, but postcode/address lookup quality and tax-region configuration coverage can vary by country while regional support is expanded. * *Route Previews:* Location coordinates are processed via Mapbox APIs to generate map previews and determine shortest paths. These third-party requests are governed by Mapbox’s respective privacy policies. * **Cloud Backups (Optional & User-Controlled):** If you choose to configure cloud backups, the application streams your local SQLite database file directly into a private, hidden folder (`appDataFolder`) inside your personal Google Drive via the official Google Drive API. This backup file remains invisible inside standard Google Drive interfaces and is entirely inaccessible to us. ## 2. How We Use Your Information Because we do not collect your data on our own servers, any data processed on your device or via external APIs is used strictly to: * Maintain local journey tracking, vehicle profiles, and automatic tax-year YTD claim calculations. * Deliver region-aware tax calculations where regional tax rate packs are available. * Authenticate your identity and provision safe access tokens for Google Drive cloud integrations. * Compile local, on-demand PDF data exports and reports for your personal distribution. ## 3. Data Sharing and Third Parties We do **not** sell, rent, commercialise, or trade your personal data, location points, or trip logs to anyone. To deliver essential application logic, the frontend coordinates directly with the following processors: * **Firebase Authentication:** To securely establish user sessions. * **Mapbox APIs:** To calculate distances and fetch mapping tile layers. * **geocoding.maps.co:** To process coordinate resolutions for postcode and address lookups. * **Google Drive API:** To execute user-directed database snapshots. * **App Store Operators (Apple/Google):** To handle transaction receipts, licence checks, and premium subscription validations. ## 4. Data Security and Retention * **Local Security:** Because your database lives on your physical device, your data security depends directly on your device's baseline operating system protection. We recommend enforcing secure device screen locks and biometric protections. * **Data Retention:** We do not retain copies of your journeys. If you choose to delete your account via Firebase Auth or delete the application from your device, your local database files and authentication configurations will be deleted immediately and permanently from the device. ## 5. Your Rights Under GDPR and Global Privacy Laws Because your data is strictly stored locally on your device, you have immediate control over your data sovereignty: * **Access and Portability:** You can inspect all data at any time inside the UI or instantly export your full database schema into an open PDF or a local backup file format. * **Erasure and Correction:** You can modify, recalculate, or permanently wipe individual entries, vehicles, or your entire database directly within the local application settings. ## 6. Account and Data Deletion If you wish to delete your MileageMate: Trip Tracker account and revoke your authentication session, you can do so automatically inside the application settings. Alternatively, you can request manual deletion by emailing dev@pixelhorizons.co.uk with the subject line "Account Deletion Request" from your registered email address. Requests are processed within 30 days. ## 7. Children's Privacy Our Service is designed for licensed vehicle drivers and is not directed at or marketed to children under the age of 13. We do not knowingly process data belonging to children. ## 8. Changes to This Privacy Policy We may update this Privacy Policy from time to time to match minor adjustments in software updates or regulatory landscapes. Any new revisions will be posted transparently inside the application interface. ## 9. Contact Us If you have any questions or complaints regarding how your on-device data is processed, please contact us at dev@pixelhorizons.co.uk.