Plain language first, because you're an angler, not a lawyer: we collect what the product needs to work, we don't sell it, and you can ask for all of it deleted by emailing [email protected].
Account. Your email address and, if you sign in with Google, the name and profile photo Google shares. Optional profile fields you choose to fill in: display name, phone number (for GO-alert texts), home base location, timezone, species and method preferences, whether you fish fly or spin, your experience, gear, music, the links to your social accounts or website you add, and a profile photo you upload (kept privately, its location taken out). Your Google photo stays with Google: we keep only its link, never a copy.
Product data. The waters you track, your areas, favorites, trips, gear cabinet entries, fishing-log days and their entries (catches, notes, and the photos and voice notes you add — kept privately, their location taken out), the river and weather conditions we read for each day you log, tip ratings and favorites, and feedback you send. Briefings we generate for you are stored so you can read them again.
Technical. Server logs (IP address, user agent, timestamps), client-side error reports from the app, and outbound-click counts on links to guides, shops and shows. We use a session cookie from our authentication provider and one routing cookie (fi_auth) that tells our edge whether to show you the app or the front page; it contains no token. Display preferences (theme, board layout) live in your browser's local storage.
How you found us. On your first visit we set one first-party cookie (of_touch, kept 90 days) that notes where you came from: the website that linked you (its name only, never the page), the campaign tags on the link you followed, the page you landed on (without its query), and when. If you create an account, we save that once with it, along with how you signed in (Apple, Google or email) and any invite link you used, so we can see which links bring people to OUTFISH. It is never sent to an analytics company or anyone else, never changed afterward, and deleted with your account.
A link to one water. A sign-up link for one river (out.fish/start/…) sets one first-party cookie (of_start, kept one day) that names that river, so it is on your board when you create your account. It holds nothing about you, is read once when the account is made, and is never sent to anyone.
Activity. While you're signed in, OUTFISH keeps a short record of what you did in it: signing in, adding or removing a water, opening your board, a river page or a briefing, each step of setup, and errors the app ran into — with the time, and whether it was the website or the iPhone app. It is first party: it stays in our own database, is never sent to an analytics company or anyone else, and is used only to make sure OUTFISH works for you, especially in your first weeks. It is kept 90 days, and deleted with your account.
Photo ID. When you ask OUTFISH to identify a fish, the photo is kept privately in your account with its location taken out. We also keep a short technical note of each request — the photo's format, size and orientation, whether it came from the website or the iPhone app, and the answer — never the photo itself, for 90 days, so the app and the website answer alike. If you tell us an answer was wrong (“Not right?”), we keep what you said it was, and your note, with your account until you delete it — to test photo ID; the photo itself is used for that only if you tick the box that allows it, and is never shown to anyone.
Location. Coordinates are used only when you choose "Near me" on the Trends or Map view, and are not stored.
Analytics. We use Google Analytics 4 to count visits and see which parts of the product get used. IP addresses are anonymized, Google Signals and ad personalization are off, and the few events we send from our servers (a sign-up, a briefing request, a Guide question, a checkout) carry a hashed account id — never your email or anything you typed.
Outbound clicks. When you follow a link to a shop, guide or show we record that a click happened (which link, when, which screen it was on) so we can show partners the traffic we send them and so affiliate commissions can be credited. Some of those links carry an affiliate tag; the merchant may set its own cookie once you arrive. We do not send your name or email with the click.
To run the product: conditions boards, briefings, alerts, trip countdowns, the Tips library and The Guide. To send you the email and push notifications you turned on — every email carries a one-click unsubscribe. To fix bugs and improve coverage. We do not sell personal data, we do not run advertising, and we do not share your data with anyone except the processors below.
Supabase (authentication and database), Cloudflare (hosting and edge), Resend (email), Pushover (push notifications), Google Analytics (usage measurement, anonymized), Stripe (billing — we never see your card number), Anthropic (the language model that writes briefings and powers The Guide receives your waters, conditions data, and the preferences relevant to the request — never your email or payment details), and Google (only if you sign in with Google). Public data providers — USGS, NOAA, TVA, USACE, state agencies, Open-Meteo — receive requests for river and weather data, not your identity; your browser fetches weather for river coordinates directly from Open-Meteo.
Apple Weather. Our server asks Apple WeatherKit for the weather at a water's point — its rain in the next hour, its hourly forecast and any severe-weather alerts — and sends Apple nothing that identifies you. When an alert is in force on one of your favorite waters we push it to you once, and keep a note of which alert we sent you and when for 14 days so you hear it only once; that note is deleted with your account. Apple's Weather mark on the page is an image your browser loads from Apple (weatherkit.apple.com).
Apple Maps (only when we have it switched on). When you are signed in and pick a place in the website's place pickers — a home base, or a new area — what you look up goes from our server to Apple Maps to be named: the name you type, or, when you choose "Use my location", your point rounded to about 100 m. Our server asks Apple, not your browser, and sends Apple nothing that identifies you. Each place Apple names comes with a small map image, which your browser loads straight from Apple (snapshot.apple-mapkit.com), so Apple sees that request as it would for any image on a page. A briefing's Where card shows the same kind of map image of the access point it names, signed by our server and loaded by your browser from Apple in the same way. Drive times come from Apple Maps too: our server sends Apple your home base, rounded to about 100 m, and the points of the waters on your board, and keeps each drive time for a day so your board does not wait on Apple. Those kept times are deleted with your account.
The website's maps are drawn by Apple's MapKit JS when it loads (and by the open-source Leaflet library when it does not). Your browser loads Apple's map code and map images straight from Apple (cdn.apple-mapkit.com and Apple's map servers), so Apple sees those requests as it would for any map on a page. Our server signs the short-lived token that lets the map load on out.fish; it sends Apple nothing about you. How your maps look (Automatic, Satellite, Dark or Standard) is saved with your profile.
You can download everything that is yours here as one file at any time: Profile → Your account → Export my data.
Your data stays while your account is active. Email [email protected] from your account address and we delete your account and its data within 30 days; backups roll off within 90. Server logs are kept up to 30 days, and the activity record and the photo-ID notes above 90 days.
OUTFISH is for anglers 16 and older. We do not knowingly collect data from anyone under 13.
This is a beta. When this policy changes materially we'll email account holders and update the date above.
OUTFISH is operated by Southern Drift, Nashville, Tennessee. Questions: [email protected].