Privacy policy.
This page explains what NavWhale collects, what we do with it, and who else sees it. It’s written in plain English on purpose — you should be able to read the whole thing in a couple of minutes.
Who we are
NavWhale is a small hobby project built and run by Liam from St. Petersburg, Florida. There’s no company, no team, no investors — just one person and the third-party services listed below.
What we collect
Account. Your email address and a hashed password, managed by Supabase Auth. We never see your password in plain text.
Profile. An optional display name, your home currency, and an avatar color you pick in Settings.
Trip content. The prompts you type, the clarification answers you give, the itineraries Claude generates for you, any edits you make, plus polls, comments, packing-list items, and the member lists on trips you share.
AI usage events. For each generation request we record the route (e.g. /api/generate), prompt length, model name, and token counts. We use this to track cost and enforce per-user rate limits — not to re-read your prompts.
Technical. Anonymous traffic measurements via Vercel Analytics and Speed Insights, and error stack traces via Sentry. Sentry is currently configured withsendDefaultPii: true, which means an error report can include your signed-in user id alongside the stack trace.
Billing.If you subscribe to NavWhale Pro, our payment processor Stripe handles the transaction. We store a Stripe customer id and your subscription status (plan, renewal date, whether it’s set to cancel) so we know what you’ve paid for — but we never see or store your full card number.
Who we share it with
NavWhale stitches together a handful of third-party services. Here’s exactly what each one sees:
Anthropic— receives your prompt, your clarification answers, and the structured trip facts we build from them, so Claude can draft an itinerary. Anthropic’s API terms say API inputs and outputs are not used to train their models.
Mapbox— receives destination strings we send server-side for geocoding. Your browser also loads map tiles directly from Mapbox when you view a trip map, which means Mapbox can see your IP address at that point.
Unsplash— receives destination strings server-side when we look up cover photos for trip cards. Your browser never contacts Unsplash directly.
Supabase— the primary database. Holds your account, profile, trips, items, polls, comments, packing lists, and member relationships.
Vercel— hosts the app and runs Analytics + Speed Insights.
Stripe— processes subscription payments if you upgrade to Pro. Stripe receives your payment details and email directly; we only receive a customer id and your subscription status. Stripe acts as our payment data processor.
Upstash Redis— stores short-lived rate-limit counters keyed by your user id.
Sentry— receives error stack traces with limited request context if something on the site throws.
Where it's stored
Supabase Postgres (United States region) is the source of truth. Upstash Redis (United States) holds the rate-limit counters. Vercel runs short-lived edge caches close to your browser. There’s no other data store.
How long we keep it
Your account, profile, trips, items, polls, comments, and packing lists live in Supabase until you ask us to delete them. Aggregate AI usage event rows may be retained after account deletion for cost tracking, with personally identifying fields stripped or anonymised.
Your rights
You can ask for a copy of the data we hold about you, ask us to correct anything that’s wrong, or ask us to delete your account entirely. Email the address at the bottom of this page and we’ll handle it.
Children
NavWhale is not directed at children under 13, and we don’t knowingly collect data from anyone in that age group. If you believe a child has signed up, email us and we’ll remove the account.
Changes to this page
We update this page in place when something material changes. The “Last updated” date at the top reflects the current version.
Contact
Questions, data requests, or anything else: email hello@navwhale.com.