Privacy

What this site collects, and for how long

Short version: a decision about whether a water is safe to fish is never behind a consent prompt, a sign-in, or a paywall. Everything below is about the small amount of data the site keeps in order to work at all.

Safety is never gated

Safety states, the evidence behind them, where each number came from, how old it is, how uncertain it is, and whether the site fell back to a degraded source are always visible to everyone. There is no cookie banner in front of them, no preference that hides them, and no tier that unlocks them. This is a standing rule, not a current courtesy.

If you are not signed in

The site counts how many reports you have opened today, so the free daily limit means something. To count them without knowing who you are, it stores a one-way hash of your IP address together with that day's date — never the address itself.

Because the date is part of the hash, the same visitor produces a different value every day. There is no way to follow an anonymous visitor from one day to the next, and no code here tries to.

If you sign in

Google handles authentication; the site receives your name, email address, and avatar URL, and stores them along with your tier. If you buy Pro, Stripe handles the payment and holds the card details — this site stores only Stripe's customer reference. Your daily report count is then kept against your account id instead of a hashed address.

How long any of it is kept

• Daily report counts — seven days, then deleted. Backups may hold a copy for up to 35 days longer.
• Sign-in sessions — until they expire, then deleted on the next sweep.
• Your account — until it is deleted. There is no self-serve delete button yet; see the open questions below.
• Error reports — held by Sentry under its retention settings, with page text and form input masked before anything is sent.

One honest caveat: the seven-day sweep is written and tested, but it has not yet run in production. Until it does, older rows are still there. That is tracked as an open item rather than described as finished.

Analytics

None are collected today. The site defines a strict list of events it would be permitted to record, and currently emits none of them.

When that changes, repeat visits will be counted in your own browser and reported only as a range — first visit, a few, several, many — never as an identifier and never as a history tied to you. A control to clear that counter will live on this page.

Who else sees anything

• Google — sign-in, and Google Maps Platform if you save a home address for drive times. The address you type is sent to Google once to look it up and is never stored. We keep only rounded coordinates (about 100 m) and a town name, and send those coordinates to Google each time you load drive times. Drive times themselves are never stored. Clear your home address from your account page at any time; deleting your account deletes it too.
• Stripe — payments. Card details never reach this site.
• Cloudflare and Neon — hosting and the database.
• Sentry — error reports, with text and inputs masked.
• LaunchDarkly — feature flags. It receives a random account id and nothing else: no email, no name, no tier.

There are no advertising networks, no tracking pixels, and no data sold or shared for marketing.

What this site does not do

• No precise location, and no catch locations — the site has no way to record either.
• No social features, sharing, streaks, badges, or feeds.
• No notifications of any kind. No email or push channel exists.
• No account is required to get a decision about a water.

Asking about any of this

Write to privacy@fishingintelligence.app. It reaches a person, not a ticket queue, so allow a few days. There is no automated request process behind it — see below.

What is not settled yet

This page describes a policy that is drafted and awaiting the product owner's approval. Three things are genuinely unfinished, and it is more useful to name them than to leave them out:

• There is no self-serve account deletion, and no automated process behind the address above — a request is handled by hand.
• The seven-day sweep has not yet run in production.
• Sentry's and LaunchDarkly's own retention windows are not confirmed here.

Last reviewed 17 September 2026. Back to the report