BlazeRadar — Privacy Policy

Effective 2026-08-26 · Version 1.1 · Covers blazeradar.org (website and live map) and the BlazeRadar mobile app.

1. The short version

• We do not track your device's location. The mobile app never asks for location permission, and the map does not use your position. Website analytics derive an approximate (city-level) location from your IP address, which is then discarded.
• No accounts, no profiles for advertising. There is nothing to sign up for.
• The website uses product analytics (PostHog) — pageviews, clicks, session replays with all typed input masked, and which map layers get used — so we can make the product better. You can opt out, and we honor Global Privacy Control signals. The mobile app contains no analytics.
• No ad networks, no ad trackers. Analytics data is never used for advertising.
• We do not sell personal data. Not to anyone, not in any form. We also do not share it for advertising.
• Contact-form messages are relayed to us rather than stored, and analytics never captures what you type into them.
• Like every internet service, our servers and infrastructure see standard connection data (IP address, request logs) needed to deliver the Service.

2. Who we are

Vibetronics LLC (a Georgia limited liability company, subsidiary of Vibewright Labs LLC) operates BlazeRadar and is the data controller for the personal data described here.
Postal address: 1870 The Exchange SE, Ste 220 #580353, Atlanta, GA 30339, USA
Email: hello@blazeradar.org

3. What we collect, and why

3.1 Contact messages (only if you send one). The contact form takes an optional name, your email address, and your message. We use them for one purpose: reading and answering your message. Contact messages are not stored on our servers. They are relayed immediately to our team email inbox and our internal team chat, and exist afterward only there, like ordinary correspondence — kept as long as needed to handle your inquiry, deleted on request. Our server keeps a short-lived, in-memory count of submissions per IP address (an anti-spam rate limit) and logs the fact that a message was relayed, never its content.

3.2 Connection data (automatic, standard). When your browser or the app requests our website, map, or data feeds, our infrastructure sees the standard data any web request carries: IP address, user-agent, endpoints requested, and timestamps — recorded in ordinary web-server access logs on our hosting (DigitalOcean, retained about 14 days) and whatever short-term operational logs our CDN (bunny.net) keeps by platform default. The mobile app requests public map-layer data roughly every two minutes while open; those requests carry your device's IP like any internet traffic, and nothing else about you. We use this data for operations, security, abuse prevention, and debugging.

3.3 Product analytics (website only — added in v1.1). The website and live map use PostHog, a product-analytics service, to understand how BlazeRadar is used and make it better. What it collects when you use the site:

• Usage events: pages viewed, clicks and interactions (autocapture), and product events like which map layers you toggle and whether you're on the fire or air-quality view;
• Session replays: a reconstruction of how pages were used. Everything you type is masked before it leaves your browser, and replay is disabled entirely on the contact page — your message content never reaches analytics;
• Device and context: browser, device type, screen size, referring page, and an approximate (city-level) location derived from your IP address — the IP itself is discarded at ingestion (anonymize-IPs is enforced in our PostHog project settings);
• Identifiers: a random ID stored in cookies/localStorage so return visits count as the same visitor. We do not tie it to your name or email — the site has no accounts.

Analytics data is used only to operate and improve BlazeRadar — never for advertising, and never sold. You can opt out on this device, and browsers sending a Global Privacy Control or Do-Not-Track signal are opted out automatically. The mobile app contains no analytics SDK — this section covers the website only.

3.4 That's the whole list. The website and app have no accounts, no forms other than the contact form, and no uploads. The app has no analytics or crash-reporting SDKs and requests no device permissions — no location, no notifications, no camera, no contacts. If any of that changes (for example, opt-in location for "fires near me," or push alerts), we will update this policy first and ask for the relevant permission at the time.

4. What we do NOT do

• We do not sell personal data, and we have not sold or shared it for advertising purposes.
• We do not track your device's location (analytics uses city-level IP geolocation only, and the IP is discarded).
• We do not use advertising networks, advertising trackers, or advertising pixels — the analytics in Section 3.3 is product analytics, not ad tech.
• We do not build advertising profiles of you or make automated decisions about you.
• We do not use your personal data to train machine-learning models.

5. Third parties that touch data to run the Service

We use a small set of infrastructure providers ("processors"). They process connection data — and contact messages, where noted — only to provide their service to us:

With the one NWS exception above, our data sources receive nothing about you: we fetch and cache wildfire, smoke, drought, and air-quality data (NIFC/WFIGS, NOAA/NWS, NASA FIRMS, EPA AirNow, the U.S. Drought Monitor, Genasys/Zonehaven, InciWeb, FEMA) on our own servers and serve it to you from there. We may also disclose data if the law genuinely requires it, or as part of a corporate transaction — in which case this policy would continue to apply to data collected under it.

6. Cookies and similar technologies

blazeradar.org uses analytics cookies and localStorage set by PostHog (Section 3.3): a random visitor ID and session state, so return visits count as the same visitor. There are no advertising cookies and no cross-site tracking. Opting out (Section 8) stops analytics storage on that device. The mobile app stores no tracking identifiers.

7. How long we keep data

8. Your rights and choices

Analytics opt-out: click here to opt out of analytics on this device . Browsers sending a Global Privacy Control or Do-Not-Track signal are opted out automatically — no click needed.

You can ask us to tell you what personal data we hold about you (for almost everyone: a contact message you sent us, analytics events from your visits, or nothing), correct it, delete it, or give you a copy of it. Contact us at hello@blazeradar.org and we will respond within 30 days. We will never penalize you for exercising these rights. Depending on where you live (for example the EEA, UK, or California), you may have specific statutory versions of these rights, including the right to complain to a supervisory authority. Because we do not sell or share personal data for advertising, there is nothing to opt out of under laws like the CCPA/CPRA — but the request channel above works for any request.

9. Children's privacy

BlazeRadar is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has submitted personal information to us, contact us at hello@blazeradar.org and we will delete it promptly.

10. Security

We use standard security measures appropriate to how little we collect: HTTPS everywhere, access-controlled servers, and minimal data collection as the primary safeguard — data we never collect cannot leak. No internet service can promise perfect security, but our exposure surface is deliberately tiny. If a breach affecting your personal data ever occurs, we will notify affected people and authorities as required by law.

11. International users

Our servers are in the United States (our CDN operates globally). If you use the Service from outside the US, your connection data is processed in the US. Where a legal transfer mechanism is required, we rely on standard contractual protections with our providers.

12. Changes to this policy

We may update this policy as the Service evolves — in particular, before we ever add location features, push notifications, accounts, analytics, or new data collection of any kind. We will post the updated policy with a new effective date and give reasonable notice of material changes. The "collect as little as possible" stance in Section 1 is the design intent of the product; changes that weaken it will be called out explicitly, not buried.

13. Contact

Vibetronics LLC
1870 The Exchange SE, Ste 220 #580353
Atlanta, GA 30339, USA
Email: hello@blazeradar.org · Contact form
Website: blazeradar.org · Terms of Use