Privacy Policy
Effective 18 July 2026
The short version: Worldward stores your travel data on your device. It has no cloud server, no accounts, no analytics, no ads and no third-party SDKs. I never see your data — and I couldn't if I wanted to.
Who I am
Worldward is developed by Smigi, an independent developer. The app is open source under the Mozilla Public License 2.0 — you can inspect everything it does at github.com/lakafior/Worldward.
What data the app handles, and where it stays
Everything you enter in Worldward — country statuses, visits, notes, trips, itineraries, packing lists and wishlist — is stored locally on your device using Apple's SwiftData framework. Worldward has no backend and makes no network calls of its own.
iCloud sync
If you use iCloud sync (when available), your travel data is stored in your private iCloud database using Apple's CloudKit. That data is tied to your Apple Account, protected by Apple, and accessible only to you and your devices. The developer has no ability to read, access or recover it. Apple's handling of iCloud data is described in Apple's Privacy Policy.
Photos
The optional photo import scans your photo library on-device to detect countries from the location and date of geotagged photos. When you attach photos to a visit, Worldward stores only a photo identifier and fetches the image from your library when displayed — it never copies, uploads or transmits your photos. Access requires your explicit permission and can be revoked at any time in Settings.
Location
The optional “Mark where I am” feature uses your location once, on-device, to determine which country you're in. Your location is not stored (only the resulting country status is) and is never transmitted. Access requires your explicit permission.
Calendar
“Add to Apple Calendar” uses write-only calendar access: the app can add a trip event you asked for, and cannot read any of your existing events.
The optional “Sync Trips with Apple Calendar” setting mirrors your trips to a dedicated “Worldward” calendar it creates — one event spanning each trip plus one per dated stop — and keeps them updated as you edit the itinerary. Keeping events updated requires full calendar access (Apple has no narrower permission that allows updating events later), but Worldward only ever creates, updates or removes events in its own “Worldward” calendar; it never reads, uses or modifies events in your other calendars. Everything happens on-device through Apple's EventKit framework. The feature is opt-in and off by default; turning it off removes the Worldward calendar and its events, while your trips stay in the app.
Notifications
Travel reminders are optional, off by default, and scheduled locally on your device. No notification content passes through any server.
Reminders
The optional reminders sync connects your packing list items to the system Reminders app. When enabled, you can choose which checklist items appear as actionable reminders — useful for last-minute errands or gear you need to buy ahead of a trip. Changes are reflected both ways and remain entirely on-device via Apple's Reminders framework. This feature is opt-in and controlled per packing list item.
On-device AI
Travel Chat, year recaps and destination suggestions run through Apple Intelligence (Apple's Foundation Models framework) entirely on your device. Your travel data is not sent to any cloud AI service.
Local automation (MCP)
The macOS app can run an optional local server that lets an AI assistant running on your Mac read your travels and, if you allow it, plan trips into Worldward on your behalf. This is the Model Context Protocol (MCP), the open standard used by coding assistants and desktop AI apps.
The server is off by default, and when you turn it on it is deliberately locked down:
- Loopback only — it listens on 127.0.0.1 and cannot be reached from the network, however your Mac is configured.
- Token-protected — each install generates its own random access token, which you can reset at any time to disconnect every client at once.
- Origin-checked — requests that carry a non-local Origin header are rejected, so a web page can't drive the app.
- Read-only option — turn off “Allow Changes” and the server answers read requests only.
Worldward never dials out: this is a listener, and nothing is sent anywhere unless a client on your own Mac connects to it. Whatever you connect can see the data you ask it about, so the feature stays off unless you're using it. The server holds no history and keeps no connection state after a request completes.
Apple system services
Like any app showing an Apple Map, Worldward displays map tiles that your device fetches from Apple. These requests are made by the operating system's MapKit framework and are governed by Apple's Privacy Policy; they do not include your travel data.
Analytics and tracking
None. Worldward contains no analytics, no advertising, no tracking and no third-party code. The App Store's own, opt-in developer analytics (crash reports and aggregate statistics Apple shares with developers) are controlled by you in your device's privacy settings.
Your data, your control
- Export — Settings offers a full JSON backup and a CSV export of your travel data at any time.
- Share — sharing a trip (as Markdown, a PDF or a .wwtrip trip file) creates a copy of that trip's data — including any files you attached to it — only when you ask, and hands it to the system share sheet. Where it goes (AirDrop, Messages, Mail…) is entirely your choice; nothing is ever shared automatically, and the transport is handled by Apple's system services, not by Worldward.
- Delete — deleting the app deletes all locally stored data. If iCloud sync is enabled, you can remove the app's iCloud data in system settings under your Apple Account's iCloud storage management.
Children
Worldward does not collect personal data from anyone, including children, and contains no third-party content, purchases or ads.
Changes to this policy
If a future version of the app changes how data is handled (for example, new sync options), this policy will be updated before that version ships, with the effective date above revised. The history of this page is public in the project repository.
Contact
Questions or concerns? Open an issue at github.com/lakafior/Worldward/issues or email worldward@smigi.net.