Trip Diary: Offline Travel Journal — Privacy Policy
Last updated: 2026-10-05
This privacy policy applies to the mobile app "Trip Diary: Offline Travel Journal" for Android:
- Google Play: package com.simonj.traveljournal, developer "Global Utility App Maker"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Trip Diary does not require an account, and we do not sell personal information. You create trips and write day pages with notes, weather, mood, photos, places and expenses, and you can turn a trip into an HTML or PDF travel book. "Offline" means that writing, the map and making books work without a connection and without a server run by the developer; your journal is kept in the app's storage on your device. The app still uses the internet for Google analytics, crash reporting, remote configuration and advertising, as described below.
PHOTOS AND PLACES
The app does not use the camera or the microphone. When you tap "Import original photos", the app first explains photo location access and offers "Import without locations" or "Continue". If you choose "Continue", it asks Android for media location access each time, before the system file picker opens. Only the image files you choose are given to the app. The app copies each chosen file as the picker provides it into its own storage; it does not remove or add metadata, but the picker may already have removed location data from the copy. Only if you chose "Continue" and media location access is granted does the app read GPS coordinates and the capture date and time, from the original photo's metadata on your device. It does not read them from its own copy, so photos imported with "Import without locations", without that access, or without readable GPS data in the original are saved without coordinates. Coordinates found are saved as that photo's location (labelled with the file name, with the capture time if present) and are used for the map, trip paths and books. If you choose "Import without locations" or access is not allowed, the photos are still imported and the app notes that location pins may be unavailable. "Remove pin" removes a photo's location.
When you tap "I'm here", the app first explains the request, then asks for location permission (while the app is in use only) and reads your position once. The coordinates, their accuracy and the time are saved as a pin on that day. If you decline or location is unavailable, nothing is saved and you can still type a place with latitude and longitude yourself. The app does not track your location in the background. The map is drawn on your device from a basemap included in the app; pins are not sent to a map service.
INFORMATION STORED ON YOUR DEVICE
For each trip the app keeps the title, start and end dates and home currency. For each day page it keeps your notes, weather note, mood, photos (the app's copy of each file, its original file name, type, size and any photo location with its capture time), places (label, latitude, longitude, how and when it was added and, for "I'm here" pins, the accuracy), and expenses (description, amount, currency and any exchange rate you enter; rates are not fetched online). There is no fixed limit on the number of trips, day pages or photos. The app also keeps a list of the IDs of deleted trips and day pages, without a limit, so that restoring a backup does not bring them back.
The journal is saved in files in the app's storage. When a day page is saved, the app first writes a recovery copy of it and removes that copy once the journal has been saved. For both the journal and the recovery copies, the app keeps the current and the previous saved version. The app may also store basic operating information such as cached advertising settings, a cached More Apps list, a session count and review-prompt state, and a list of imported backups.
The developer does not run a server that receives your journal. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not upload your trips, day pages, places, expenses or photos. When you open More Apps, app icons are loaded from the web addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches, the start screen view, when a launch ad is shown, a running count of app sessions, ad revenue events (ad format, value, currency and precision), app version, device type, and app-instance identifiers. These events do not include trip titles, notes, places, coordinates, expenses, photos or file names.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob. AdMob may also request ads from the InMobi and Liftoff (Vungle) mediation networks. Google and these partners may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location. The app's own code does not give your location or journal places to analytics or ad services; if you have allowed location permission, ad SDKs included in the app may be able to access device location under their own policies.
A banner ad is shown at the bottom of the Trips tab; it is not shown on the Map or Export tabs or while a day page or the trip form is open. A full-screen ad may appear when the app starts or when you return to it, after you save a day page or create a book, and a native ad may appear in the exit dialog. When you return to the app, it does not start an app-open ad while a day page, the trip form or the menu is open, or while a book is being created.
PERMISSIONS AND ADVERTISING CHOICES
The feature permissions the app may request are location, only when you tap "I'm here", and media location access, only when you choose "Continue" after tapping "Import original photos", as described above. Media location access lets the app read location data saved in the photos you pick; it does not give the app your device's current location. The app does not request camera, microphone, photo library, contacts, Bluetooth, health data, background location or notifications. Haptic feedback uses Android's vibration permission, which does not show a request.
When the app starts, Google's consent message (UMP) is checked first. Personalized ads are requested only where Google reports that consent is not required or your choice allows them; otherwise ads are non-personalized. If the consent check fails or Google reports that ads cannot be requested, the app does not request ads until it is started again. The app works whatever you choose. Where Google requires it, the app menu shows "Privacy choices", which reopens the consent message so you can change your advertising choice.
STORAGE AND YOUR CONTROL
On a day page you can edit or clear text and, after confirming, use "Remove" on a photo, place or expense. When the change is saved, a removed photo's file is deleted from the app's storage unless another day page or a recovery copy still uses it; photo files that no day page or recovery copy uses are also deleted when the app starts. "Delete trip" in Trip details removes the trip, its day pages and their recovery copies from the journal, deletes their photo files unless another day page or recovery copy still uses them, and deletes the books the app created for that trip. It does not delete earlier backups, and the previous saved version of the journal and of the recovery copies may remain in the app's storage. "Storage saver" in the menu replaces a trip's photo files with resized JPEG copies; the original files are then deleted from the app's storage unless another day page or recovery copy still uses them. You can also clear the app's data on Android or uninstall the app. Local data may be included in a Google or device backup depending on your backup settings; uninstalling normally removes the active copy but may not remove an older backup.
"Create backup" in the menu writes a manifest and part files to the app's storage containing your whole journal (including photo locations, capture times and the list of deleted IDs) and the stored photo files, with any metadata they contain. When the app starts, it keeps the three newest backups it can verify as complete and deletes older ones; incomplete or unreadable backup attempts are kept, and if the list of imported backups cannot be read, no backups are deleted. "Restore / attach backup parts" copies the files you pick into the app's storage and merges them with your journal; imported backups are kept, although files from a restore that failed may later be deleted like older backups. HTML and PDF books include the trip title and dates, notes, weather, mood, place labels and photo locations with coordinates, expenses, photo file names, resized photos and a map of your pins with lines connecting them in date order. Books are saved in the app's storage; when the app starts, it keeps the files of the three most recent book creations and deletes older ones, and keeps only the three newest temporary book, print and resized-image files of each kind in the app's cache. Files are only sent when you tap "Share file" and choose a destination; copies may remain in the app's cache (including files picked for a restore) or wherever you saved or sent them.
Because we do not receive your journal, we cannot delete it for you; the controls above remove it from the app. For questions about data processed by Google, InMobi or Liftoff, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
- Liftoff Privacy Policy: https://liftoff.io/privacy-policy/
SECURITY
Your journal, photos, backups and books are kept in the app's private storage on your device, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Apart from the limited analytics events described above and files you choose to share, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partners uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app collects to what is described in this policy.
IMPORTANT NOTICE
Places, photo locations, capture times and photos you add can reveal where and when you have been. Backups, books and the original photo files in them may contain these locations, so check what a file includes before you share it, and only share photos you have the right to use. Expense totals use the exchange rates you enter.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com