Privacy Policy

1. Introduction

This Privacy Policy describes how Roamlog ("we," "our," or "the App") handles data when you use our Android application. Roamlog is developed by an independent developer and is committed to protecting your privacy.

By using Roamlog, you agree to the practices described in this policy. If you do not agree, please discontinue use of the App.

2. Data Controller

The data controller responsible for your personal data is:

• App Name: Roamlog
• Platform: Android (Google Play Store)
• Contact: support@roamlog.dev

3. Data We Collect and Store

Your trip content is stored exclusively on your device. Purchase license data may be sent to a verification backend solely to confirm a Google Play purchase before Pro access is granted.

Data Type	Purpose	Storage Location
GPS Location Coordinates	Pin stops, campsites, and points of interest on the map	Device only (local SQLite database)
Photos	Attach images to trip stops as visual memories	Device only (local app storage)
Trip Data	Store trip names, dates, descriptions, vehicle info, and notes	Device only (local SQLite database)
Fuel and Cost Entries	Track fuel consumption, costs, and multi-currency expenses	Device only (local SQLite database)
Vehicle Information	Store vehicle name, odometer, fuel type, and maintenance reminders	Device only (local SQLite database)
Purchase Token and License Status	Verify and remember the one-time Pro unlock	Device preferences; purchase token may be sent to the configured verification backend and Google Play Developer API

4. Permissions Requested

Roamlog requests the following device permissions:

4.1 Location (GPS)

• Permission: ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION
• Reason: To record the GPS coordinates of your stops and fuel entries when you actively tap the "Capture GPS" button, and optionally to show your live position on the map via the "Follow Me" feature. Roamlog does not track your location in the background. The live position stream is paused when the app is backgrounded.

4.2 Photos

• Permission: READ_MEDIA_IMAGES (Android 13+)
• Reason: To select photos from your gallery and attach them to trip stops or vehicle documents. Photos can also be taken directly with the camera via the system image picker. All photos are stored locally in the app's private directory.

4.3 Notifications

• Permission: POST_NOTIFICATIONS, RECEIVE_BOOT_COMPLETED, VIBRATE
• Reason: To send optional daily logging reminders and vehicle document expiry reminders (e.g., insurance, inspection). RECEIVE_BOOT_COMPLETED reschedules reminders after a device reboot. You can enable or disable the daily reminder at any time from Settings. Notifications are never used for marketing or advertising.

4.4 Network

• Permission: INTERNET
• Reason: To fetch map tiles, currency exchange rates, vehicle make/model data, and verify Google Play purchases. See Section 5 for full details. All core trip logging features work offline; network access is only needed for these optional enrichments and billing checks.

5. Third-Party and Functional Network Services

Roamlog communicates with the following services for specific app functions. These services do not receive your trip notes, photos, costs, or journal entries. Only the specific data described below is transmitted.

5.1 Google Play Billing

• Purpose: To process the one-time in-app purchase for the full version (including 7-day free trial).
• Data Shared: Google handles payment processing. Roamlog does not receive your payment card details. Google may share a purchase token with the app. The app may send that token, package name, and product ID to the configured Roamlog purchase verification backend, which verifies the purchase with the Google Play Developer API before Pro access is granted.
• Privacy Policy: Google Payments Privacy Notice

5.2 TomTom — Map Tiles

• Purpose: To display map tiles in the interactive journey map.
• Data Shared: Map tile requests include tile coordinates (x/y/z) derived from the map viewport. No trip notes, photos, costs, or journal entries are included in these requests.
• Privacy Policy: TomTom Privacy Statement

5.3 Local Approximate Trip Line

• Purpose: To show the order and overall shape of your logged stops on the map.
• Data Shared: None. The line between stops is calculated locally on your device and is not sent to a routing provider. It is not turn-by-turn navigation or a road-accurate route.

5.4 Frankfurter API — Currency Exchange Rates

