Effective 14 November 2026. Version 19.
Odyssey is a trip planner you share with the people you travel with. A trip says where you will be, when, and with whom, so this page tells you where that information goes and who can see it.
Odyssey is run by Venkata Bommireddipalli, an individual in Australia, who is responsible for your information. Questions, requests and complaints: support@vbi.dev.
Your account. When you sign in with Google, Google tells us your name, email address, profile photo and an account id. When you sign in with Apple, Apple tells us an account id and your email address, or a private relay address if you chose to hide it, and your name the first time you sign in. Your name and photo are copied onto each trip you join so the other members can see who is who. If we have no name for you, we use the part of your email address before the @, or "Traveller" if that address is a private relay one, and it is shown wherever your name is. If you sign in with Apple using the same email address as your Google account, both sign in to the same Odyssey account. If you ask us for access by email, we keep the email address you give us, so that you can create trips and connect an AI app as soon as you sign in with it, whether or not you have signed in yet.
Your trips. Everything you and the other members add: the trip's name, dates and description; days, stops and stays with their names, addresses, map positions, dates and notes; journeys with carriers, times, booking references, seats and notes; expenses, how they are split, and the names of anyone added to the budget, including people who do not use Odyssey; photos and files.
Photos and files as you upload them. We store the original file and its details, such as the camera model and when a photo was taken, and for a document in a trip's Files a small preview of it (the first page of a PDF, or a smaller copy of a photo), stored with it. Deleting the document normally deletes its preview too, though one can remain if the delete is interrupted or made from an older version of the app; deleting the trip always removes it. Before a photo or PDF leaves your device, we remove the GPS location the camera recorded in it, wherever we can read it. A place name written into a photo's details, or a location you type yourself, is kept, and anyone who can open the file can read what remains.
Your conversations with Hermes. What you write to Hermes, its replies, the changes it proposed and made, facts Hermes saves to remember in that conversation (it can save these without asking; you can see and delete them in the chat), and the files you attach: photos, PDFs, emails and spreadsheets. A photo or PDF you attach is also listed in the trip's Files.
Your settings. Which kinds of change Hermes may make without asking, the finishing chime, which page the app opens to, and which of our in-app announcements you have already seen, so each shows once.
Apps you connect. If you connect an AI app such as Claude or ChatGPT to Odyssey, we record when you connected it, the id WorkOS gives your account, when you last disconnected your apps, and how many requests the app makes each day and each minute.
Purchases. If you buy Odyssey Pro or a Trip Pass, we record your plan's status and renewal date, the ids Stripe gives your account and your purchases, the checkout you have open, and for a Trip Pass which trip it is for, what was paid and who bought it. Stripe takes the payment; we never see your card. If you are given a free-year code, we record which code, tied to a scrambled form of your Google or Apple sign-in id rather than to your account.
On your device. Odyssey keeps:
Your location, only if you ask. If you switch on "show my location", your position is used on your device to draw it on the map. We do not store it or send it to our servers. The map then zooms in to the streets around you, and because Google supplies the map, Google can tell which area you are looking at.
Technical records. Our servers record account and trip ids, counts, timings and errors, and may record the network address and browser details of each request. They are built not to record what you wrote, though an error reported by another service can include a short piece of it. When the app itself hits an error, it sends us the error, where in the app it happened and which version, with your account id if you are signed in, and that can include a short piece of what you typed.
We do not show ads, we do not sell or rent your information, we do not track you across other apps or websites, and we do not use a third-party analytics service. We never see payment details.
Everyone on a trip sees all of it, including the Hermes conversations and their files.
Anyone with a published trip's link can see its itinerary, budget and photos without an account, along with the name and photo of every member, including people who have since left, and the names of anyone added to the budget. They cannot see Hermes conversations, files, or journey booking references, seats and notes. Only the trip's owner can publish a trip, and switching it off withdraws the link.
Anyone with a photo's own link can open that photo, whether or not the trip is published, because each photo is reached through a link with a secret in it. Those links are shown to people on the trip and to viewers of a published trip, and the link to a trip's cover photo is also shown to anyone holding an invite link. While a trip is published, its photos are open to anyone with its link anyway. When the trip is unpublished, and when someone leaves or is removed from a trip that is not published, we replace these secrets, so every photo link handed out before then stops working, usually within minutes of the change; if replacing them fails, we keep retrying. Otherwise a link keeps working until the photo is deleted or its secret is next replaced, and that includes the cover link shown with an invite that has since stopped working. Files attached in Hermes conversations, and documents uploaded to a trip's Files, are reached the same way, and their secrets are replaced whenever someone leaves or is removed from the trip, published or not, and when it is unpublished.
Anyone holding an invite link can see the trip's name, dates, cover photo, how many days and stops it has, and the first names and photos of its members, before they decide to join. An invite link stops working between 30 and 180 days after it is made, depending on when the trip ends, or sooner if the owner resets or revokes it.
If you are removed from a trip, you lose access straight away, but your device keeps what it had already downloaded until the app next starts after you sign out, when it is cleared. If that clear fails, it is tried again at the next start.
We send information to other services only to run the features you use. We give your account id, name and email address only to Google, which runs our servers and Google sign-in, and to Apple if you sign in with Apple. If you buy Odyssey Pro or a Trip Pass, we give your account id and email address to Stripe, which sells them for us. If you connect an AI app to Odyssey, we also give your account id and email address to WorkOS, which handles that app's sign-in, and that app's sign-in tokens carry your account id. The other services below do not get them from us, but what you write or attach can contain names and contact details, and so can some of Hermes's working notes: for example, when Hermes adds an expense, it is told the name of the person who paid.
| Service | What it receives | When |
|---|---|---|
| Google Firebase and Google Cloud (Google LLC) | Everything described on this page. It is where Odyssey stores your information and runs. | Always |
| Google sign-in | That you signed in to Odyssey, and it gives us your name, email address, profile photo and an account id. | When you sign in with Google |
| Sign in with Apple | That you signed in to Odyssey, and it gives us an account id, your email address or a private relay address, and your name the first time. When you delete your account, we ask Apple to revoke Odyssey's access. | When you sign in with Apple, and when you delete an account that uses it |
| Google Maps Platform | The map library itself, with your network address and browser details; the part of the map you look at; the text you type into place search and the places you choose; the names and positions of stops and journeys, to find places, photos and driving times. | Whenever Odyssey is open, on every page, in the browser and in the iPhone app |
| Google reCAPTCHA | Information about your browser or device and how it is used, to check that requests come from Odyssey and not from a script. It also stores a small entry of its own on your device. | Whenever Odyssey is open, in the browser and in the iPhone app |
| OpenAI | For each message you send Hermes: the recent conversation, including files you attached and the results of the changes Hermes made; the trip's name and dates, day titles, stop and stay names, addresses, map positions and dates, journey details, the facts Hermes has saved to remember, and which kinds of change you let Hermes make without asking. When Hermes looks at the trip in detail: its description, notes, and stop times, and when it asks for them, booking references and seats. It also carries out the web searches Hermes makes. For an email forwarded to a trip's address: the email's text and its attached files, to find the bookings in it. | Each time you use Hermes, and each time an email is forwarded to a trip's address |
| WorkOS | Your account id and email address, so that an AI app you connect to Odyssey can sign in as you. It keeps a record of your account with them, and of the apps you have connected. | Only when you connect an AI app, such as Claude or ChatGPT, to Odyssey |
| An AI app you connect (for example Claude, by Anthropic, or ChatGPT, by OpenAI) | Your account id, which every sign-in token it holds carries, and your email address if it asks to see it when you connect. Then what it asks Odyssey for, at your direction: the names and dates of the trips you are on; a trip's description, its days, stops and stays with their addresses, map positions, times and notes, and its journeys with their notes; and its routes, booking references and seats when it asks for them. | Only if you connect it to Odyssey, each time it reads one of your trips |
| Wikimedia (Commons and Wikidata) | From our servers: the name and map position of a stop, to find freely licensed photos of it and near it. From your browser: your network address and browser details, when it shows a photo Wikimedia hosts. | When photos are found for a stop, and each time such a photo is shown |
| Openverse | From our servers: the name of a stop, to find freely licensed photos of it. | When photos are found for a stop |
| Visual Crossing | From our servers: the approximate location, to about 10 km, of the places on a trip's upcoming days, and of its past days (normally once each), and their dates, to find the weather there. Never your name, your account or the trip. | When someone on the trip opens it and an upcoming day's weather is due a refresh, or a past day's weather has not been fetched yet |
| AeroDataBox, through API.Market | From our servers: a flight's number and its departure date, to find its live status (times, gate, delays), and for flight alerts the flight's number and the address where it sends us that flight's updates. Never your name, your account, the trip or your booking. | When a flight is added to a trip, or its number or date changes, once; when someone on the trip opens it while one of its flights departs within about two days, or is in the air; and for flight alerts, from about six hours before a flight departs until it lands |
| Resend | Your account's email address and the alert: the flight's number, where it goes, what changed (a delay, a gate, a cancellation or a diversion) with its times and gate, the trip's name and a link to it. And any email forwarded to a trip's address, with its attachments, which it receives for us and we fetch from it. | When a flight on a trip you are on changes and you get flight alerts by email (turn them off in Settings), and when anyone forwards an email to a trip's address |
| Google (Firebase Cloud Messaging) and Apple (push notifications) | In the iOS app, once you allow notifications: a code for your phone that lets it receive them, and each flight alert sent to it: the flight's number, where it goes, what changed with its times and gate, and which trip it is on. Never your name or email address. | When a flight on a trip you are on changes, on each phone where you allowed notifications for Odyssey (turn them off in Settings) |
| Stripe (and Link, its payments service), which sells Odyssey Pro and the Trip Pass for us | When you buy Odyssey Pro or a Trip Pass on the website: your account's email address and account id, and for a Trip Pass the trip's id and its dates, never its name. Stripe collects your card, country and billing address itself, as the seller, and we never see them. | When you buy, manage or cancel a plan, when a payment is refunded or disputed, and when we check a purchase (on your return from the payment page, and once a day for a plan) |
| Photo sites those services point to (for example Flickr) | Your network address and browser details, when your browser shows or downloads a photo they host. This includes anyone viewing a published trip. | Each time such a photo is shown, until Odyssey has saved its own copy, and always for a photo it could not copy |
| Stay22 | A stay's name, address and dates, and a reference to the trip. | Only if you tap Check availability. This link is switched off today. |
| Booking.com | A stay's name, address and dates, and a reference to the trip. | Only if you tap Check availability. This link is switched off today. |
Everything described on this page. It is where Odyssey stores your information and runs.
Always
That you signed in to Odyssey, and it gives us your name, email address, profile photo and an account id.
When you sign in with Google
That you signed in to Odyssey, and it gives us an account id, your email address or a private relay address, and your name the first time. When you delete your account, we ask Apple to revoke Odyssey's access.
When you sign in with Apple, and when you delete an account that uses it
The map library itself, with your network address and browser details; the part of the map you look at; the text you type into place search and the places you choose; the names and positions of stops and journeys, to find places, photos and driving times.
Whenever Odyssey is open, on every page, in the browser and in the iPhone app
Information about your browser or device and how it is used, to check that requests come from Odyssey and not from a script. It also stores a small entry of its own on your device.
Whenever Odyssey is open, in the browser and in the iPhone app
For each message you send Hermes: the recent conversation, including files you attached and the results of the changes Hermes made; the trip's name and dates, day titles, stop and stay names, addresses, map positions and dates, journey details, the facts Hermes has saved to remember, and which kinds of change you let Hermes make without asking. When Hermes looks at the trip in detail: its description, notes, and stop times, and when it asks for them, booking references and seats. It also carries out the web searches Hermes makes. For an email forwarded to a trip's address: the email's text and its attached files, to find the bookings in it.
Each time you use Hermes, and each time an email is forwarded to a trip's address
Your account id and email address, so that an AI app you connect to Odyssey can sign in as you. It keeps a record of your account with them, and of the apps you have connected.
Only when you connect an AI app, such as Claude or ChatGPT, to Odyssey
Your account id, which every sign-in token it holds carries, and your email address if it asks to see it when you connect. Then what it asks Odyssey for, at your direction: the names and dates of the trips you are on; a trip's description, its days, stops and stays with their addresses, map positions, times and notes, and its journeys with their notes; and its routes, booking references and seats when it asks for them.
Only if you connect it to Odyssey, each time it reads one of your trips
From our servers: the name and map position of a stop, to find freely licensed photos of it and near it. From your browser: your network address and browser details, when it shows a photo Wikimedia hosts.
When photos are found for a stop, and each time such a photo is shown
From our servers: the name of a stop, to find freely licensed photos of it.
When photos are found for a stop
From our servers: the approximate location, to about 10 km, of the places on a trip's upcoming days, and of its past days (normally once each), and their dates, to find the weather there. Never your name, your account or the trip.
When someone on the trip opens it and an upcoming day's weather is due a refresh, or a past day's weather has not been fetched yet
From our servers: a flight's number and its departure date, to find its live status (times, gate, delays), and for flight alerts the flight's number and the address where it sends us that flight's updates. Never your name, your account, the trip or your booking.
When a flight is added to a trip, or its number or date changes, once; when someone on the trip opens it while one of its flights departs within about two days, or is in the air; and for flight alerts, from about six hours before a flight departs until it lands
Your account's email address and the alert: the flight's number, where it goes, what changed (a delay, a gate, a cancellation or a diversion) with its times and gate, the trip's name and a link to it. And any email forwarded to a trip's address, with its attachments, which it receives for us and we fetch from it.
When a flight on a trip you are on changes and you get flight alerts by email (turn them off in Settings), and when anyone forwards an email to a trip's address
In the iOS app, once you allow notifications: a code for your phone that lets it receive them, and each flight alert sent to it: the flight's number, where it goes, what changed with its times and gate, and which trip it is on. Never your name or email address.
When a flight on a trip you are on changes, on each phone where you allowed notifications for Odyssey (turn them off in Settings)
When you buy Odyssey Pro or a Trip Pass on the website: your account's email address and account id, and for a Trip Pass the trip's id and its dates, never its name. Stripe collects your card, country and billing address itself, as the seller, and we never see them.
When you buy, manage or cancel a plan, when a payment is refunded or disputed, and when we check a purchase (on your return from the payment page, and once a day for a plan)
Your network address and browser details, when your browser shows or downloads a photo they host. This includes anyone viewing a published trip.
Each time such a photo is shown, until Odyssey has saved its own copy, and always for a photo it could not copy
A stay's name, address and dates, and a reference to the trip.
Only if you tap Check availability. This link is switched off today.
A stay's name, address and dates, and a reference to the trip.
Only if you tap Check availability. This link is switched off today.
What the AI provider keeps. We ask OpenAI not to store our requests; OpenAI still keeps a copy for up to 30 days to check for abuse.
An AI app you connect can read the trips you are on whenever it asks, until you remove it from that app or ask us to disconnect it. What it does with them, and how long it keeps them, is between you and that app.
Hermes reads web pages and files. Text in them can try to steer it. Hermes shows you the changes it wants to make to your trip before making them, unless you have told it not to ask for that kind of change. It can save facts to remember without asking; you can see and delete them in the chat.
In the United States, where Google, Apple, OpenAI, WorkOS and Stripe run the services above. Stay22 is based in Canada and Booking.com in the Netherlands. Photo sites, and an AI app you connect, are wherever each is run.
Settings, then Delete account. When you do:
Wherever you live, you can ask us to:
We use your information to provide the service you signed up for, and to keep it secure and working, for example by recording errors and costs. Showing your location on the map happens only when you switch it on.
If you are unhappy with how we handle your information, tell us first at support@vbi.dev. You can also complain to the Office of the Australian Information Commissioner, or to the data protection authority where you live.
Your information is encrypted on its way to and from our servers, and when stored on them. Who can read a trip is checked by our servers each time the app asks. Photos and files are the exception: each is reached through a link with a secret in it, and anyone holding that link can open the file without an account until the file is deleted or its secret is replaced, which happens for photos when a trip is unpublished and when someone leaves or is removed from a trip that is not published, and for files attached in Hermes conversations or uploaded to a trip's Files whenever someone leaves or is removed. The copy kept on your device for offline reading is protected by your device's lock, not by Odyssey. The keys for our AI and routing services stay on our servers; the map and place search use a key built into the app, limited to Odyssey's website and app. If something goes wrong that puts your information at risk, we will tell you what happened, what it affects and what we have done, as soon as we can.
Odyssey is not for children under 16. If you believe a child under 16 has an account, tell us: we will delete that account as described under Deleting your account, and remove anything else the child added that you ask us to.
We change this page when Odyssey changes. The date at the top says when this version took effect, and the list below says what changed and when. If a change affects what we collect or who receives it, we will email you no later than the day it takes effect.
Venkata Bommireddipalli, support@vbi.dev