Privacy

Short version: no accounts, no ads, no tracking cookies, no analytics. We don’t store the addresses you search. If you buy a report or Pro, Stripe handles the payment and we keep only what’s needed to give you access.

Addresses you search

When you search a street address, your browser sends it to our server, which passes it to the free U.S. Census Bureau Geocoder to find its coordinates. We don’t store or log the address, and we send it in the body of the request rather than in the URL. The Census Bureau handles it under its own policies. ZIP codes, town names and coordinates you type are matched in your browser and only sent to us to look up which county they’re in.

The lookup page’s address bar contains what you searched (for example ?q=…), so you can bookmark or share a result. That URL stays in your browser unless you share it.

Address suggestions (Pro)

With Pro, what you type in the search box is sent to our server and on to the Census Geocoder to suggest matching addresses. It isn’t stored or logged.

Well map (paid reports)

The map in a paid report loads its code from the jsDelivrCDN and its map images from OpenStreetMap. Like any site, those services see your IP address, and OpenStreetMap sees which map area is shown. Free lookups load no map. Choose “Plot” instead and this browser remembers it (in local storage, not a cookie), so the map stays off.

“Use my location”

If you choose this, your browser asks for permission and gives the page your approximate coordinates. They’re only used to run the lookup and appear in the page URL. We don’t store them.

Hosting

The site runs on Cloudflare. Like any web host, Cloudflare processes technical data such as IP addresses to deliver pages and protect against abuse, under its privacy policy. We use Cloudflare’s rate limiting, which counts each IP address’s requests to the lookup and checkout over a minute, to stop automated abuse. We don’t use that data to identify or profile visitors.

Payments

Payments are processed by Stripe, which collects your card details and email address under its own policy. We never see your card number. From Stripe we keep a customer and subscription reference, the subscription’s status and, for Pro, your email address. For a Neighborhood report we keep the point (coordinates), the radius and the search label from your lookup, which can be the address you typed, so the report can be unlocked again. Stripe also has these details, because they travel with the checkout.

If you make a one-time link to open a purchase on another device, we keep it until it’s used or for 24 hours, whichever comes first. For Pro we count how many full lookups you run each day (a number, not what you searched) to apply the fair-use limit in the terms; the count is deleted after two days.

Cookies and analytics

We set no cookies unless you buy something. When you start a checkout we set fwd_checkout, which remembers that checkout for two days so the browser that paid is recognized when it returns. After a purchase we set fwd_access, a signed cookie listing which reports or Pro subscription this browser holds, and with Pro, fwd_plan, which tells the page to offer address suggestions. These are ours alone, last up to 400 days, and aren’t used to track you. Stripe’s checkout pages set their own cookies. We run no analytics or advertising scripts. If that changes, we’ll update this page first and say what we use and why.

Email

If you email us, we use your message and address only to reply, and keep them only as long as needed for that.

Public records

Well records come from public agency datasets. We deliberately don’t collect or show owner names, street addresses or contractor names from those records.

Contact

Questions: hello@floridawells.com.