The Travel Binder is a fully local app. Your trips, flights, hotels, bookings, confirmation codes, places, packing lists, checklists, notes and documents are stored only on your device, in a database no one else can reach. There is no account, no login, no server and no cloud sync. We cannot see, access, or recover your data — including if you lose the device.
When you attach a photo or a PDF — a passport scan, an insurance certificate, a rail pass, a booking confirmation — the app opens your camera or file picker only at the moment you choose the file. The file is then copied into the app’s own storage on your device. Attachments are never uploaded, scanned, or read by us.
Your pins are coordinates saved in your own trip and drawn by the app, so they appear correctly with no connection at all. Background map imagery is different: those tiles come from your device’s map provider — Apple Maps on iOS, Google Maps on Android — and fetching them requires a connection to that provider, governed by their privacy policy rather than this one. Your device keeps tiles for areas you have already viewed, which is why a map you looked at while planning still works abroad in airplane mode.
Searching for a place by name likewise sends that search text to the provider. Typing coordinates directly, or pasting a map link, is handled entirely on your device and sends nothing.
Neither request carries anything about your trip. The provider sees a map area or a single search term — never your itinerary, your bookings, or your other pins.
The Atlas, the route diagram on a finished trip, and every share card are drawn by the app from your own data with no map imagery whatsoever, so nothing you share is ever assembled by, or routed through, a map provider.
If you tap Directions, a single destination is handed to your own maps app and you leave The Travel Binder entirely. From that point onward that app’s privacy policy applies rather than this one.
The app does not ask for location permission, does not use your device’s location, and does not record your movements.
Checklist due dates and trip-day reminders are scheduled locally by your device. Nothing about a reminder is sent to any server. You can decline the notification permission, or revoke it later in your system settings, and the rest of the app carries on working.
Exporting your trip — as PDF, Markdown, JSON, CSV or a trip bundle — produces a file that is handed to whichever app or destination you pick from your device’s share sheet. Where that file then goes, and who can read it, is entirely your decision. We never receive a copy.
Share cards are images you generate and send yourself. Because a booking reference on a public post is a genuine leak, confirmation codes are replaced with dots on every share card by default, and costs are left off unless you deliberately switch them on.
The Travel Binder uses Firebase Crashlytics to collect anonymous crash diagnostics: device model, operating system version, and the technical state of the app at the moment it failed. No personal information, trip data, documents, photos, or coordinates are ever included. Crash reports exist solely so we can find and fix defects.
We do not use any analytics SDK and do not track how you use the app.
The free version shows a single banner advertisement, and only on the trips list — never inside a trip, and never over your itinerary. It is served by Google AdMob, which may collect device identifiers to serve ads. In regions where consent is required (the EEA, UK and Switzerland) you will be asked for your choices before any ad is requested, and you can change them at any time from Settings → Manage Ad Consent. Buying the one-time unlock removes advertising entirely.
The one-time unlock is processed by Google Play or the Apple App Store. We never see or handle your payment details.
Everything in the app is yours. You can export it in open formats at any time, and deleting the app removes every trip, document and photo it held from your device. There is no central copy to request, correct, or erase, because one was never made.
If this policy changes, the revised version will appear on this page with a new date, and the copy inside the app will be updated to match.
Questions about this policy are welcome at admin@eritech.studio.