• Purpose: To fetch current currency exchange rates for multi-currency cost conversion.
• Data Shared: Only the base currency code (e.g., "EUR") is sent as a URL parameter. No personal data is transmitted. Exchange rates are cached locally for 24 hours and used offline.
• Website: frankfurter.app

5.5 NHTSA — Vehicle Make/Model Data

• Purpose: To provide vehicle make and model suggestions when adding a vehicle.
• Data Shared: Only vehicle make names are sent as URL parameters to the public NHTSA API. No personal data is transmitted. Results are cached locally for 30 days.
• Website: NHTSA VPIC API

Roamlog does not use any analytics SDKs (e.g., Google Analytics, Firebase Analytics), advertising SDKs, crash reporting services, or social media SDKs.

6. Data Sharing

We do not sell, rent, trade, or otherwise share your personal data with any third party for any purpose, except as described in Section 5 for the sole purpose of providing the app's core functionality (maps, currency conversion, vehicle data, and billing). Your trip notes, photos, costs, and journal entries are never transmitted to any server.

7. Data Retention

Trip data is retained on your device for as long as you have the app installed. If you uninstall Roamlog, all locally stored trip data (trips, stops, photos, fuel entries) is permanently deleted. We have no ability to recover it, as we never possess your trip content. Purchase verification records may be retained only as needed to validate and maintain your Pro license.

8. Data Export

You can export your trip data at any time using the built-in PDF export feature. The generated PDF includes trip statistics, stop details with GPS coordinates, and up to 3 photos per stop. PDFs are generated locally on your device and shared via the Android share sheet — no data is uploaded to any server during this process.

9. Children's Privacy

Roamlog is not directed at children under the age of 16. We do not knowingly collect personal data from children. If you believe a child has used the app and you wish to have any data removed, please contact us and we will assist to the extent possible (given that all data is device-local).

10. Security

Since all data is stored locally on your device, the security of your data depends on the security of your device itself. We recommend using a device lock (PIN, pattern, or biometric) to protect your information. Roamlog uses the local network only for the functional services described in Section 5; your trip data, photos, and notes are never transmitted.

11. Your Rights (GDPR / EU Users)

If you are a resident of the European Economic Area (EEA), you have the following rights under the General Data Protection Regulation (GDPR):

• Right of Access: You can access all your data directly within the app at any time.
• Right to Rectification: You can edit any trip, stop, or entry directly in the app.
• Right to Erasure: You can delete individual entries, entire trips, or all data by uninstalling the app.
• Right to Data Portability: You can export your data using the PDF export feature.
• Right to Object: Roamlog does not perform automated decision-making or profiling.
• Right to Lodge a Complaint: You may lodge a complaint with your local supervisory authority.

12. International Users

Roamlog is available worldwide. Your trip content stays on your device regardless of your location. Functional network requests described in Section 5, such as purchase verification, map tiles, currency rates, and vehicle lookup, may be processed by service providers in other countries.

13. Google Play Developer Requirements

In compliance with Google Play's Developer Program Policies, we disclose:

• Roamlog collects device location data (GPS) to enable stop and fuel entry mapping, and optionally for the "Follow Me" map feature.
• Location data is collected when the user actively taps the "Capture GPS" button while logging a stop or fuel entry, or when the user activates the "Follow Me" button on the map screen.
• Saved stop coordinates are not sent to an external routing service. The approximate trip line is calculated locally on the device. No route coordinates or live tracking data are shared with third parties. See Section 5.3 for details.
• Roamlog does not access location in the background. The map "Follow Me" position stream is paused when the app is backgrounded.
• Photos and gallery access (READ_MEDIA_IMAGES) are used solely for attaching images to trip stops and vehicle documents.
• Google Play purchase tokens may be sent to the configured purchase verification backend solely to validate Pro entitlement.
• No analytics, advertising, or crash reporting SDKs are present in the app.

14. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the "Last updated" date at the top of this page. Continued use of the app after changes constitutes acceptance of the updated policy.

15. Contact

If you have any questions or concerns about this Privacy Policy or your data, please contact us at:

• Email: support@roamlog.dev