Privacy Policy

Section 1 — Introduction

DriveLedger (the "App") is committed to protecting your privacy. This Privacy Policy explains how information is handled when you use this mileage logging app for freelancers and gig workers.

By using the App, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use the App.

The App is a mobile application for personal use. All trip records and vehicle data are processed and stored locally on your device.

Section 2 — Information We Do Not Collect

The App is designed with privacy in mind. By default, we do not collect, transmit, or store:

• Your name, phone number, or home address
• Financial account information (bank or tax-filing account details)
• Real-time location data or GPS coordinates (trip start / destination fields are free-text labels you enter manually)
• Device identifiers for tracking purposes
• Browsing history or behavioral data
• Contacts
• Biometric data

Optional account creation (for device transfer only): The App uses anonymous authentication by default — no account creation is required to use the App. If you choose to create an account in order to transfer your Pro subscription to a different Android device, you may voluntarily provide an email address. This data is processed by Firebase Authentication (Google LLC). See Section 5 for details.

Section 3 — Local Data Storage

The following data is stored locally on your device in a local database and in preferences storage:

• Trip records (date, start / destination, distance, odometer values, purpose, notes)
• Vehicle information (nickname, year, make, model, odometer, unit preference)
• Favorite routes
• Mileage deduction rates (IRS / CRA / HMRC / ATO reference values)
• Settings (distance unit, currency, language, theme, backup frequency)
• Trip photos (if you attach them — saved to the app's sandboxed directory)

The following data is managed externally:

• Authentication state — an anonymous or signed-in Firebase UID is managed by Firebase Authentication (Google LLC) and cached locally. This identifier contains no personal information unless you sign in with an email address.
• Pro subscription status — subscription entitlements are verified and cached by RevenueCat, Inc. See Section 5 for details.
• Optional Pro cloud backup — if you enable cloud backup, encrypted backup files are stored in your own Google Drive (app-specific hidden folder). We have no access to these files. See Section 4.

Your trip records are never transmitted outside your device unless you explicitly enable cloud backup or export them.

Section 4 — Data Encryption & Cloud Backup (Pro)

The App offers an encrypted backup feature for Pro users. When creating a backup:

• Data is encrypted using AES-256 encryption
• The encryption key is embedded within the backup file
• Backup files are saved to a location you choose (local share) or to your own Google Drive when cloud backup is enabled
• We cannot access your encrypted backup data
• Backup contents include: encrypted database, plain-text CSV exports per table (for readability without the app), and any trip photos you attached

Section 5 — Third-Party Services

The App integrates with the following third-party services, which may collect information independently:

A. Google Play Store

• Download and installation data
• App version and update information
• Crash reports (if enabled in device settings)
• Payment processing for Pro subscriptions
• Subject to Google's privacy policy

B. RevenueCat (Subscription Management)

The App uses RevenueCat, Inc. to manage and validate Pro subscriptions. RevenueCat acts as an intermediary between the App and Google Play Store to provide reliable receipt validation and subscription tracking.

Information RevenueCat receives:

• An anonymous app user ID (your Firebase UID — contains no personal information by default)
• Purchase receipts from Google Play for validation
• Subscription status (active / expired / refunded) and entitlement data
• Platform and app version information

Information RevenueCat does not receive:

• Credit card numbers, billing address, or payment credentials
• Your trip records, vehicle data, or photos

RevenueCat's privacy policy: https://www.revenuecat.com/privacy

C. Firebase Authentication (Google LLC)

The App uses Firebase Authentication to provide anonymous authentication by default and optional account creation for Pro subscription transfer across Android devices.

By default (anonymous mode):

• An anonymous user ID is created automatically — no personal information is associated with it
• This ID is used as the RevenueCat app user ID to link your subscription to your device

If you choose to create an account (for device transfer only):

• Your email address and hashed password (if using email sign-in) are stored in Firebase Authentication
• Google account information (name, email) may be received if you sign in with Google

Firebase Authentication's privacy policy: https://firebase.google.com/support/privacy

D. Google Drive (Pro cloud backup)

If you enable cloud backup (Pro feature):

• Encrypted backup files are stored in your own Google Drive appData folder (an app-specific hidden folder managed by Google Drive)
• We have no access to these files; they are stored in your personal cloud account
• Backup history metadata (file names, timestamps) is kept locally in preferences storage

E. Device Operating System

• Android may collect diagnostic data
• Crash reports may be sent to Google depending on your device settings
• We do not control OS-level data collection

Section 6 — Data Sharing and Disclosure

We do not sell, rent, or trade your data to third parties.

We do not share data with third parties except:

• When required by law (court order, warrant, regulatory requirement)
• To protect our legal rights or prevent illegal activity
• With your explicit consent

Since we do not collect personal data on our servers, there is generally no data to share in most situations.

Section 7 — Analytics and Crash Reporting

The App does not include:

• Analytics SDKs (Google Analytics, Firebase Analytics, Crashlytics, etc.)
• User tracking or behavioral monitoring
• Advertising SDKs or ad networks
• Social media integrations

Note on Firebase: The App uses Firebase Authentication only — not Firebase Analytics, Firebase Crashlytics, or any other Firebase product. No usage data, session data, or crash reports are sent to Firebase.

However, if enabled in your device settings, the OS may automatically collect crash diagnostic information. To disable:

• Android: Settings → Google → Usage & Diagnostics (Off)

Section 8 — Children's Privacy

The App is not intended for users under 13. If we become aware that a child under 13 has provided information, we will take prompt action to remove it.

Section 9 — Data Retention and Deletion

Your trip data remains stored locally on your device until you:

• Manually delete trips or vehicles within the App
• Uninstall the App
• Perform a factory reset on your device

Account data (if you created an account): Your Firebase Authentication account (email address and anonymous UID) can be deleted by contacting us at the address listed in Section 17. Upon request, we will delete your Firebase account and associated RevenueCat data. Note that deleting your account will permanently remove the link between your subscription and your account; subscription history managed by Google Play Store cannot be deleted by us.

Anonymous sessions (no account created) do not store any personal data on our servers.

Section 10 — Data Security

Security measures in place to protect local data:

• Local database stored in an app-specific directory (inaccessible to other apps)
• AES-256 encryption for backup files
• Secure storage for sensitive settings (flutter_secure_storage)
• No network transmission of trip data except explicit cloud backup to your own Google Drive

However, no system is completely secure. Risks such as device theft, malware, and OS vulnerabilities exist. You are responsible for maintaining the security of your device.

Section 11 — International Data Transfers

Your trip records are stored locally on your device and are not transferred internationally unless you enable cloud backup to your own Google Drive account.

The following data may be transferred internationally by third-party services:

• Firebase Authentication (Google LLC): Authentication data (anonymous UID or email if provided) may be processed on servers in the United States or other countries where Google operates. Google LLC is certified under the EU-U.S. Data Privacy Framework.
• RevenueCat, Inc.: Subscription status and purchase receipts may be processed on servers in the United States. RevenueCat, Inc. is based in the United States.

By using these features, you consent to the transfer of applicable data to these services as described in their respective privacy policies.

Section 12 — Your Rights and Choices

You have full control over your data:

• Access: All trip data is accessible within the App
• Edit: Any trip or vehicle record can be edited or updated
• Delete: Individual records can be deleted from within the App
• Export: AES-256 encrypted backups and CSV exports can be created (Pro feature)
• Account deletion: If you created an account, contact us to delete your Firebase account and associated data (see Section 9 for details)
• Opt-out of account creation: The App functions fully without creating an account. Anonymous authentication is used by default and requires no personal information

Since trip data is stored locally on your device, data subject access requests (GDPR, CCPA) do not apply to trip records — they are already under your control on your device. For account data held by Firebase, you may request deletion as described in Section 9.

Section 13 — California Privacy Rights (CCPA)

Since DriveLedger does not collect personal information on servers, does not sell personal information, and stores all data locally on your device, most CCPA provisions do not apply to our operations.

Section 14 — European Privacy Rights (GDPR)

Since we do not collect or store personal data on our servers, our GDPR obligations are minimal. All data is on your device under your control. For data related to Google Play, please contact Google directly.

Section 15 — Changes to This Policy

We may update this Privacy Policy. For material changes, we will notify you through an app update. Continued use after changes constitutes acceptance of the updated policy.

We will not reduce your privacy rights without your explicit consent.

Section 16 — Limitation of Liability

To the maximum extent permitted by applicable law, we are not liable for:

• Data loss or corruption
• Unauthorized access to your device
• Backup failures
• Third-party privacy practices (Google Play Store, OS providers, Firebase, RevenueCat)

Section 17 — Contact

For privacy-related requests including account deletion, data access, or questions about this policy, please contact us through the Contact page or via the support link within the App.