TripMeter
Back to TripMeter

Privacy Policy

Last updated: August 9, 2026

This Privacy Policy explains how TripMeter (“TripMeter”, “we”, “us”) handles information when you use our marketing website at https://tripmeter.app and the TripMeter mobile applications for iOS and Android (including the iOS home-screen widget where available).

Contact: technologiesinfomania@gmail.com

1. Summary

  • You do not need a TripMeter account to use the app.
  • Trips, day logs, fuel and expenses, vehicles, people names, checklists, and preferences are stored on your device by default.
  • On Android you may optionally sign in with Google to back up an encrypted file to a TripMeter folder in your own Google Drive. That is not a TripMeter cloud account.
  • We do not use Apple HealthKit or device location for core features.
  • Purchases use Apple App Store / Google Play and RevenueCat. Ads use Google Mobile Ads where enabled. Firebase Remote Config may supply ad unit IDs and RevenueCat keys — we do not use Firebase Analytics or Crashlytics in the iOS app.

2. Information we process

2.1 On your device (local)

Depending on how you use the app, we may store locally:

  • Trips and rides (dates, distance, duration, budgets, bag checklists, reminders you configure)
  • Day logs: odometer legs, sub-destinations, notes, fuel fills, and expenses
  • Vehicles (photos you add, plates, mileage, service, maintenance, insurance, PUC, fines, and notes)
  • People names you attach to trips
  • Multi-currency account settings, theme, distance unit, expense categories, and similar preferences
  • Encrypted .tripmeter backup files you export or import through the system share sheet
  • On iOS, data shared with the home-screen widget via an App Group so the widget can show period stats (counts, distance, spend) — on your device only
  • Optional Preview Demo sample data bundled with the app

2.2 Photos

If you add a vehicle photo, the iOS app may request photo library access so you can pick an image. Photos stay in the app’s local App Group storage on your device. Camera access is not required for core trip logging.

2.3 Optional Google Drive backup (Android)

On Android, if you choose Google Drive backup, you sign in with Google and TripMeter may upload an encrypted backup file into a folder named TripMeter in your own Drive (using Drive file access limited to files the app creates). Google manages that sign-in. See Account & data deletion for how to remove Drive files and disconnect. This Drive option is not part of the current iOS app.

2.4 Purchases and subscriptions

Paid features are processed by Apple or Google and by RevenueCat to validate entitlements, restore purchases, and manage subscriptions. We do not receive your full payment card details. RevenueCat may process an anonymous app user identifier and purchase status. Further information: revenuecat.com/privacy.

2.5 Ads, consent, and remote configuration

  • Google Mobile Ads may show banners, interstitials, or rewarded ads when you are not on Pro (and not in Preview Demo). Google may process device and advertising-related data under Google’s advertising technologies and Privacy Policy.
  • Google User Messaging Platform (UMP) may be used to obtain advertising consent where required.
  • Firebase Remote Config may provide configuration such as ad unit IDs and the RevenueCat API key. We do not use Firebase Analytics, Crashlytics, Auth, Messaging, Firestore, or Storage in the iOS app for behavioural tracking of your trips. See Firebase Privacy and Security.

2.6 Support and feature requests

If you email us or open our feature board on Featurebase (tripmeter.featurebase.app), you provide whatever information you choose to send (for example email address and message content). That board is operated by Featurebase; see their Privacy Policy.

2.7 Marketing website

The website at https://tripmeter.app is informational. It does not require an account. Standard web server or hosting logs (for example IP address, browser type, pages requested) may be processed by our hosting provider as part of operating the site. We publish app-ads.txt for ad verification when ads are used in the apps.

3. What we do not do

  • We do not require you to create a TripMeter login or password.
  • We do not integrate Apple HealthKit.
  • We do not use device location APIs for core trip or fuel logging.
  • We do not sell your trip or vehicle history as a standalone product. Third-party SDKs (ads, purchases, Remote Config) operate under their own policies as described above.

4. Notifications

With your permission, the app may send local notifications (for example trip reminders and vehicle service / insurance / PUC expiry reminders). These are scheduled on your device and are not sent through our push servers.

5. Import and export

You may export or import encrypted .tripmeter backups. Files you export are under your control when you share or save them. On Android, optional Drive backup uploads that backup file to your Drive folder as described above.

6. Children

TripMeter is not directed to children under 13 (or the minimum age in your country). Do not use the app if you are under the applicable age without a parent or guardian.

7. International processing

Apple, Google, RevenueCat, Firebase, and other processors may process data in the United States or other countries. By using the app you understand that such transfers may occur subject to those providers’ safeguards and applicable law.

8. Your choices

See User Privacy Choices for a dedicated overview. In short:

  • Edit or delete trips, vehicles, expenses, and categories in the app
  • Revoke photo, notification, or tracking-related permissions in system settings
  • Delete the TripMeter folder in Google Drive and sign out if you used Android Drive backup
  • Delete or uninstall the app to remove local data on that device
  • Manage or cancel subscriptions in App Store / Google Play settings
  • Contact us to ask questions about this policy

9. Response times

We aim to respond to all privacy requests within:

  • General inquiries: 5 business days
  • Rights exercises: 30 days (as required by GDPR)
  • Data breach notifications: Immediately

10. Language

This Policy is provided in English. In case of translations into other languages, the English version shall prevail in case of any discrepancies.

11. Changes

We may update this Privacy Policy from time to time. The “Last updated” date will change when we do. Continued use after changes means you accept the updated policy, unless applicable law requires otherwise.

12. Contact

Questions about privacy: technologiesinfomania@gmail.com

I, Piyush, am able to communicate in Hindi, Marathi, and English.