OnTravelPlan English policy

Privacy Policy

OnTravelPlan stores trip-related data on your device by default. Selected external services may be used only when you trigger features such as share-link generation or opening external links.

1. Data stored on your device

The app mainly stores travel plans, itinerary groups, cards, notes, selected images, and backup files on your device. These items are used to display schedules, support editing, restore backups, and handle share or import flows.

Stored on device Trip titles, schedules, memos, categories, imported images, backup files
Requested permissions Camera for scanning shared trip QR codes, and photo or media access for saving shared images

2. Data that may be sent to external services

  • When you choose link sharing, share data is encoded in the link itself.
  • When you open an external browser or map app, that app or service may process the request.
  • Third-party services: The app uses Google AdMob (advertising) and Firebase Analytics (analytics). These services may collect device identifiers, advertising data, and app usage data to serve personalized ads, measure ad performance, analyze app usage, improve stability, limit ad frequency, and prevent fraud or abuse. On iOS, the app requests permission through Apple's App Tracking Transparency framework before using the advertising identifier or data for tracking-based advertising or measurement. If permission is denied or restricted, ads may still appear but will be limited or non-personalized, and tracking-based analytics collection remains disabled. For more info, see How Google uses data when you use our partners' sites or apps.
  • Map and Location-based services: The app uses Google Maps and Apple Maps APIs to provide place search and map interfaces. However, the app does not collect, use, store, or request your current location data. Only the search terms entered by you are sent to the respective map providers to retrieve search results. The handling of this data is governed by the privacy policies of each provider.
  • HTTP headers or operational logs may be processed by hosting infrastructure for reliability and abuse prevention.

3. Why this data is used

  • To display and manage travel plans and cards on your device.
  • To support sharing features such as QR scanning, saving shared images, and generating share links.
  • To serve relevant advertisements and analyze app usage to improve features and stability.
  • To support backups, recovery, and app stability.

4. Current app details

  • No mandatory account registration or sign-in flow.
  • Camera permission may be needed for QR scanning, and photo or media permission may be needed to save shared images.
  • The app includes Google AdMob and Firebase Analytics SDKs. Ads may appear and usage data may be collected as described above.
  • The app does not include persistent background location collection.

5. Your controls

  • You can decline camera or photo permissions, although QR scanning or saving shared images may stop working.
  • Ad Settings: On iOS, you can allow or deny tracking permission when prompted and later change it in iOS Settings. If tracking permission is denied or restricted, ads may still appear in a limited or non-personalized form. On Android, you can manage ad privacy choices in your device or Google settings where available.
  • You can remove local trip data and backup files through the app's data-management flows.
  • You can avoid external sharing flows by not using share-link generation, QR scanning, or image saving features.

6. Contact and updates

If you need support, contact [email protected] or visit the support page. This page will be updated if the app's data handling or third-party services change.

Last updated: 2026-04-30