Privacy policy

Ordo saves travel bookings into trips for you, from ChatGPT or Claude. This is all it keeps and who sees it.

What is stored

• Account: your Google account id and email, and when you first signed in. Sign-in asks Google for your email only (openid email); Ordo reads nothing else from Google.
• Trips: a name.
• Bookings: the fields of each booking as they're saved (kind, title, provider, confirmation code, dates and times, places, address, city, country, details, price and currency), the map coordinates found for them, and a SHA-256 hash of the text the booking was read from. The email or document text itself, and uploaded files, are never stored: they are read once and discarded.
• Sign-ins: the OAuth grants and tokens that let your ChatGPT or Claude account reach your trips, kept in Cloudflare KV; tokens are stored hashed and the account details on them encrypted.
• A shared place cache: place names and addresses looked up for map pins, with their coordinates, not tied to any account.

Who else is involved

• Cloudflare hosts the service and its storage.
• Google handles sign-in.
• OpenStreetMap Nominatim receives the place names and addresses of bookings to find their map pins.
• jsDelivr and OpenStreetMap's tile servers serve the trip view's map code and map tiles to your browser, so they see your IP address and the area shown.
• The AI host (OpenAI's ChatGPT or Anthropic's Claude) reads the emails you give it and sees every tool result; their own policies apply to what they keep.

No tracking, no analytics, no ads; nothing is sold or shared beyond this.

Deleting your data

Ask the assistant to delete your Ordo account (the delete_account tool). It removes your bookings, trips and account at once and revokes every sign-in; the place cache keeps no link to you. Connecting again starts a fresh account.

Contact

privacy@asyncvoyage.com

Ordo