Privacy Policy — Trip Tracker
Effective date: October 6, 2026
Trip Tracker is provided by Trip Tracker Software. This policy explains what information the app stores, what limited technical and product-usage information is transmitted, and how that information is used.
Information stored on your device
Trip Tracker stores the records you create or import, which may include Trips, Stops, Locations, equipment, reference numbers, mileage, pay and expense records, notes, reminders, images, reports, backups, and related workflow information. These working records are stored locally on your device. Trip Tracker does not provide a developer-hosted account or cloud database for these records.
Backups and exports are created only when you choose to create or share them. Copies kept outside the app remain under your control and must be deleted from their saved location separately.
Camera, images, and on-device text recognition
Trip Tracker uses the camera or Android file/photo picker only when you choose to capture or select an image. Images may be attached to records or used by the optional Fuel OCR feature.
Fuel OCR uses the bundled Google ML Kit Text Recognition model to examine the selected image on your device and suggest Fuel values for your review. Trip Tracker does not send the image, the recognized text, or the suggested Fuel values to Trip Tracker Software or to Firebase Analytics. Temporary OCR images are removed when they are no longer needed unless you choose to retain the image with the saved Fuel Event.
The ML Kit SDK may transmit limited technical diagnostics and usage information to Google, such as device and app information, a per-installation identifier, performance measurements, API configuration, input/output size, feature version, feature events, and error codes. This telemetry does not include the image or recognized text.
Product analytics
Trip Tracker uses Google Analytics for Firebase to understand app acquisition and a small product funnel. Analytics collection is on by default. It may collect an app-instance identifier, approximate location derived from a masked IP address, app lifecycle and interaction events, and Google Play in-app purchase events such as product ID, product name, and price.
Trip Tracker sends only a fixed set of custom product events: Trip-creation progression in broad buckets, Trial limit reached, an attempted Trip creation blocked by the Trial limit, viewing the full Pro offer, and successfully starting the Google Play purchase flow. These events do not include the substantive contents of your records.
Trip Tracker does not send Trip, Stop, Location, customer, route, load, reference, Tractor, Trailer, date, coordinate, mileage, pay, expense, weight, note, image, filename, free-form text, purchase token, order ID, email address, personal name, account identifier, or user-assigned ID to Firebase Analytics.
Advertising ID collection and ad-personalization signals are disabled. Trip Tracker does not use analytics for personalized advertising, remarketing, or audience sharing. Analytics may be used to measure whether acquisition efforts lead to first use, Trial activity, and Pro purchase flow.
Purchases
The optional Pro upgrade is processed by Google Play. Trip Tracker Software does not receive or store your payment-card details. The app receives the purchase status needed to provide and restore Pro access. Google Play and Google Analytics may process purchase information under Google's own terms and privacy practices.
Data sharing and sale
Trip Tracker Software does not sell personal data. Limited analytics and SDK diagnostic data is transmitted to Google as a service provider for the purposes described above. Trip Tracker does not send your locally stored Trip Tracker records, images, or recognized OCR text to advertising partners or other third parties.
Retention and deletion
Local app records remain on your device until you edit or delete them, clear the app's data, or uninstall the app, subject to backups or exported copies outside the app. Trip Tracker Software does not keep a server copy of those records.
Analytics and SDK diagnostic data is retained and processed by Google according to the applicable Google service terms and the configured retention settings. Trip Tracker does not attach a name, email address, or Trip Tracker account to Analytics data and does not provide an in-app control for deleting already transmitted Analytics events.
Security
Trip Tracker keeps its working records on the device. Their security depends in part on the security of your device and any backup or export locations you choose. The Analytics and ML Kit technical data described above is encrypted in transit by Google.
Children's privacy
Trip Tracker is not directed to children.
Changes to this policy
This policy may be updated when Trip Tracker's features or data practices change. The current version will be published at this address with a revised effective date.
Contact
Trip Tracker Software
triptrackersoftware@gmail.com