Draft, written from how the app is built. Read it before it ships, and change anything that is not how you want to say it.
The short version
Traypass is made by Gonzalo Fuentes. It keeps what it needs to plan a trip with the people you invite, and nothing it can avoid. The files you add to a trip are encrypted on your iPhone before they leave it, with keys only the people on that trip hold. Nothing is sold, and nothing is used for advertising.
Your account
You sign in with Apple or Google through Firebase Authentication. Traypass keeps your user id, the name and the optional @username you choose, the photo you add, and the country you set off from. Sign in with Apple can hide your email from us; Google shares the address of the account you pick.
Your trips
A trip lives in Firebase Firestore, in the European region, and is shared with every member of that trip. The name of the trip, its dates and destinations, the name and address of every stay, the title and place of every plan, seats and booking references, and the titles of shared documents are sealed with a key that only the trip's members hold; the servers store them but cannot read them. The flight itself (number, airline, times, airports) stays readable so the server can watch it for cancellations and gate changes.
Your documents
Every file you add is encrypted on the phone (AES-256-GCM, with a Curve25519 identity kept in your iCloud Keychain) and stored as an opaque envelope on our own server. We cannot open it. A document shared with a trip can be opened by its members once one of them lets a newcomer in; a personal document can be opened only by you. Deleting a document deletes the envelope.
Packing and the wardrobe
The wardrobe you describe, and how you adjust the lists the app proposes, are kept with your account so the next list starts as yours. When you ask for suggestions, the request sent to our server and on to the model provider (OpenAI) carries the trip's shape (destinations, dates, climate, the list's categories) and no names, no free text and no itinerary.
Suggested plans
A suggested day is built from a corpus of public places (Wikivoyage) and the trip's own anchors: where you sleep and when your flights land. The model picks from that list and writes the words; it does not receive your name, your documents or your messages.
What the servers see
- Weather comes from Apple's WeatherKit, asked for by place and date.
- Cover photographs come from Unsplash, chosen by the name of the place.
- Flight status comes from AeroDataBox, asked for by flight number and date.
- Exchange rates come from the European Central Bank and exchangerate-api.com.
- Notifications are sent through Apple's push service to the phones registered on your account. The server writes the sentence; a name in it is sealed and filled in on your phone.
- Purchases are handled by Apple and RevenueCat. We never see a card number.
- This website uses Vercel Analytics, which does not use cookies and does not identify you.
What is never collected
No advertising identifiers, no contacts, no location in the background. Bookings you share into the app from your mail or Wallet are read on the phone, with Apple Intelligence, and are not sent anywhere to be read.
Deleting your account
Settings, then Delete account, erases your profile, your wardrobe, your personal lists and your documents, removes you from every trip, deletes the trips you created and asks Apple to revoke its sign-in. Nothing is kept afterwards apart from what the law requires of a purchase receipt.
Questions
Write to [SUPPORT EMAIL].