Privacy policy

App name: DriveFive.

Provided by: DriveFive.

Support and privacy inquiries: hellodrivefive@gmail.com.

The app stores vehicle details you enter, such as nicknames, licence plates and optional VINs; trips, purposes, odometers and categories; fuel, charging, service and expenses; receipts and documents; saved places; preferences, including Android Auto trip settings; NFC assignments and unfinished drafts. GPS trips can include precise coordinates, times, routes, speed and accuracy. Trip search indexes and running-cost calculations are kept on the device; displaying records in pages does not upload your history.

With your consent and Android permission, precise location is used to record distance and routes, detect driving and stops, show current speed and GPS accuracy, and suggest starting places and destinations. A GPS trip or enabled automatic monitoring can keep using location while the screen is off or the app is in the background through an ongoing foreground-service notification. When Auto Trip or Android Auto starts are enabled, the recorder can receive location updates while waiting for a trip to begin. NFC starts GPS only after an eligible vehicle tap and the required permissions.

To stop the app’s location monitoring, finish any active trip and turn off both Auto Trip and Android Auto starts. You can also revoke location permission in Android settings. Pausing a trip does not by itself stop the foreground location service. Disabling NFC or Android Auto starts alone does not finish an already active trip. Manual records remain available when location consent is declined.

Android Auto starts are optional and separate from movement-based Auto Trip. When you enable this option, DriveFive observes the phone’s Android Auto connection status and can start a GPS trip for the garage vehicle you selected. Connection status does not identify which garage vehicle you are using. Your selected vehicle, default trip details and disconnect preferences are stored on the phone and can be included in a full backup.

You can separately choose whether a disconnection finishes a connection-started trip, immediately or after a delay. Reconnecting cancels a pending disconnect countdown. Turning Android Auto starts off cancels its pending finish countdown but leaves an active trip available to finish manually. Auto Trip has its own switch and may continue monitoring if left on. No DriveFive cloud service is used to detect the connection.

The working garage is kept in DriveFive’s private app storage. This build has no account system, advertising SDK, developer analytics upload or DriveFive-operated cloud service. The app does not sell your records.

• Optional encrypted address lookup sends precise coordinates for unnamed trip endpoints or places filled from GPS to Photon (komoot) at photon.komoot.io using HTTPS with TLS 1.2 or newer. A lookup can run when a trip finishes while the app is off-screen. It is off until you enable it in Tracking & NFC and accept the provider disclosure, including after an upgrade from 1.8.1 or a backup restore. The provider also receives your IP address and an app/version header and may keep request logs under its own practices. Routes, vehicle details, receipts and notes are not included in these requests. The public API has no account, key or API fee; reasonable-use limits and availability apply. DriveFive caches up to 128 results in memory for up to 24 hours, limits requests, rejects redirects and invalid certificates, and never falls back to an unencrypted or system-geocoder request. Turning the option off stops new lookups and clears this cache; a request already sent cannot be recalled. Existing saved addresses remain in your records until edited or deleted. GPS recording, saved place matching and manual naming work without this service. Address data: © OpenStreetMap contributors (ODbL); geocoding by Photon. Read komoot privacy information and the OpenStreetMap licence and attribution.
• Opening a point in Maps passes that location to your chosen map application.
• Opening or sharing a receipt, report, GPX, CSV or backup passes the selected content to the application or destination you choose.
• A cloud-backed backup folder is provided by its document-provider service, which may transfer files off the phone under its own terms.
• The Amazon.ca tag link opens your browser and Amazon; no vehicle data is added to the link and it contains no affiliate code.

DriveFive 1.16.1 enforces HTTPS with TLS 1.2 or newer and certificate and hostname verification for address requests. Google documents HTTPS for ML Kit’s SDK data. This protects these transfers in transit; it does not add encryption to exported ZIP files or control transfers by the cloud folder, receiving app or external browser you choose.

Versions 1.8.1 and earlier used Android’s system geocoder for optional address lookups. That device-selected provider controls its transport and processing. The HTTPS-only implementation introduced in 1.8.2 is retained in 1.16.1; address lookup remains off until you accept its provider disclosure.

Take photo opens a compatible camera app on your phone. DriveFive gives that app temporary access to one private output file so it can return a full-size receipt photo. It does not pass your existing receipts, vehicle records or trip history to the camera. Confirming a photo imports it into the selected vehicle’s documents and, when the original entry is still open, selects it for that entry. Cancelling keeps your existing entry and receipt selection.

DriveFive temporarily keeps the pending attachment and unfinished form in private app storage so it can recover them after an interruption. Temporary camera files are removed after processing or cancellation; abandoned captures and pending attachment state expire after 24 hours and are cleaned when the app next opens. Saved receipts remain until deleted and may be included in backups or exports. DriveFive does not add captures to the phone’s photo gallery. Your camera app can have its own settings, metadata, copies or cloud services, governed by that app’s privacy practices. Photo optimisation is optional and can change image quality; do not assume that every original photo’s metadata is removed.

Receipt scanning is off by default. When you enable it and scan a selected photo, Google ML Kit recognises Latin-script text on the device. DriveFive interprets that text locally to suggest fields for fuel, charging, service or expense records. Receipt images and recognised text are not sent to a DriveFive server. Google Play services downloads and manages the optional model. The SDK can send Google device and app information, identifiers, API usage and performance or diagnostic information under Google’s terms.

