BirdTrout

Privacy

BirdTrout is a map of trout water and bird cover. It knows your email address, the spots you save, a handful of settings and, if you pay for membership, the state of that membership — never your card. That is the whole list, and this page explains each one.

Last updated 19 November 2026 · dotonesix llc, Michigan

You can use most of BirdTrout without an account at all. Open the map, read the water temperatures, save spots — none of that requires signing in, and until you do, everything you save lives in your own browser and never reaches us.

What we collect, and why

Your email address

If you make an account, we store your email address. It reaches us one way: you choose "Continue with Apple" or "Continue with Google", and Apple or Google tells us your address after you approve it. We ask for your email and basic profile only — not your contacts, calendar, Drive, or anything else. Apple lets you hide your real address behind a relay, and that works here.

The email address is the account. It is how your saved spots find you on a second device, and it is how we would reach you if something about the service changed. It is also where account email goes: a welcome, a reminder near the end of your free trial, and a note if a membership payment fails or a membership ends. There is no password anywhere in BirdTrout, so there is no password for us to store or for anyone to steal. We do not send marketing email; if that ever changes, it will be something you opt into, not out of.

The spots you save

A saved waypoint is a name, a latitude and longitude, any notes you typed, and a note of what kind of thing it was (a dropped pin, a stream, a campground). Signed out, those live only in your browser's local storage. Signed in, they are also written to our database so the spot you saved standing in the river is on the laptop when you get home.

We understand what these are. A list of the places someone fishes or hunts is about as personal as a map gets. They are yours: no other account can read them, we don't aggregate them into anything, we don't sell them, and they are not part of any analytics event.

Your settings

A dozen small preferences travel with your account: your home place (the name and approximate coordinates of the town or spot you set as home), whether you're in fishing or hunting mode, which states you picked, which species you're after, which basemap you like, and whether you've been through the setup questions. They exist so a second device opens into your map rather than into a stranger's default.

Your location, if you offer it

Tapping the locate control asks your browser or your phone for a position fix, and it asks you first. Say no and everything else on the map still works.

The full-accuracy fix never leaves your device. It is used in the page, and only in the page: to move the camera to where you are, to work out which watershed you're standing in, and to rank the water within a couple of hours' drive of you. None of that is written down and none of it is sent anywhere.

What does leave is rounded first, to two decimal places — about a kilometre, which is a town rather than a street. That happens once, at the point where a position becomes your home place, and everything downstream uses the rounded version. There are exactly three things that see it:

Rounding costs those three nothing: a town's name is a town's name, and a drive time from a kilometre away is the same drive time. It is done because a coordinate good to the metre is a home address, and none of them need one.

Saved waypoints are a separate thing and are not rounded — a spot on a river is only useful if it is the actual spot. Those are yours, described above, and they are never sent to Nominatim, OSRM or anyone else.

Where it lives

Supabase holds the account and the synced data — the email address, the waypoints, the settings — in a Postgres database in the US East (Northern Virginia) region. Every table has row-level security switched on, which means the database itself refuses to return one person's rows to another person's session, rather than trusting our code to remember. Supabase also runs the sign-in flow and issues the session token your browser holds.

Vercel hosts the site: the map, the data files, the pages. Like any web host it processes the requests your browser makes, which includes your IP address in its ordinary server logs. We don't build anything on top of those logs.

Third parties BirdTrout talks to

The map is assembled in your browser from several public sources. Some of these your browser contacts directly, which means those services see your IP address the same way any website you visit does. Apart from Stripe and Resend, below, none of them are sent your email address, and none of them, Stripe and Resend included, are sent your waypoints or your notes.

Analytics

We use Vercel Analytics, which is cookieless and aggregated: page views, and a short list of events like "someone exported a GPX file". Every event is filtered before it leaves the browser — strings, numbers and booleans only, nothing free-text, no coordinates, no waypoint names, no notes, no email address. The point is to know that a feature is used, not who used it. There are no advertising or cross-site tracking scripts on this site, and no third-party ad cookies.

