Travel Log Privacy Policy
Effective date: 21 May 2026 · Last updated: 1 November 2026
Short version. Travel Log builds a journal of your trips using location, photo and optional calendar data on your device. Your travel history is not sent to the developer, and nothing is sent to a server controlled by us. Some features contact Apple services directly. If you turn on iCloud sync, your data syncs through your own iCloud account (we cannot see it). The app contains no analytics, advertising, tracking or third-party network SDK; the only non-Apple code it bundles is an offline geospatial library that never contacts a server. During TestFlight testing and App Store distribution, Apple may provide the developer with limited installation, usage, crash and feedback information, as explained below.
1. Who publishes this app?
Konstantinos Fragkoulis (referred to in this policy as "we", "us", or "the developer"), the independent publisher of the Travel Log iOS application. You can reach the developer at travellog@kfragkoulis.com.
The developer operates no server, database or analytics pipeline that receives your travel history. We may receive information that you choose to send by email or through TestFlight feedback, along with limited distribution and diagnostic information that Apple provides through TestFlight or App Store Connect. This policy describes both that limited information and the data handled inside the app so that you can make an informed decision before granting permissions.
2. What data does Travel Log handle on your device?
- Location. With Always location permission, Travel Log monitors iOS Significant Location Change events and system-detected visits in the background. These provide occasional readings after meaningful movement and observations of arrivals and departures; the app does not run continuous GPS tracking in the background. While the app is active on screen, it can use a continuous stream of higher-frequency location updates with When In Use or Always permission. It filters these updates before storing them and stops the stream when the app becomes inactive. Precise Location, Low Power Mode and device temperature affect whether the stream can run; when it cannot provide a suitable reading, the app may request a single location reading instead. Accepted readings can include coordinates, time, horizontal accuracy and, when available, altitude and vertical accuracy. Visit records include coordinates, accuracy, arrival time, departure time when available, and the time the observation was received. Readings and visits are stored locally and used to build stays and trips; they can also sync through your private iCloud account if you enable sync. You can change location access in iOS Settings.
- Photo data, only for photos you have authorised the app to read. When you opt into the Photo Library Import feature, or when you browse a trip's photos, the app reads the creation date and location made available by Photos so that it can match the photo to a trip and display it inside the app. The app does not upload, modify or delete your photos. If a photo is stored in iCloud Photos rather than on the device, iOS may download it from Apple so that the app can show it. A photo leaves the app only when you choose to share it through the system share sheet. Photos you hide or pin in a trip are remembered by their photo identifiers, which sync with your trips when iCloud sync is on.
- Calendar data (optional). If you grant Calendar access, Travel Log reads event titles, dates, locations, notes and basic calendar information to show possible upcoming trips, help classify past trips and confirm flights. Calendar events are not used to name past trips. Notes are inspected in memory for relevant signals but are not saved. Event titles, dates and locations, together with derived planned-trip information, may be stored on your device and in your iCloud when sync is enabled. The app never creates, edits or deletes calendar events. iOS calls this "Full Access" because it does not offer a read-only calendar permission.
- Place names and place search. Coordinates are translated into human-readable city / country names primarily by a geographic database bundled inside the app (built from open datasets such as GeoNames, OpenStreetMap and Natural Earth, credited in Settings → About). These lookups happen entirely on your device. When the offline database has no useful answer, the app can send a coordinate directly to Apple's MapKit service. Place searches and the optional Calendar feature may also send search text or calendar location text directly to MapKit so that Apple can resolve it to a place. When you pick a place for a temporary home, the app sends its coordinate to MapKit to look up that place's time zone. Maps in the app are drawn by MapKit, which loads map data from Apple for the area shown and can show your current location on the map. We do not see these requests or the responses, and Apple's privacy policy applies to them.
- Weather for stays and planned trips. The app uses Apple's WeatherKit service for historical weather on stays and forecasts for upcoming trips detected from your calendar. Your device sends the relevant coordinates and dates directly to Apple; the developer never sees these requests. The returned weather is stored on your device (and in your iCloud, if sync is on). Apple's privacy policy applies to the lookup.
- On-device AI output. When available, Apple's Foundation Models framework (Apple Intelligence) helps assess possible calendar trips. Model inference runs on your device; the app does not send prompts to a remote AI service. The model's answers are stored locally. Upcoming trips it helps find are kept like other planned trips and can be included in private iCloud sync or files you choose to export. Annual year-in-review narratives use predefined text based on your travel statistics.
- Your "Home", home area and Routine places. Travel Log stores the home coordinates and dates you enter, routine-place coordinates and radii, learned home-area places and any corrections you make. It uses these to distinguish ordinary life from travel.
- Files you choose to import or export. You can import Travel Log backups, GPX files and supported Google Timeline exports. The selected file is read on your device and used to create travel data. Exported Travel Log files can contain sensitive trip, home and location information, including visit arrival and departure times. Files are saved wherever you choose in the system share sheet. When you export a backup you can optionally protect it with a password: the backup is then encrypted on your device (AES-GCM, with a key derived from your password) before it is saved, and the app asks for the password when you import it. The password is never stored, logged, synced or sent anywhere, so a forgotten password cannot be recovered. Backups exported without a password, and other files you export or share, are not encrypted by Travel Log.
- Trips you choose to share. You can share selected trips through the system share sheet as a picture of the trip, a Travel Log trip file and, optionally, a GPX route. Before anything is shared, the app leaves out every location reading and stay inside your home areas, and it never writes your home location or distance from home into the file. The trip file contains the trip's titles, dates, countries, stays, location readings and visit times, and a sender name only if you enter one. The trip picture is drawn on your device, with a map that MapKit loads from Apple. The app does not send shared trips to the developer or to any server; they reach only the people and apps you pick in the share sheet, and the recipient can see everything the file contains. When someone shares a trip with you, the file is read on your device, and the trip is added to your journal only if you choose to import it.
- System features. Travel Log can make trip titles, dates and place names available to iOS Spotlight, Siri and Shortcuts. Its widgets read selected trip and statistics data from the app's shared private container. If you allow notifications, notification text may include trip, country, homecoming or yearly-memory information.
3. What data does the developer collect?
The app itself sends no travel data to the developer. It contains no analytics, telemetry, advertising SDK or crash-reporting SDK, and the developer has no infrastructure that receives data from your installation.
Apple may nevertheless provide the developer with limited information through the services used to distribute the app:
- TestFlight. During beta testing, Apple automatically shares installation status, app and build version, device model and identifier, OS version, language, session counts, crashes and crash logs with the developer. If you submit TestFlight feedback, the developer also receives your comments, screenshots and related diagnostic details. Joining through a public link does not by itself reveal your name or email address to the developer. See Apple's TestFlight & Privacy notice.
- App Store Connect. Apple provides privacy-protected information such as downloads, installations, sessions and stability metrics. Some usage and diagnostic information is available only from users who have agreed to share it with developers, and Apple applies aggregation and privacy thresholds. See Apple's App Store Connect Analytics documentation.
- Information you send us. If you email the developer or submit feedback, we receive the address and content you choose to provide.
Apple's standard distribution and diagnostic information does not give the developer your Travel Log database, location history, photos, calendar contents or AI prompts. Information that you intentionally include in feedback, an attachment or a screenshot may contain details from the app. The information is used only to respond to you, investigate problems and improve the app. It is not sold, used for advertising or combined into a profile of your travels.
4. Where does the data live?
- On your device, in the app's sandboxed SwiftData store and supporting private files and settings. Travel Log's widgets use the same private app-group container. Trip information donated to Spotlight, Siri or Shortcuts is stored and managed by iOS.
- If you enable iCloud sync in Settings, app data syncs through your own iCloud account to your other Apple devices using a CloudKit private database. Apple states that a private CloudKit database is available only to its user by default and is not visible in the developer portal. See Apple's iCloud privacy policy for how Apple itself handles iCloud data.
- Independently of the iCloud sync setting, a small number of preferences are kept in your own iCloud key-value storage whenever your device is signed in to iCloud, so they match across your devices: which trips you pinned (as trip identifiers), the countries you mark as visited, your temperature unit, and records of imported files (a file fingerprint, a random device identifier and the date) that let the app warn you before you import the same backup again. They contain no locations or stays. Signed out of iCloud, they stay on the device.
- Files you export or trips you share live in the location you select or with the people you send them to, outside Travel Log's control. Deleting data from the app does not delete copies that you exported or shared.
5. Third parties
There are no advertising networks, analytics providers or non-Apple network SDKs in the app; the only non-Apple code bundled is an open-source geospatial indexing library (H3) that runs entirely on the device and never contacts a server. The external services used by Travel Log are Apple's own: MapKit (maps, place search, geocoding and time-zone lookups), WeatherKit (weather for stays and planned trips), iCloud Photos (downloads of photos you view), CloudKit (optional sync of your travel history), iCloud key-value storage (a few preferences, kept independently of the sync setting whenever you are signed in to iCloud), and Apple Push Notification Service (so that CloudKit can notify your devices of changes). Photos, Calendar, Spotlight, Siri, Shortcuts, widgets and local notifications are accessed through Apple's system frameworks. TestFlight and the App Store are separate Apple distribution services. Apple's privacy policy and the settings of your Apple Account and device govern Apple's handling of data.
6. Children
The app is not directed at children under 13 (or the equivalent age of digital consent in your jurisdiction), and the developer does not knowingly collect personal data from children. If a child uses the app, its on-device processing works in the same way described in this policy. You can delete the app and, if iCloud sync was used, clear its data from iCloud storage in iOS Settings. Contact the developer if a child sent information by email or through feedback and you want that information deleted.
7. How long is data kept?
Indefinitely on your device until you delete it. You can:
- Delete individual trips or stays from inside the app.
- Delete all travel data from Settings → "Delete All Data." This erases trips, stays, location readings, recorded arrivals and departures, map visits, photo references (including hidden and pinned photos), planned trips, yearly memories and home-area corrections. It also clears delivered and scheduled notifications and notification history, the countries you marked as visited, dismissed suggestions and the Spotlight index, removes the app's saved caches and asks iOS to refresh the widgets. Your homes, temporary homes and routine places, app settings and permission choices are kept, and so are pinned-trip marks and import records in your iCloud preferences, because your other devices share them. With iCloud sync on, the deletions sync to your other devices. With sync off, copies already in your iCloud are not deleted; you can delete them in iOS Settings under iCloud storage. The cleared preferences above sync through iCloud whenever you are signed in, whatever the sync setting. Exported files and anything you shared are not affected. New travel data can be recorded while location access remains enabled.
- Delete only the photo-import data from Settings → "Delete imported data." This removes everything that was created by the photo-library backfill.
- Delete Calendar-derived data from Settings → "Delete Calendar Data." This removes detected upcoming trips and clears generated trip titles and related calendar caches so they can be rebuilt without calendar context after access is disabled.
- Delete the app from your device, which removes the local store. If iCloud sync was on, the data in iCloud remains until you also remove it from your iCloud storage (iOS Settings → Apple Account → iCloud → Manage Storage → Travel Log → Delete Data).
- Delete exported copies yourself. Files that you saved or shared outside the app are not controlled by Travel Log and are not removed by its deletion tools.
Emails, feedback and diagnostic information retained by the developer are kept only as long as reasonably necessary to respond, investigate the issue and improve the app. TestFlight and App Store information is made available through Apple's systems and is also subject to Apple's retention rules and controls. You may contact the developer to request deletion of a message or feedback that we can identify.
8. Your rights
Your travel database is held on your device and, if enabled, in your private iCloud storage, so the in-app tools above are the direct way to access, correct, export or delete it. For limited information that the developer may receive through email, TestFlight or App Store distribution, you can contact us using the address below. The following rights apply where the relevant law covers your request:
European Economic Area, United Kingdom, Switzerland (GDPR & UK GDPR)
Under Articles 15–22 of the GDPR, you may have rights to access, rectify, erase, restrict or object to processing, receive portable data, withdraw consent, and receive protections concerning automated decisions. You can exercise these rights for your travel history through the app's data-management features and your device's iCloud controls. Contact us for identifiable information that you sent to the developer. You also have the right to lodge a complaint with your national data-protection supervisory authority.
California (CCPA / CPRA)
California residents may have rights to know, delete, correct, and limit certain uses of their personal information, and to opt out of any "sale" or "sharing" of personal information. We do not sell or share personal information for cross-context behavioural advertising. The in-app tools cover your travel data, and you can contact us about identifiable information that you sent to the developer.
For any rights request that the in-app controls do not satisfy, please write to travellog@kfragkoulis.com.
9. International users
Your travel database does not transfer to the developer. iCloud, MapKit, WeatherKit, TestFlight and App Store distribution use Apple's infrastructure under Apple's terms and privacy policy. If you contact the developer directly, your message may be processed in Greece and by the communication service you choose.
10. Security
On-device data is stored in sandboxed app and app-group containers and is protected by iOS device security and Data Protection. Data in the CloudKit private database is not visible in the developer portal. Apple states that third-party app data in iCloud is encrypted in transit and on Apple's servers, and that CloudKit encrypted fields and assets are end-to-end encrypted when Advanced Data Protection is enabled. The developer holds no keys or copies of your travel database. A backup you protect with a password is encrypted on your device before it is saved, and only that password opens it. Other exported files, including backups exported without a password, are protected only by the destination and sharing method you choose, so you should treat them as sensitive.
11. Changes to this policy
If this policy is updated, the "Last updated" date at the top of the page will change. Material changes, such as introducing collection of travel data by the developer, will also be communicated through the app or its distribution page when appropriate or legally required.
12. Contact
For any privacy-related question, please write to travellog@kfragkoulis.com. We will reply within a reasonable time. If your request concerns your statutory rights under GDPR or CCPA, please include enough context for the request type to be identified.