DriveFive initialises the recognition SDK only when a scan is requested, not at app startup. Turning scanning off prevents new scans but may not cancel a scan in progress. You choose which suggestions to apply. Saved records and attached receipts are kept in the private working garage; optional backups, exports and sharing can create copies outside the app, as described below. Manual entry remains available. Review every suggestion before applying it.

Tags contain a DriveFive link with assignment identifiers, not your receipt files or full journey history. A tag is readable by someone with physical access and is not a security credential. DriveFive checks whether the assignment belongs to the enabled garage before acting. You can disable NFC and remove or reprogram an assignment.

Create and share backup prepares a full unencrypted ZIP and gives the app you choose temporary read access. Its provider controls sign-in, destination, upload and retention. DriveFive does not connect cloud accounts or verify cloud uploads. It records creation time/size, an observable selected destination and any explicit confirmation you provide separately. Temporary shared files expire after 24 hours or may be removed sooner by Android cache management. Reminder dates and snoozes stay in the local app and are independent of folder-backup success. Disable reminders anytime in Backups.

Backups are optional and unencrypted. They can contain sensitive identifiers, precise journeys, saved places and receipts. Folder access is granted through Android’s picker. Scheduled backups use the approved destination, with older tracked scheduled copies removed only after a new one is verified. Manual exports and unrelated files are not automatically removed. A same-phone backup does not protect against losing the phone.

Use a device lock and protect exported files. Optional route retention removes eligible detailed routes while keeping trip summaries; unreviewed trips and originals retained by trip corrections are protected. Correction history, original records and their routes remain in full backups; only current trips count in ordinary reports. Photo optimisation can change receipt image quality. Drafts are bounded, and supported deletions have a temporary 30-second recovery window.

The optional widget displays the selected vehicle name and recent tracking status on your home screen. Other people viewing that screen can see those details. Remove the widget or choose another vehicle through its title. It opens DriveFive for actions and does not start background tracking by itself.

You can view, edit, export or delete your records, discard drafts, disable optional features and change permissions in Android settings. Supported individual deletions retain the affected records temporarily for a 30-second Undo window. After that window they can no longer be restored using Undo. When deleting a trip, you can keep the current odometer or explicitly enter a dashboard correction; Undo does not overwrite newer vehicle readings.

Optional old-record cleanup lets you choose a cutoff date, vehicles and record types, review the selection and confirm deletion. It offers a verified full backup first. Bulk cleanup is permanent in the working garage and has no bulk Undo. It removes associated routes and attachments that are no longer needed by retained records, while protecting shared attachments, unfinished drafts and linked corrections that do not qualify for cleanup. It preserves current odometers, reminder schedules and saved places. Bulk record cleanup does not run on a schedule.

Deleting records or running cleanup does not remove existing backups, exports or copies held by other apps or services. Those copies can still contain deleted records, receipts and routes. Restoring an older backup can bring that information back. Remove outside copies separately through the app, folder or provider where you saved them.

Clearing app storage or uninstalling removes the internal garage. Android-managed cloud backup and device-to-device transfer of the app’s private data are excluded in this build. Use DriveFive’s full ZIP backup and restore to move your garage to another phone. There are no DriveFive accounts to delete. External applications and services control their own copies, retention and privacy practices. Review the User guide for backup, restore and data-management steps.

Google SDK information: ML Kit Android data disclosure. External services also have their own privacy policies.

Creating a vehicle-history report processes the selected vehicle records and documents on your device. You choose the vehicle details, service information and optional documents to include. Generation and preview work offline and do not create a hosted public link.

Selected receipt images and PDF attachments are copied into the report without automatic redaction. They can contain names, addresses, VINs or other personal information. Review the full report and attachments before sharing. The app gives your chosen sharing destination temporary access; saved, printed and shared copies remain with you or their recipients. Temporary reports are available to the sharing provider for up to 24 hours. See the vehicle-history guide.

These website pages cannot read the garage stored inside your Android app. The website guide search runs in your browser; it does not send your search text or app records to DriveFive. The website uses locally served fonts and does not include advertising pixels or third-party analytics scripts.

Loading the website sends ordinary connection information, such as your IP address, browser information, requested page and request time, to the hosting infrastructure. Hosting and access-control services may process technical logs and session information to deliver and secure the site. The website is hosted with OpenAI Sites; see OpenAI’s privacy policy for its practices. External links and email links open services with their own privacy practices.

If you email the publisher, we receive your email address, message and any attachments you choose to send. We use that information to respond to your request, provide support or administer requested tester access. Sending a support message does not subscribe you to marketing. Include only the information needed to explain the issue. Support correspondence is kept only as long as needed for those purposes and applicable legal obligations.

Contact DriveFive at hellodrivefive@gmail.com for privacy questions or to request access to, correction of, or deletion of personal information under the publisher’s control, subject to applicable legal requirements and exceptions. We may ask for information reasonably needed to verify your identity and locate the relevant information. The publisher cannot remotely retrieve or delete the garage stored only on your phone.

Use the app and Android settings to manage optional permissions and your on-device records. Withdrawal of permission may prevent the related optional feature from working. Nothing in this policy removes rights under applicable Canadian privacy law. You may raise a concern with the Office of the Information and Privacy Commissioner for British Columbia or, where federal law applies, the Office of the Privacy Commissioner of Canada.

Updates to this policy will appear on this page with a revised effective date. For questions about this policy or your information, contact hellodrivefive@gmail.com.