Effective October 14, 2026
Sequence finds the travel bookings in your Gmail and turns them into a timeline of your trips. It is run by Sequence Apps LLC, the controller of your data. Contact: hello@sequence.travel.
We don't store your emails. We read each email only while we process it, keep the details we find in it and a short record of the message (listed below), and discard the email itself.
We ask Google for one permission, gmail.readonly: read-only access to Gmail. We fetch only email that is likely a travel booking or receipt, including receipts from the tree-planting charity we support, and read its full text, including PDF and calendar attachments. We never send, change, label or delete email.
We keep:
We never keep an email's body or attachments. Opening a booking to review it fetches it fresh from Gmail and does not keep it. We keep the coordinates of places we look up, so each is looked up once; that store holds places, not people, and is not linked to your account.
Legal basis: we use this data only to provide the service you asked for. Without Gmail access, Sequence cannot find your trips.
| Provider | Receives | Why | Where |
|---|---|---|---|
| TypeSafe | Every email our booking scan fetches, with attachment text. For a flight booking, also your email address and Google display name. | Tells whether an email is a booking and of what kind; for a flight, what it says about each flight and booking number, and whether you are flying | US |
| OpenAI | Travel booking emails the check admits, with attachment text; a booking's vendor name, address and dates | Pulls out travel details, assembles trips, places bookings on the map | US |
| Anthropic | A tree-charity receipt we cannot read ourselves | Pulls out the order number, trees, amount and date | US |
| Supabase | The data we keep | Database | US |
| Railway | Everything we process, while we process it. Its request logs also keep the address of each page and map image you load, which shows the map areas you view, with your IP address, for up to 30 days. | Hosts our servers | US |
| Sentry | Error reports, with personal data removed | Error monitoring | US |
| Hetzner | Place names from bookings; flight numbers and dates | Rents us our own server, which turns places into map coordinates and looks up past flights | Finland |
| OpenStreetMap | A place's text, like a hotel address or station name | Turns it into map coordinates when our own server cannot | UK, Netherlands |
| US Census Bureau | The same text | A second opinion on where the place is | US |
| FlightAware | A flight number, airport pair and dates | Flight schedules and status | US |
| Apple | In the app: notification text, like a booking's name, address and time, and App Store payments. On our servers: a printed address with a house number that our own server could not place at the house, and a printed airport terminal our own map data has no match for. We keep nothing Apple sends back. | Notifications, payment, and the map point for that house or terminal | US |
| Resend | Your email address | Sends you email | US |
| RevenueCat | Your account ID, email address and purchase record | Manages subscriptions | US |
| Stripe | Your payment details, from you directly | Web payments | US |
We do not use your email or any other Gmail data to develop, improve or train AI or machine learning models. Only TypeSafe, OpenAI and Anthropic see email content, and none of them trains a model on it. For OpenAI and Anthropic that is part of their standard terms, which also let them keep a copy for up to thirty days to investigate abuse; for TypeSafe it is part of its privacy policy. Only Resend, RevenueCat and TypeSafe receive your email address, and only TypeSafe your name. We never see your card. OpenStreetMap, the Census Bureau, FlightAware and Hetzner receive nothing that identifies you.
We have signed data processing agreements with Railway and Hetzner. Every other provider handles your data under its own standard terms; for TypeSafe, OpenAI, Anthropic, Supabase, Resend, RevenueCat and Stripe, those terms include a data processing agreement. For EU and UK users, sending personal data to the US is a transfer; Railway's agreement and those seven providers' terms include the standard contractual clauses for it. Hetzner's server is in the EU, so for EU users it is not a transfer. We do not sell your data or share it with advertisers or anyone else, and no other party tracks your activity across sites through Sequence. A new provider is added here before it handles anything.
We keep your trips, message records and account details while your account is active, and delete them immediately when you delete your account. We delete each entry in the security record after a year, or sooner when you delete your account; the copy of each entry in our hosting provider's logs expires on its own within 30 days. We never keep email content beyond processing it. After deletion we keep only two things. Your subscription record (plan, dates, paid or free), without your email address, which we and RevenueCat keep so a paid subscription survives if you return; RevenueCat also keeps its purchase record. And your Google account ID with the dates you first imported trips and deleted your account.
You can see your trips on your dashboard, correct or delete any of them, and email us for a copy. You can delete everything from account settings or by emailing us; deletion is immediate, cannot be undone, and revokes our Google token. You can also revoke our access on your Google permissions page, and withdraw consent by disconnecting Gmail. In the EU or UK you can also ask us to restrict or object to processing, and complain to your data protection authority.
We use Google user data only to provide the features described here. We do not use it for ads, sell it, or use it for credit decisions, and no person reads it unless you ask, security requires it, or the law does.
Sequence's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
If we change this policy, we update the date at the top of this page.