The short version: MyDestinations has no accounts or logins, shows no ads, and does not run any server that receives your trips, photos, Traveler Information, or location. We don't sell your information. Your trips, itineraries, photos, and Traveler Information stay on your device. A few features use outside services — mapping services for destination lookup and maps, Expo for app updates, RevenueCat for the optional Premium purchase, and on Android, Google's ML Kit tools, which send Google diagnostic data — and exactly what each one receives is described below.
1. Who we are
MyDestinations is developed and published by NovaNexusVibe, an independent developer. You can reach us at NovaNexusVibe@gmail.com.
2. What we collect
We do not have accounts, logins, or any registration process, and we never ask for your name, email address, or phone number. We do not run any server that receives your trips, photos, Traveler Information, or location, and we do not run advertising or analytics services in the app. Apart from files you choose to send to someone yourself (section 8), the only data that leaves your device because of the app goes to the outside services described in sections 7, 9, 10, and 11. That includes the diagnostic and usage data that Google's ML Kit tools send to Google on Android (section 7).
3. Data stored on your device
MyDestinations stores the following data locally on your device. This data never leaves your device except where noted below, and is not accessible to us:
- Your trips, itineraries, stops, flights, transport, lodging, and notes
- Memories — an automatic archive of your completed trips, kept as a snapshot separate from your active trips
- Reduced-size preview copies of the photos you attach to plans (section 6)
- Pairing details for trips you share with a co-planner through Plan Together (section 8)
- Copies of any pictures you choose for your Home screen tiles
- Your app settings, preferences, and trip reminders
This data is deleted when you uninstall the app.
4. Traveler Information (encrypted, separately protected)
Traveler Information is an optional feature for storing passport-adjacent details — Known Traveler Number, embassy contacts, and similar traveler information. This data is stored using your device's secure hardware-backed storage (iOS Keychain / Android Keystore), encrypted at rest, and is never included in cloud backups or transferred to a new device automatically. It is protected by a PIN you choose and, optionally, Face ID, Touch ID, or fingerprint unlock — handled entirely by your device's operating system. MyDestinations never sees, stores, or transmits your biometric data or your PIN itself; only a salted hash of your PIN is kept, on-device, to verify it later.
5. Location
MyDestinations asks for your device's location, only while the app is in use, so the map you can open from a stop or lodging form can show places near you. Your location is held in memory only, is never stored persistently or sent to us, and its only destination is the Google Maps page shown inside the app, which receives it as a coordinate (section 9). You can decline location access and use the app's other features without it.
6. Camera, photos, notifications, and local network
The app asks for each of these only when you use the feature that needs it, and works without them:
- Camera — only to scan a Plan Together invite QR code from your co-planner's phone. The camera view is used live to read the code; no photo or video is taken or saved, and the microphone is never used.
- Photos — when you attach photos to a plan, you choose them in your device's photo picker, and the app reads only the photos you choose. It keeps a reduced-size preview copy of each one in its private storage on your device (and, on Android, remembers where the original sits in your gallery so it can open it for you). Photos are never uploaded, and they are not included in Plan Together updates, backups, or shared PDFs.
- Notifications — trip reminders are scheduled on your device itself. The app does not use a push-notification server and does not collect a notification token.
- Local network — used only for Plan Together's “Go Live” (section 8).
7. Auto-reader and itinerary import
Auto-reader fills in flights, stays, rental cars, and tickets from the screenshots, PDFs, or email text you choose. The reading happens on your device, and the app doesn't upload your pictures, PDFs, or text. They aren't saved with your trip; only the details you keep are. PDF pages are turned into temporary images in the app's private temporary storage, which is cleared automatically over time. The app reads your clipboard only when you tap Paste.
- iPhone and iPad — Apple's built-in text recognition and data detection and, on devices with Apple Intelligence, Apple's on-device AI model. Nothing is sent off your device.
- Android — Google's ML Kit tools on your device (text recognition and entity extraction, whose English language model is downloaded from Google once) and, on phones that have it, Google's on-device AI (Gemini Nano through AICore). The booking's text stays on your phone.
Diagnostic data on Android. ML Kit also sends Google diagnostic and usage data. According to Google's ML Kit disclosure, this covers device information (such as manufacturer, model, and OS version), the app's package name and version, identifiers for your installation (and, for on-device AI, user, device, or other identifiers), performance metrics, configuration details, input and output sizes, feature versions, event types such as model downloads, error codes, and configured languages. Google says this data is encrypted in transit and not transferred to third parties. That list does not include the text or pictures being read.
Itinerary import. Where your version of the app includes it, itinerary import reads PDFs, calendar files, and screenshots on your device in the same way, and works out places offline without an online lookup.
8. Plan Together, sharing, and backups
Plan Together has no server. Two phones exchange a trip in one of two ways:
- Go Live sends changes directly between the two phones over the Wi-Fi network they are both on. To find your co-planner's phone, your phone tries to connect to other addresses on that Wi-Fi network and keeps only the device that shows the matching pairing code. The invite QR code contains your phone's local network address and a pairing code, so whoever scans it can connect to you. Nothing passes through us.
- Invite and update files are created on your device and handed to your phone's share sheet; you choose the app and the person (for example WhatsApp, email, or Messages). We never see them. Once you send a file, it is held by that service and the recipient under their own policies, and a trip you share is copied onto your co-planner's device, where we cannot remove it.
A shared trip includes the trip itself (plans, notes, and dates) and the display name you chose to show your co-planner — not your photos or Traveler Information.
PDFs and backups. The itinerary PDF (Share) and the Memories PDF and backup file are built on your device and handed to the share sheet the same way. A backup file contains your Memories and the places you added by hand; if you have set up Traveler Information, those details go in only as an encrypted block that needs your Traveler Information PIN to open again. You decide where these files go, and we never receive them.
9. Destination lookup and maps (OpenStreetMap & Google)
Destination lookup. When you enter a destination's city and country — when you start a trip or add a past trip — MyDestinations sends that text (never your name, account, or device identifiers) to Nominatim, the OpenStreetMap project's public search service, to find the matching places and their coordinates. Nominatim is a community-run, third-party service. Standard web server logs kept by such services may include your device's IP address as part of normal request handling, which is outside our control.
Hotel-name lookup. When Auto-reader finds a stay's address but no readable name, and the name box is empty, the app sends that address to Nominatim to look for a hotel or other place there. Nothing else from the booking is sent.
Maps on the stop and lodging forms. From a stop or lodging form you can open a map. Depending on your choice, that is either the Google Maps website shown inside the app, or your phone's maps app. When it is shown inside the app, the page is loaded with the place name or address from that form as its search and, if you have allowed location access, your device's coordinates so it can show places near you; Google also receives whatever you then type or tap on that page. Google handles this under Google's Privacy Policy. Directions open in Google Maps or Apple Maps, governed by their policies.
The Memories map. The Memories map displays an OpenFreeMap vector map showing pins for your archived trips' destinations. It is drawn with the MapLibre library, which is loaded from the jsDelivr public content network, and its map tiles come from OpenFreeMap. Your device fetches these directly, so those services can see your device's IP address and which part of the map you view; your trips are not sent to them.
10. App updates
MyDestinations can receive small fixes without a new download from the app store. When the app starts, it asks Expo's update service (the service that hosts these updates) whether a newer version of the app's code is available, and downloads it if so. That request includes your device's operating system (iOS or Android), the app's version and release channel, and a random identifier generated for your installation — it is not derived from your device, your name, or any account, and it is not an advertising ID. As with any online request, Expo's servers also see your device's IP address. Your trips and other content are never part of this request. Expo handles this data under Expo's Privacy Policy.
11. Premium purchases
MyDestinations offers an optional one-time Premium purchase. The store (Apple's App Store or Google Play) handles the payment; we never see your card or payment details. To confirm that you own Premium, and to let you restore it on a new phone, the app uses RevenueCat, a third-party purchase service. RevenueCat receives your purchase history for this app (what you bought and when), an anonymous random ID it creates for your installation, and your device's locale and currency; as with any online service, its servers also see your device's IP address. Because MyDestinations has no accounts, this information is not linked to your name or to any account, and we do not use it to track you or for advertising. RevenueCat handles this data under RevenueCat's Privacy Policy.
12. Advertising and analytics
MyDestinations does not display ads, does not use advertising or tracking SDKs, and we do not collect analytics about how you use the app, such as which screens you open or what you tap. On Android, Google's ML Kit tools send Google their own diagnostic and usage data (section 7). Apart from those tools, the only built-in services that contact their own servers for purposes other than maps are Expo (app updates, section 10) and RevenueCat (purchases, section 11).
13. Your choices
- You can decline or later turn off any permission (location, camera, photos, notifications, local network) in your device's settings. The features that need it stop working, and the rest of the app keeps working.
- Your trips, photos, and settings are stored only on your device, so deleting the app removes them. Use Backup first if you want to keep your travel history.
- Because we hold none of your data on a server and there are no accounts, there is nothing for us to look up, change, or delete on your behalf. For purchase records held by RevenueCat, update requests handled by Expo, or ML Kit diagnostic data handled by Google, you can contact them directly or write to us and we will help you reach them.
14. Children’s privacy
MyDestinations is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided personal information through this app, please contact us and we will take appropriate action.
15. Changes to this policy
We may update this privacy policy from time to time. Any changes will be reflected here with an updated effective date. Continued use of the app after changes constitutes acceptance of the updated policy.
16. Contact us
If you have any questions about this privacy policy or how MyDestinations handles data, please contact us at NovaNexusVibe@gmail.com.