Privacy Policy

Jai turns your travel booking emails into a trip you can see at a glance. This page explains what we access, what we store, what we never do, and how to delete your data.

What we access

If you connect your Gmail inbox to Jai's automatic import feature, we request the gmail.readonly scope — read-only access to your mail. This is requested as its own, separate permission step, never bundled into signing in with Google. Before we read a message, a simple filter checks whether it looks like a booking; messages that don't are skipped and never sent to our extraction step. You can disconnect this access at any time from Settings, which revokes our access at Google immediately.

If you instead forward a booking confirmation to us by email, we only ever process the message you chose to send.

Jai's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

What we store

The trip details we extract from a booking confirmation — flight numbers, dates, confirmation codes, hotel names, and similar — so we can show you your trip.
The original email source, kept so a booking can be re-processed if something goes wrong; it is never modified once stored.
If you connect Gmail import, an encrypted copy of the access token that lets us check your inbox on your behalf. It's encrypted (AES-256-GCM) with a key only our server holds, and it is never visible to us in plain text, never logged, and never shared.
Basic account information: your email address and anything you tell us directly (like a trip name).

What we never do

We never sell your data, to anyone, for any reason.
We never use your emails or trip data for advertising, and we don't build advertising profiles from them.
No one at Jai reads your email content as a matter of course. The only exception is a genuine security investigation (for example, checking for abuse) or where we're legally required to — and even then, access is limited to what's necessary.

Retention and deletion

We keep your trip data and connected-inbox access for as long as your account is active, so Jai keeps working the way you'd expect. If you disconnect Gmail import, we stop reading your inbox immediately and delete the stored access token — trips already created are unaffected.

To delete your account and everything we've stored about you, email us at the address below and we'll delete it. (We're building a self-serve "delete my account" option directly into the app; until it ships, this email request is the path.)

Who else touches your data (subprocessors)

We use a small number of service providers to run Jai. None of them are permitted to use your data for their own purposes.

Supabase — our database and sign-in provider.
Cloudflare — runs our backend and stores incoming email and trip attachments.
Google (Gemini API) — reads a booking confirmation's text to pull out the trip details (dates, flight numbers, and so on). This is the model we use for every real extraction.
Anthropic (Claude) — used only for internal quality testing and comparisons, not for real bookings, at this time.
Resend — sends transactional email (like a trip invite).
Expo — delivers push notifications to the Jai app.
Sentry — receives crash and error reports from the app so we can fix problems. These reports never include the contents of your email.

Contact

Questions, requests, or concerns: hello@myjai.app.

← Back to myjai.app