Vibetronics LLC, a Georgia limited liability company and subsidiary of Vibewright Labs LLC, operates BlazeRadar and is responsible for the processing described in this notice. Write to hello@blazeradar.org or Vibetronics LLC, 1870 The Exchange SE, Ste 220 #580353, Atlanta, GA 30339, USA.
The homepage's mobile-launch link addresses your email to hello@vibewrightlabs.com, the parent company's inbox. Sending that request shares your email address, message and email metadata with Vibewright Labs as well as the personnel handling BlazeRadar launch requests. You can instead use the BlazeRadar contact above. An ordinary support question does not subscribe you to launch notifications.
Contact and support. The form collects an optional name, your email and message. We use these to read, respond to and resolve your enquiry. The contact service relays messages to the team's email and internal Discord chat through the providers listed below. Those copies are correspondence; delivery is not the same as deleting all copies. Request processing also uses connection information and anti-spam controls. Please do not send passwords, precise personal whereabouts or unnecessary sensitive information.
Requested launch notification. If you ask to hear when the mobile app is ready, we use your email, request and associated correspondence to send the requested launch notice and handle that request. You may withdraw at any time by replying or emailing either contact above. This does not authorize unrelated marketing. A request creates no account, purchase, app reservation or guaranteed launch date.
Connection and operations. Requests to our site and API carry IP addresses, browser/user-agent information, endpoints and timestamps. Our hosting and CDN use operational records for delivery, troubleshooting, security and abuse prevention. Third-party map tiles, fonts, scripts or forecast requests also expose ordinary connection information to their providers. Turning off analytics does not stop those necessary requests.
After you allow analytics, the website loads PostHog's JavaScript from its US service and sends a limited set of events: the page category viewed and map-layer toggles, including the layer name, whether it was enabled and the fire/air view. The events include a random identifier held in memory for that page and a timestamp. We do not send URL query strings, map-coordinate fragments, referral tags, typed input or message content in these events. We configure no person profiles, session replay, automatic click/form capture, heatmaps, exception capture or browser-performance collection.
We use those limited events to understand which parts of BlazeRadar are useful. We do not identify the visitor by name or email or use these events for advertising. The client disables geographic enrichment and IP event properties. PostHog necessarily receives connection information when your browser contacts it; this client configuration is not a promise that every provider network log discards an IP immediately.
Analytics uses memory rather than a persistent visitor identifier in cookies or local storage. The separate preference blazeradar.analytics.v2 is saved in your browser so your choice works before the analytics library loads. SDK opt-out preferences may also be stored after withdrawal. Choices apply to this browser and origin; a map opened directly on the API host has a separate preference and starts with analytics off. Older analytics identifiers may remain from an earlier version until you clear that site's stored data; this version does not use them to link visits.
The mobile app is in development. This website notice does not certify the permissions, analytics or crash-reporting behavior of an unreleased build. Before a release that collects app data, we will provide the applicable app disclosures, store privacy information and required permission requests. References to possible app features or platform map services describe prospective functionality, not a currently available tracking service.
The following services handle data for delivery, communication or optional analytics. Their legal roles depend on the service and applicable agreement; some also process requests for their own security or service purposes under their own notices.
| Provider | Function and information |
|---|---|
| DigitalOcean | Website/API hosting; data and connection records handled by those services. |
| bunny.net (BUNNYWAY d.o.o.) | CDN; visitor IP, user-agent and request metadata for delivery and operations. |
| Cloudflare | Domain DNS service and DNS requests. |
| Proton | BlazeRadar email hosting; messages, addresses and correspondence metadata. |
| Mailgun (Sinch) and Discord | Contact-form email delivery and internal chat copies; submitted name, email and message. |
| Vibewright Labs LLC | Parent-company inbox and personnel handling launch requests addressed to it; email, request and correspondence metadata. |
| PostHog | Optional analytics on its US service; the limited events above and connection information. No new session replay. |
| unpkg, Google Fonts and OpenStreetMap | Leaflet library, fonts and map tiles requested by your browser; IP/user-agent and request details. |
| NOAA / National Weather Service | When you open the wind readout for a fire, your browser requests that area's forecast; ordinary connection information and the requested forecast location. |
Most source datasets are fetched and cached by our servers. Opening a news story or another external link takes you to the publisher's service, where its own policy applies. We may disclose information when legally required or reasonably necessary to investigate abuse or protect rights and security. A corporate transfer remains subject to existing privacy commitments and any required notice or consent.
Open analytics choices to allow or refuse optional analytics. You can withdraw as easily as you allow it; the choice is saved independently of PostHog and checked again before initialization and each event. GPC or Do Not Track overrides an earlier allowance. If the choice cannot be saved, analytics stays off. Withdrawal stops future capture; it does not automatically delete events already sent.
If you want help locating a current page's analytics records, before closing the page: no ID requested. The ID is optional; do not send extra identity documents merely to make an analytics request. Because identifiers are not retained across page loads, we may not be able to link an older visit to you without additional information.
Ask hello@blazeradar.org for access, correction, deletion or a copy, or to withdraw a launch request. We will respond within 30 days, explaining any lawful extension, exception or verification needed. Depending on applicable law, you may also have rights to portability, objection, restriction, withdrawal of consent and complaint to a data-protection regulator. We will not penalize you for exercising these rights. Our analytics preference is separate from any statutory sale/sharing opt-out right.
Vibetronics operates in the United States; hosting and PostHog processing may occur there and the CDN operates globally. Other providers process requests where their services operate. Where a restricted international transfer requires a safeguard, the applicable arrangement must be established with the provider. A US location statement does not itself establish that safeguard. Contact us for the mechanism and access to safeguards applicable to your information; we do not treat using the website as consent to waive these protections.
Where EU/UK data-protection law applies, optional analytics relies on your permission, and requested launch messages rely on your request/consent as applicable. We use legitimate interests for proportionate website delivery, responding to enquiries, troubleshooting and abuse prevention, balanced against your rights; legal obligations apply to required records or lawful disclosures. Withdrawing consent does not make earlier lawful processing unlawful. We seek separate consent where an activity or local rule requires it.
BlazeRadar is not directed to children under 13 and we do not knowingly collect personal information from them. Contact us if a child has supplied information so we can investigate and remove it as appropriate. Do not send private information about a child through a map or contact message.
We use safeguards appropriate to the information handled, including secure transport and restricted administrative access. No service can promise absolute security. We notify affected people and authorities about a personal-data breach where the law requires it.
We update this policy's date and version when practices change and give appropriate notice of material changes. New or materially changed analytics, location, notification, account or app data collection will be explained before it begins, with required consent or permission requested separately. Publication or continued website use is not analytics consent.
Vibetronics LLC · 1870 The Exchange SE, Ste 220 #580353, Atlanta, GA 30339, USA · hello@blazeradar.org · Contact form · Terms of Use