Privacy

What is stored

The trips you create and everything on them: flights, stays, transfers, tickets, confirmation numbers, costs, points, notes, and to-dos. Your account: an identifier from the service you signed in with, your email address, and a name to call you by.

The last two are narrower than they sound. The email address is stored as ciphertext rather than in the clear, and it can be an address that says nothing about who you are. The name is a given name only: every traveler Stub reads out of an email is reduced to a given name and one initial before anything is written down.

Date of birth, passport numbers, Known Traveler and Global Entry numbers, and loyalty numbers are never collected at all. Security says how that is enforced. There is no advertising tracking anywhere in the product.

What leaves the server

Text you ask Stub to read — a pasted confirmation, a described trip — goes to OpenRouter, which routes it to a language model that turns it into structured items. Place names go to OpenStreetMap's Nominatim to become coordinates. Destinations and dates go to weather.gov and Open-Meteo for the forecast strip. None of those four services receives your whole trip, and none is told who you are.

Map tiles are the exception. Your browser fetches them straight from CARTO, so CARTO sees your IP address and roughly where on a map you are looking.

Ask Miles is a separate case. A question asked in the dock is sent to Stub first, and Stub forwards it to Miles, authorized by your Miles account — your browser never talks to Miles directly. What Stub sends is the trip's id, its dates, the panel open when you asked, the id of every item on it, the message itself, and recent history. The trip's name is deliberately left out: it is text you typed rather than a fact Stub already has, so Miles reads it back through its own call into Stub's MCP server instead — the same call that returns the trip you have open in full, not a redacted copy, with the token identifying you because Miles issued it. What Miles does with a question once it has it, and with the trip data its own call reads back, is governed by Miles' privacy policy, not this one.

stub.travel also runs Cloudflare Web Analytics, a beacon Cloudflare adds to the page rather than something this application sends. It counts visits and measures how fast pages load. It sets no cookie and keeps no identifier for you, so it cannot follow you to another site or build a profile of you. It never sees a trip: the beacon reports straight from your browser to Cloudflare, so it never reaches this application's server at all.

Sharing is something you do

A share link is unlisted, read-only, and revocable at any time, and it holds back confirmation numbers, costs, and notes. Sending someone your itinerary is not the same as sending them your booking. A calendar subscription link is the same shape.

Both are unguessable rather than access-controlled: anyone holding one can read it until you revoke it. Nothing is published unless you publish it, and nothing about your trips is ever sold, rented, or handed to an advertiser.

Forwarded email

Mail sent to your forwarding address is read for itinerary details, and those details become items on your trips. The message itself is read in memory and never written to the database. The address is random rather than derived from your name, so it cannot be guessed, and regenerating it permanently stops anything sent to the old one. Mail from a sender other than your own address is never treated as trusted, and everything forwarded in waits in the unfiled tray for you to review.

Where it lives

On a machine I control, in a single database file, replicated to object storage. Not on a cloud platform that reads it. Sign-in sessions are stored as hashes, never as the value in your browser, and your email address and Miles access tokens are encrypted with a key held inside Vault that the application can use but cannot read. Your trips are not encrypted by the application. The disk under them is, and it unlocks by hand rather than on its own. Security is the page that says so properly, with the rest of the limits.

Getting it back, or getting rid of it

Ask for an export or deletion by emailing support@askmiles.ai. There is no export button and no delete-account button. I carry out both requests by hand. Deletion covers the account row, its trips and items, its sessions, and any share or calendar links it minted.

Deleted trips can remain in server dumps, and replicated database history remains for up to 7 days. There is no account key I can destroy to make those copies unreadable sooner. Deleting your Miles account does not delete any of this, so if you want both gone, ask for both.