Privacy
FireRiskHere is built to answer one question — is there wildfire near me right now — with as little of your data as possible. No account, no login, no tracking. This page explains exactly what the site does and doesn’t do with information.
How the site knows roughly where you are
Like every website, our hosting provider (Cloudflare) receives your IP address in order to deliver the page. We use it for one extra thing: an approximate, city-level location estimate, so the page can show you fires near you. That estimate is used to render your result and nothing else — there’s no login, no profile, and the location isn’t saved against any identifier for you. (How accurate this is, and why it’s city-level rather than street-level, is covered in our guide on IP geolocation.)
If you use address search
When you type an address into the search box, that text is sent to OpenStreetMap’s Nominatim service to turn it into map coordinates. To avoid repeating the same lookup, we cache the result for up to 90 days — keyed on the search text itself, not on you. Two people searching the same place share one cached entry; the cache has no idea who did the searching.
If you use the contact form
You send us your name, email address, a subject, and your message, so we can reply. The form is protected by Cloudflare Turnstile to keep out spam bots, and your message reaches us through Resend (an email-sending service) and Cloudflare Email Routing. We use what you send only to respond to you.
If you sign up for email alerts
You give us an email address and a place. We turn the place into map coordinates (through the same OpenStreetMap lookup as address search), store both, and send you a confirmation link — nothing is sent until you click it. After that you receive one email per new fire reported inside your radius, each with an unsubscribe link that works immediately. We keep a log of which alerts were sent to you so we never send the same one twice. We store a shortened, hashed form of your IP address at signup as an anti-abuse measure, never the address itself. Emails are delivered through Resend.
If you request FireRiskHere Watch or an insurance quote
Those forms store what you type (name, email, and the details you give) so we can follow up. Insurance-quote requests are shared with an independent agent only after you tick the consent box on that form, and the page says so plainly; we may be paid for that introduction.
How we count visits
We count page views in aggregate on our own server: which page, which country and region, which site referred the visit, and whether the visitor looked like a bot. No cookie, no visitor ID, no IP address stored, no third-party analytics script — the numbers can tell us that a state page had 300 views on a Tuesday, not who any of them were.
What we don’t do
No accounts. No advertising networks. No third-party analytics or tracking scripts — which is also why there’s no cookie-consent banner: we don’t set tracking cookies. We don’t sell or trade your information.
About the fire archive
We keep a historical record of wildfire activity — the fires themselves, their size and status over time. That archive is about fires, not about visitors. It holds no personal information about you.
Services we rely on
Cloudflare hosts the site and provides security, the location estimate, and email routing. OpenStreetMap’s Nominatim handles address lookups — only when you use search. Resend delivers contact-form messages — only when you write to us.
Questions
Anything here you’d like clarified? Reach us through the contact form.
Last updated: 17 August 2026.