Privacy Policy
Last updated 2026-11-16
The short version
Milespie has no ads, no analytics tracking, doesn’t sell data, and doesn’t do anything with your itineraries that you didn’t ask for. Everything below spells out exactly which data is involved — what’s written here is all of it.
What an account needs
Accounts can only be created inside the app: with Sign in with Apple in the iOS app, or Sign in with Google in the Android app. Signing in on the web with the same Apple ID or Google account gets you the same account. Your password never passes through us.
From Apple we receive an identifier for your Apple ID, your email (if you chose “Hide My Email”, this is Apple’s relay address, not your real inbox), and the name you chose to share the first time you signed in. These are stored with your account.
When you sign in, the app also sends Apple’s signed proof of download (StoreKit’s AppTransaction). We verify it really comes from Apple and is for this app before creating an account — one App Store account can open one Milespie account. It also records when you first got the app: people who bought Milespie before it became a free download become permanent Pro based on that date.
With Google, we receive an identifier for your Google account, your email, and the name and profile picture URL on your Google account. These are stored with your account. The Android app also sends the Google Play purchase token for the one-time unlock, and we check with Google Play that it’s a valid purchase of this app before creating an account.
If an Apple ID or Google account that has never signed in to the app signs in on the web, we create no account and keep no data.
What you put in
Everything in your trips is stored in Cloudflare’s D1 database: trip names and dates, each day’s items, transit legs, places, costs, notes, tags, checklists and reminder times. New accounts come with a sample trip you can simply delete.
Images you upload are stored in Cloudflare R2, including QR codes and e-tickets you mark as credentials. Only your account (and travel companions you invite to a party) can read them.
All three kinds of sharing are opt-in and can be turned off any time:
- Showcase link: anyone with the link can view the trip, without costs, credentials or booking references.
- Recipe link: anyone with the link can copy the trip into their own account. They get a snapshot; later edits don’t follow.
- Party: members you invite can read and edit the trip, including attachments. Attachments a member uploads count against their own quota.
What gets sent to Google
Our server forwards the following to Google, who handles it under their own privacy policy. Only the query itself is sent — never your account, name or email.
- Place search (Google Places API): what you type in a place field, and the place you pick.
- Route lookup (Google Routes API): the coordinates of the start and end points, and the departure time.
- Map thumbnails (Maps Static API): the coordinates to draw.
When you paste a Google Maps short link, our server follows it to read the start and end points inside.
Results are cached on our side for a while to call Google’s API less often. The cache holds the places and images themselves, not who searched for what.
What goes to Anthropic
Importing a route from screenshots: the route screenshots you pick are forwarded by our server to Anthropic’s Claude, which reads the lines, stations and times. We ask you the first time you use it. Only the screenshots are sent, without your account, name or email — but anything visible in them (notifications, profile photos) goes too, so crop those out first.
We don’t keep the screenshots: they are dropped once forwarded — not stored in our database, not saved as files, not written to logs. What stays is the route text, once you tap Apply.
Anthropic handles them under its privacy policy: by default, content sent to its API isn’t used to train models and is deleted from its servers within 30 days (content its safety systems flag for a usage-policy violation may be kept longer).
Your location
“Sort by distance” asks for location permission when you tap it. Your location is only used on your device to sort; it is never sent to our server or stored.
The app side
Neither app has analytics or advertising SDKs. The iOS app has no third-party SDKs at all (buying Pro uses Apple’s own StoreKit); the Android app uses only Google’s own sign-in component (Credential Manager) and Google Play’s purchase component (Play Billing), which signing in with Google and buying on Google Play require. Apart from the sign-in, the proof of download and the Pro purchase records below, the app only syncs trips with your own account.
Your trips live in a database on your phone, credential images are cached in the app’s files (so the QR still opens in airplane mode), and your sign-in credential lives in the iOS Keychain (on Android, encrypted with a key in the Android Keystore). Home Screen widgets, Live Activities on iOS and trip notifications on Android keep a snapshot of what’s next on your phone. None of this leaves your phone except to sync with your own account.
A few technical records
Purchase verification record: which App Store proof of download (Apple’s transaction identifier and environment) or Google Play purchase (order ID and purchase token) your account was created with, plus the credential we use to revoke Sign in with Apple when you delete your account. This is how one proof maps to one account.
Pro purchase records: when you buy Milespie Pro in the app, the app sends Apple’s signed transaction to our server, and Apple later notifies us directly about renewals, expirations and refunds. We store which plan you bought (monthly, yearly or lifetime), Apple’s transaction identifier and environment, the expiry date and any refund time — used only to tell whether your account is on the Free plan or Pro, and to make sure one purchase applies to one account. Apple handles the payment; we never see your payment method or card details.
Hashed device identifier: when signing in, the iOS app sends iOS’s identifier for vendor to confirm the proof of purchase came from this device; the Android app sends a random identifier it generated on first launch — not a hardware or advertising ID. We store only a hash of it, used to retire old sign-in credentials when the same device signs in again. It only means something to Milespie and can’t be used to track you across apps.
Sign-in records: web sign-in sessions record the IP address and browser information at the time, and are deleted when the session expires or the account is deleted.
Daily usage counts: for the four features we pay Google for — place search, place details, route lookup and map thumbnails — and for screenshot reading, which we pay Anthropic for, we keep a daily count to stop abnormal usage. Counts, not content. The Free plan’s total screenshot reads are added up from these counts.
How to delete it
In the app, go to Settings → Account → Delete Account, or use the Account page on the web. Both do the same thing: permanently delete your account, all trips, the images in R2, the purchase verification record, Pro purchase records and sign-in records. This can’t be undone. We also ask Apple to revoke Milespie’s Sign in with Apple authorization, and if you used Sign in with Google on the web, that Google authorization is revoked too.
Deleting your account doesn’t affect your App Store or Google Play purchases: sign in with Apple or Google again and the app re-verifies, opens a brand-new, empty account, and Pro comes back (if it doesn’t, tap Restore Purchases under Settings → Plan in the app). Deleting your account doesn’t stop an auto-renewing subscription — cancel it separately in your App Store subscription settings.
To leave on one device without deleting anything, use “Sign Out” in the app’s settings — your data stays.
The copy on your phone is cleared separately: delete the app, and iOS or Android removes its local database and caches with it.
If this policy changes
Changes update the date at the top of this page. If a change concerns something substantive — what your data is used for — we’ll also send an email about it.
Contact
For questions, or to request access to or deletion of your data, email support@milespie.com. Milespie is built and run by Anderson Hu, an independent developer.