Jaunt Log does not require a Jaunt Log account and does not operate a central server that stores your personal location history, photos or journal notes. Your logbook is primarily stored on your device. Photos are analysed on-device where applicable, and an offline place catalogue is used so your coordinates do not need to be sent to a place-data provider to recognise a visit. This summary does not replace the details below.
1. Who we are
Jaunt Log is published by M-PAX Group. For privacy enquiries, contact [email protected].
Placeholder: replace with legal entity name and postal address before final publication if required for your jurisdiction.
2. Overview & scope
This policy describes how Jaunt Log handles information when you use the iOS app and when you visit this website. The app is local-first: core features work without a Jaunt Log backend. Some system services (e.g. map tiles, Apple platform services) may involve network requests as described below.
We do not make claims such as “we collect absolutely nothing” or “nothing ever leaves your device” unless that is literally true for every enabled feature. Where a feature may use the network, it is disclosed here and in the in-app Privacy screen, which should always be treated as the authoritative description for the shipped build.
3. Information Jaunt Log processes
Jaunt Log processes the following only to provide the features you choose to use:
| Category | Examples | Purpose |
|---|---|---|
| Visit & journal data | Places visited, dates, notes, favourites | Build your personal logbook; show progress and history |
| Location | Coordinates used to match visits | Recognise places, support arrival notices (if enabled) |
| Photo metadata | Date, location embedded in your photos (where available) | Rediscover past visits from your existing library (on-device, optional) |
| App data | Preferences, discovery history | Remember your settings and what has been discovered |
All of the above is primarily stored on your device. See §7 and §10.
4. Photos
If you grant Photo Library access, Jaunt Log can scan for photos that contain geographic information (date and location) to suggest past visits. Scanning is performed on-device via PhotoKit where applicable. Original photos remain in your Photos library; Jaunt Log does not need to upload your entire library to a Jaunt Log server to provide this feature, and it does not upload your images to a Jaunt Log server.
Jaunt Log uses only the minimum information necessary to associate a photo with a place — typically location and date/time. Access is optional. You can grant limited, full, or no access and change it anytime in Settings → Privacy & Security → Photos. If you deny access, photo-based rediscovery is unavailable; the rest of the app still works.
Manage permission: Apple — Control access to your photos.
5. Location
Location access is optional and used only to recognise places you visit and, if you enable them, to provide arrival notifications for places you choose to track. Jaunt Log is designed to recognise meaningful visits rather than maintain an unnecessary record of every movement.
Permission choices
- Never / Off — visits are not recognised automatically; manual logging and photo discovery still work.
- While Using the App (recommended) — recognised while you use Jaunt Log.
- Always — only needed for optional background arrival notifications when the app isn’t open; not always required.
Change anytime in Settings → Privacy & Security → Location Services → Jaunt Log. See Apple — Location controls.
6. Notifications
If you enable notifications, Jaunt Log may send local iOS notifications when you arrive at a place you’ve chosen. These are generated on your device and are not a mechanism for sending your location to a Jaunt Log server. Disable in Settings → Notifications → Jaunt Log.
7. On-device storage & offline catalogue
Your journal — visits, notes, favourites and progress — is stored locally on your device using SwiftData and a local spatial index (SQLite / R-Tree). No Jaunt Log backend is required for core use.
Jaunt Log includes a bundled offline catalogue of places and geographic boundaries (which may be derived from open/public datasets such as OpenStreetMap, Wikidata and UK government open geographic data). Matching a coordinate to a place happens on your device, so your location does not need to be sent to those data providers simply because Jaunt Log uses their public data.
Map imagery (MapKit tiles) and some place-detail links, if loaded, may require network requests to Apple or to the linked website. Those requests are governed by the respective provider’s privacy policy.
8. No account required
Jaunt Log does not require you to create a Jaunt Log account or social profile. There is no Jaunt Log-hosted profile containing your location history or photo library.
9. Third-party services & websites
Apple platform services
Jaunt Log uses Apple frameworks: PhotoKit, Core Location, MapKit and SwiftData. Their use is subject to Apple’s privacy policy and your device settings.
Place data sources
The offline catalogue may include data from:
- OpenStreetMap © OpenStreetMap contributors, ODbL
- Wikidata (CC0)
- UK government open geographic data (Open Government Licence where applicable)
We use plain text attribution and do not reproduce trademarked logos without permission. These datasets describe public geography; they do not receive your personal journey data.
Websites you choose to open
If you tap a link to an official place website, Jaunt Log opens it in Apple’s browser (SafariViewController). That site has its own privacy policy. Jaunt Log does not control third-party sites.
10. Data sharing
We do not sell your location history, photographs or journal to third parties and we do not build advertising profiles from your journeys.
We share data only as follows:
- On your device — processing stays local wherever possible.
- With service providers you interact with via the OS — e.g. Apple (MapKit tiles, PhotoKit, Core Location) as governed by Apple and your settings.
- With websites you explicitly choose to visit — subject to their policies.
- As required by law — if legally obliged.
11. Retention & deletion
Your logbook is retained on your device until you delete it:
- Delete a single visit, note or saved place in the app.
- Clear imported/discovered records in Settings.
- Delete all local Jaunt Log data via in-app Settings, or by deleting the app (which removes its local container on that device).
We cannot delete data from systems we do not control (e.g. a third-party website you visited). Have the final wording reviewed against the shipped build before publication.
12. Legal bases (UK / EEA)
Where UK GDPR / EU GDPR applies, we process on-device journal data to perform the contract (provide the app you requested) and on the basis of your consent where you grant optional permissions (Photos, Location, Notifications). You may withdraw consent by changing the permission in iOS Settings; this does not affect prior processing.
13. Children
Jaunt Log does not knowingly collect personal information from children for advertising or profiling and does not use location for ads. If a child uses the app on a family device, the same local-first protections apply. Guardians should use Apple’s Screen Time and Family Sharing controls. Ensure the App Store age rating is appropriate and have this section legally reviewed.
14. Your rights
Depending on your jurisdiction, you may have rights to access, correct, delete or restrict processing of your information, and to object or withdraw consent. Because your journal is primarily on your device, you can directly access and delete it in the app. To exercise other rights, contact [email protected].
UK users may also lodge a complaint with the Information Commissioner’s Office (ICO).
15. Security
We design Jaunt Log to minimise collection and to keep processing on-device. No method is 100% secure. We avoid claims such as “100% secure” and instead describe the actual measures: local storage, OS-controlled permissions, and use of Apple’s platform security.
16. Changes to this policy
We may update this policy to reflect app changes or legal requirements. The “Effective” date at the top will be updated and, where appropriate, we will note changes in release notes or in-app.
17. Contact
Questions or requests: [email protected]