We also keep a small count of our own, in our own database, and it exists to answer one question: of the people who find a river or bird page through a search engine, how many go on to open the map. Each row is a step — "a page was read", "the map was opened", "someone signed in" — tagged with an anonymous id described under Cookies and storage below, and with the kind of page it happened on ("a river page", "a bird page"). Never the address of the page, never a referrer, never a coordinate, never anything you typed. Nobody outside this project can read that table, and nothing in it is shared with anyone.

What we don't do

Your rights

These aren't ceremonial. Here is how each one actually works today.

It is a real delete, not a flag on a row we keep. Nothing is queued, nothing waits on a person reading an inbox, and there is no grace period during which we still have it. If the button is not working for you, email us from the address on the account and we'll do it by hand.

Cookies and storage

Three things get stored in your browser, and none of them is a tracker.

The sign-in session. When you sign in, Supabase stores a session token so you stay signed in between visits. Sign out and it's cleared. If you never make an account, this never exists.

Local storage. Your saved spots, your preferences, and a small cache so the map opens where you left it. This is your browser's own storage on your own device — clearing your browser data clears it. Signed out, this is the only copy; signed in, it's a mirror of what's in the database.

An anonymous id. Sixteen random bytes, generated in your browser the first time you arrive and kept in that browser's own storage. It is random rather than derived: it is not made from your address, your device, your email or anything else about you, and by itself it identifies nobody. Its only job is to let us tell "one person read a page and then opened the map" apart from "two people did two unrelated things", which is a question about the site rather than about you. It never leaves this domain, is never sold or shared, is not used for advertising, and clearing your browser data replaces it with a new one.

Retention

Your spots and settings stay until you delete them or delete your account. We don't expire them, and a spot you saved four seasons ago should still be there. Deleting a waypoint marks it deleted immediately so an offline phone can't resurrect it, and the row is cleared out afterwards. Deleting your account removes your email address and your membership record along with everything else, with two exceptions. Stripe keeps the invoices and payment records the law requires it to (see Payments). And we keep a copy of each account email we've prepared for you — the address, the subject and the message; deleting your account currently disconnects those from it but doesn't erase them. We're fixing that, and until we have, email us and we'll erase them by hand.

Kids under 13

BirdTrout isn't for children under 13 and we don't knowingly collect anything from them. This isn't a judgement about who should be on a river — it's that collecting a child's email address and the coordinates of where they go carries obligations under COPPA that a product this small is not set up to meet. Take your kids fishing; use your own account. If you believe a child under 13 has made an account, email us and we'll delete it.

Payments

Membership is paid for on www.birdtrout.com through Stripe, which handles the card. The card details go from your browser to Stripe and never reach us: we don't see your card number and we don't store it, or even its last four digits.

What Stripe receives: your email address, your card details, the billing details Stripe's checkout asks for (such as your country and postal code), and information about your device and connection that Stripe uses to stop fraud. Stripe handles these under its own privacy policy. We don't send Stripe your spots, your settings or anything about how you use the map.

What we store: the identifiers Stripe gives your customer record and your subscription, the membership's status (for example active, payment overdue or cancelled), and when it started and when the current period ends. That is what lets the map know you're a member on any device you sign in on. We also keep a record against your account of each completed payment — the amount, the currency and whether it was your first — so we can count members and revenue, and we note when a checkout is started as one of the steps described under Analytics. All of these are deleted with your account.

When you delete your account, any membership is cancelled at Stripe first, so nothing more is charged, and we ask Stripe to delete your customer record, which removes the email address and card it held for you. Stripe keeps the invoices and payment records it is legally required to keep, and we can still see those in Stripe for our own accounting and tax records.

Membership can't be bought inside the iOS app today. If that changes, purchases made there will go through Apple, and this page will say what Apple and we receive before it happens.

Changes to this policy

We can change this page. If a change actually affects you — new data collected, a new company involved, a different use for something we already hold — we'll email the address on your account before it takes effect. Wording fixes and clarifications we'll just make, and the "last updated" date at the top will move.

Contact

Questions, requests, or something on this page that doesn't match what you're seeing: andrew@dotonesix.com. A person reads it.