What the app stores, what it shares, and what it never does.
This policy describes what WhenWeGo does with data. It is written from the app's actual behaviour and is kept short on purpose.
Trips, participants and plan data are stored on your devices and in iCloud using Apple's CloudKit: a trip you organize lives in your private iCloud database; when you share it, its contents are placed in a shared CloudKit zone that the people you invite can read (and, with edit access, change). Your exact budget figure is stored only in your private iCloud database and only published to the shared trip if you choose to share it. WhenWeGo has no server of its own and the developer cannot access your trips.
On a shared trip, everyone with access sees: trip name, dates, destinations, proposals and votes, stays, travel legs, itinerary items, shared expenses, and for each participant their name, departure city and airports, interests, free and blocked date ranges, flexibility, travel-time and connection limits, accessibility notes, lodging preference and budget level (1–5). Share trips with people you trust: iCloud sharing grants read or read-write access to the whole trip, and the app's finer rules (who may edit what) are enforced by the app, not by the server.
To compute typical weather, WhenWeGo sends a selected destination's coordinates and historical full-month date ranges to Open-Meteo (archive-api.open-meteo.com). These requests reveal the month being compared, but do not send your name, exact future trip days, budget or device location. Open-Meteo's free-service policy says it may collect IP addresses for technical maintenance and misuse prevention, and keeps troubleshooting logs that may contain geographical coordinates for up to 90 days. The provider states that this information is not linked to user identities and is not shared with third parties. WhenWeGo also requests a fixed current euro rate table from Frankfurter (api.frankfurter.dev), whose hosted-service policy states that it does not retain individual request/IP/URL logs. Place search uses Apple Maps (MapKit); invitation and sync traffic uses Apple's iCloud. See Open-Meteo's policy and Frankfurter's policy.
The optional assistant runs on your device with Apple's Foundation Models (Apple Intelligence). No prompt or trip data is sent to WhenWeGo or to any AI provider.
WhenWeGo has no developer-operated server, analytics, advertising or tracking code. The weather provider's retained request context and technical data are disclosed in the App Store privacy label as Other User Content and Other Diagnostic Data for App Functionality. The label conservatively marks these as linked to you because we cannot verify anonymization before collection; this does not mean that the developer receives your trips or that the provider claims to identify you. Neither category is used for tracking. If you email support, the developer receives your email and message and uses them to help you.
WhenWeGo asks for no device permissions beyond iCloud (used for storage and sharing). It does not access your calendar, contacts, photos or location.
Delete a trip you organize to remove it for everyone (Trip settings → Delete trip); this also deletes your private budget figure for it. Leave a trip you were invited to from Trip settings (Manage or leave this trip): your access ends and, once you confirm, the private budget figure you entered for that trip is deleted from your iCloud. Your participant entry (name, dates, stays, travel) remains in the organizer's trip until the organizer removes it under People. Deleting the app removes its local data; iCloud data is removed when you delete your trips or manage WhenWeGo's data in iOS Settings → Apple Account → iCloud.
WhenWeGo is not directed at children under 13 and is rated for general audiences.
This policy is updated when the app's data practices change; the date at the bottom of the page is the current version.
Questions about privacy or a request about your data: jago.naeher@gmail.com. The app is published by Jakob Näher (Apple Developer Program), who is responsible for this policy.