Privacy
This is an unreviewed draft. It describes what the app actually does today, written from the source, but it has had no legal review and the App Store requires a policy that has. Every highlighted passage is a decision nobody has made yet.
Odyse holds your travel plans. That is a more personal thing than it sounds — where you'll be, when, and who with — so this page is specific rather than reassuring.
Who we are
Odyse is made by Vonoverse — legal entity name, registered address and jurisdiction to confirm. Questions about this policy go to support@odyse.app.
Signing in
Odyse uses Sign in with Apple or Sign in with Google, and nothing else. There is no password, because the app never handles one. The provider gives us the name and email address on the account you sign in with — if you use Apple's private relay address, that relay is all we ever see.
What you put in, and what we store
Your account holds the things you create in the app:
- Trips, days, activities, accommodation, transport and bookings.
- Expenses and budgets, including how they're split with other travellers.
- Packing lists and phrase sheets.
- Travel documents you upload, and receipt or boarding-pass images you scan.
- Your conversations with the planning assistant, and the notes it keeps about a trip so it doesn't ask you the same thing twice.
- Profile details you set: your name, home city, home currency and travel preferences.
- Your Oddies balance, and a statement of every top-up and every AI request that spent them.
Files — receipts, scans, profile photos — are stored separately from the rest and are readable only by your account, and by people you've shared a trip with where the file belongs to that trip.
Where it's stored
On managed PostgreSQL provided by Supabase, hosted in Singapore. Your device also keeps a full local copy so the app works with no signal; that copy lives in the app's own storage and is removed when you delete the app.
The AI features
Odyse plans in two places, and nothing goes to the cloud until you say so. The first time you sign in, the app asks whether it may use cloud AI; the answer is kept on your account and can be changed any time under Settings → Privacy.
- On your device. Apple's on-device model. Nothing leaves the phone, and these features work in airplane mode. This is what runs if you decline cloud AI, and whenever you're offline. Planning a whole trip in one go needs the cloud.
- In the cloud. Your request goes to our server, which passes it to Anthropic, whose Claude models write the answer. What's sent is what each request needs: what you write in the chats; the trip it's about — places, dates, bookings and notes; receipts and bookings you ask it to read; and your location, when you ask about where you are.
A chat about a trip runs as a session on Anthropic's servers for as long as the chat is open, so the conversation can continue without being re-sent each time. We delete that session when you clear the chat, delete the trip, or delete your account; a daily job does the deleting, so it is gone within a day. Our own server keeps a copy of each reply for up to an hour, only so a reply lost to a dropped connection can be delivered without being paid for twice, and keeps the conversation and what each message cost in the statement behind your Oddies balance.
Anthropic's retention terms for API and Managed Agents traffic need stating precisely here, from their current data processing terms — confirm before this goes live. Your trip content is not used to train any model.
Location, maps and weather
If you allow it, Odyse uses your location to suggest what's nearby and to re-plan around where you actually are. Forecasts come from Apple's WeatherKit and place search from Apple Maps; those requests are handled by Apple under Apple's own privacy terms, and Apple does not receive your Odyse account with them.
Photos of a place, and its opening hours, come from Google Maps. When you open a place, or the planner checks that a restaurant is open, our server sends Google the place's name and position — never your account or your location — and shows you what comes back. Nothing from Google is stored except the place's Google identifier, so the same place isn't searched for twice.
Sharing a trip
A trip is private until you open it for sharing. Once you do, people holding the invite link can join it and see the trip's shared content. Expenses you mark private, your own packing list and your travel documents stay yours and are not visible to them.
Payments
Cloud AI is paid for in Oddies, bought as in-app packs. Purchases are handled entirely by Apple: we never see your card details. Apple sends us a signed record of each pack you buy, and of any refund, which is what credits or removes the Oddies on your account. There is no subscription.
Analytics
Odyse sends usage analytics to Google Analytics, through Firebase, so we can see which parts of the app get used and where people give up. It is anonymous: events carry no account, name or trip content. It is on by default and switched off under Settings → Privacy → Share usage analytics; switching it off also discards the identifier this install had been counted under, so switching it back on later starts over as a new visitor. Whether the EU and UK launch needs this to be asked before it runs, rather than on by default, is on the legal review list.
Crash reports are off unless you turn them on, under Settings → Privacy → Crash reports. With the switch on, a crash sends Firebase Crashlytics what crashed — the stack trace, the app version, and your device's model and system version — so we can fix it. A report never carries your account, your trips, or anything you typed, and switching it off stops the next one from being sent.
Deleting things
Deleting a trip, an expense or a document removes it from every device you're signed in on immediately, and takes any AI session about that trip with it.
Deleting your account, under Profile → Account, hides it at once and erases it 30 days later. In those 30 days, signing in again restores it exactly as it was; after them, a daily job deletes your uploaded files, your AI sessions at Anthropic, and then every row of your account, and nothing can bring it back.
If you signed in with Apple, deleting your account also tells Apple to revoke that sign-in: you confirm with Apple once more as you delete, and the next time you use Sign in with Apple with Odyse it starts as a first sign-in. Odyse keeps no Apple token before or after.
Two things stay, because other people's trips depend on them: an expense you logged on a trip you shared with someone else stays on that trip, re-assigned to the trip's owner with your receipt removed, so their balances still add up; and your name stays on that trip's list of participants, no longer linked to any account.
Your rights
You can ask for a copy of your data, ask us to correct it, or ask us to erase it, by writing to support@odyse.app. Depending on the jurisdiction we register in, this section needs the GDPR lawful-basis table, the response deadline, and the supervisory-authority complaint route.
Children
Odyse isn't intended for children under age threshold to confirm — it follows from the App Store age rating and the jurisdiction, and we don't knowingly collect their information.
Changes
If this policy changes in a way that affects what we do with what you've already given us, we'll say so in the app rather than only here.