Privacy Policy
Last updated October 13, 2026
We collect account details, security records and operational logs. Optional community features store the profile, connections, shared plans and content you choose to publish. Coordinates are sent for nearby services and routing; polygon-chat participation additionally requires explicit location-sharing consent. We do not sell your information or use advertising trackers. Some map, imagery and camera requests go directly to their providers, which see your IP address.
1. Who this covers
This Privacy Policy explains how DopplerNav Technologies LLC ("DopplerNav", "we", "us") handles information about people who use dopplernav.com and the radar app (the "Service"). You can reach us at support@dopplernav.com. It is part of our Terms of Use.
2. What we collect
| Information | What it is and why we have it |
|---|---|
| Account details | The name and email address you give when you sign up, when the account was created and confirmed, its status, and which version of our policies you accepted and when. We use these to run your account, confirm it is you, tell you about your account, and keep a record of your agreement. |
| Password | Never stored as you typed it. We keep only a salted one-way hash (scrypt), which cannot be turned back into your password. |
| Email codes | The 6-digit confirmation code we email you is stored only as a keyed hash, expires after 15 minutes, and is cleared once used. |
| Sign-in session | A signed cookie and shared, revocable session record keep you signed in. They include an account reference, policy version and activity/expiry times, never your password. |
| Server logs | Our servers log operational events: failed sign-in attempts and sign-up attempts with the IP address they came from (used to spot and block abuse), unusually slow requests, errors, and anonymous performance reports from the app (a few timing numbers and a coarse browser class such as "chrome-desktop"). Our hosting provider also keeps standard network and platform logs, which include IP addresses. We do not use logs for advertising or profiling. |
| IP address | Seen by us and our hosting provider whenever you connect. Shared security counters use keyed identifiers to rate-limit requests. Platform logs can include IP addresses. We do not display them in community profiles. |
| Location and routes | With browser permission, your reported location is used for your position, nearby resources and Drive mode. Nearby-data and routing requests send the coordinates needed to answer them to our servers and the configured provider. Posting in polygon chat additionally requires explicit consent: a fresh reported position is sent to our server to check whether it is inside the current area. This is not proof of physical location. Sharing a viewing area with connected people is a separate opt-in with a short expiry. We do not publish your account email or a continuous vehicle-location history to other users. |
| Community content | Your optional display profile, invitation code, contact permissions, saved/shared layer groups, collaborative forecast or route inputs, room messages and uploaded images or short videos are stored to provide those features. Connected recipients receive content you grant them access to. Signed-in users outside a polygon can read its room. Moderators can review reports, remove content or restrict participation. Upload only media you have permission to share. |
| What you type in search | Place and address searches are sent to our servers and, for streets and addresses, on to the geocoding provider (Photon, using OpenStreetMap data) to answer them. We do not store your searches or link them to your account. |
| Messages to us | If you email us, we keep the message and your address so we can reply. |
Early access remains free and paid activation is paused. If you later choose a subscription checkout or billing portal, Stripe processes it on its hosted pages. DopplerNav stores the customer/subscription references needed to manage it, never your full card number or security code. Community uploads use files you select; we do not import your device address book or require government identification.
3. What we do not do
- We do not sell your personal information, and we do not share it for advertising.
- We do not run advertising or analytics trackers, and we do not use cookies to follow you across other sites.
- We do not sell location history. Saved route plans and explicitly shared viewing areas can reveal places you intend to visit; choose recipients carefully and revoke sharing when finished.
4. How we use information
- To create and secure your account, send your confirmation code, and tell you when someone tries to register with your email.
- To provide the Service and keep it working: serving the app, protecting it against abuse and fixing faults.
- To send you service messages, such as security notices and changes to our policies. We do not send marketing email today. If we ever do, we will ask you first.
- To keep a record that you accepted our Terms and policies, and which version.
- To meet legal obligations and to protect our rights and those of our users.
5. Who else is involved
Companies that help us run the Service
- Microsoft Azure hosts the Service in the United States (Central US region), stores account records in Azure Storage, and sends our emails through Azure Communication Services. They process this information on our behalf.
- Stripe provides hosted subscription checkout and billing management when you choose to use them. We share your account email and an account reference with Stripe to associate the subscription with your account. Stripe processes payment information under its own Privacy Policy. No billing information is sent to Stripe merely by viewing a Free account while billing is off.
- Cloudflare provides the domain name service (DNS) for dopplernav.com. Traffic to the Service is not routed through its proxy.
Data providers our servers contact for you
To show weather, aircraft, road, geocoding and similar data, our servers request it from providers such as the National Weather Service, NOAA, the Storm Prediction Center, the Iowa Environmental Mesonet, the USGS, adsb.lol, RainViewer, Aviation Weather, Photon and state and national transportation agencies. These requests come from our servers, not your browser, and do not carry your name or email. They may include the area or search text needed to answer you.
Providers your browser contacts directly
Some things load straight from the provider to your browser, so the provider sees your IP address, browser details and what you asked for, under its own privacy policy: map and imagery tiles (OpenFreeMap, Esri, the Iowa Environmental Mesonet, NOAA's nowCoast and NCEP services, terrain tiles for the 3D globe), surface observations from Open-Meteo, the typefaces on our public pages (Google Fonts), and live camera video, which plays from the transportation agency's own stream servers. We cannot control what those providers do with this information.
Other disclosures
If you explicitly connect Discord or a supported streaming platform, we store the connection identifiers, selected alert area and delivery rules needed to post enabled alerts. Streaming authorization tokens are encrypted on the server. Disconnecting stops future delivery and removes the local authorization; provider-side revocation may also be available in your platform account. Messages already posted to a third-party channel are governed by that platform and are not recalled when you disconnect. No chat-platform connection is required to use the core weather features.
We may disclose information if the law requires it, to respond to valid legal process, to protect the safety, rights or property of people or the Service, or to a successor if the Service changes hands (we would tell you, and this policy would continue to apply unless you agree to a new one).
6. Cookies and storage on your device
We use only the cookies the Service needs to work. None is used for advertising or tracking.
| Name | Purpose | Lasts |
|---|---|---|
dn_session | Keeps you signed in. Signed, HTTP-only, restricted to the application host. | Browser session cookie; server expiry within 7 days, after configured inactivity (8 hours by default), or when revoked |
dn_pending | Remembers an unfinished sign-up while you enter your email code. | Up to 60 minutes |
The app saves display preferences, forecast favorites, alert zones, local route drafts, storm-scene references, your chosen NWS office and pinned cameras in browser storage. These local features are separate from community objects you explicitly save or share to the server. Clearing browser storage removes local preferences and drafts. Foreground zone sounds require the app to be open and enabled during that visit; they are not background emergency notifications.
7. How long we keep things
- Account details: until you ask us to delete the account, or until we close an account that has been inactive or abused.
- Billing records: while needed to manage a subscription or respond to a billing request. Account deletion requests also cover our billing references and information held by Stripe, subject to any legally required retention.
- Unconfirmed sign-ups: may be removed if they are never confirmed.
- Polygon rooms: normally become inaccessible ten minutes after their area ends. An official damage report or moderator-confirmed community damage report can extend a room to two hours after its last content activity. Reading does not extend that period. Automated cleanup removes expired messages and media; deletion can be delayed while storage is unavailable. Provider backup retention is separate.
- Shared views: access expires after two minutes without refresh, or when revoked. Connections and saved collaborative objects remain until removed or the account is deleted.
- Email codes: cleared when used and expire after 15 minutes.
- Logs: kept only as long as needed to run, secure and fix the Service, within the retention limits of our hosting provider.
- We may keep some information longer where the law requires it or to resolve a dispute or enforce our terms. A record that you accepted a policy version may be kept for that purpose.
8. Security
We protect the Service with encrypted connections (HTTPS), hashed passwords, signed sessions and rate limits on sign-in. No system is perfectly secure, and we cannot promise that information will never be accessed without permission. If we learn of a breach that affects you, we will tell you as the law requires.
9. Your choices and rights
- See, correct or delete what we hold about you by emailing support@dopplernav.com from your account's address. We will respond within 30 days.
- Location: you control it in your browser's site settings. The Service still works without it.
- Cookies and local storage: clear them in your browser. Signing out removes the session cookie.
- Email: we send only service messages. Tell us if you do not want even those, and we will close the account.
Depending on where you live (for example California, other US states with privacy laws, the UK or the EU), you may have additional rights, such as to know what we hold, to correct or delete it, to object to or restrict its use, or to complain to a regulator. Email us and we will honour them as the law requires. We do not sell personal information or share it for cross-context behavioural advertising.
10. Where information is processed
The Service is run from the United States and information is processed and stored there. If you use it from elsewhere, you understand that your information will be transferred to and handled in the United States, which may have different data-protection rules than your country.
11. Children
The Service is not for children under 13, and we do not knowingly collect their information. If you believe a child under 13 has an account, email us and we will delete it. People aged 13 to 17 may use the Service only with a parent's or guardian's permission, as described in the Terms.
12. Changes to this policy
We will post changes here and change the date above. If a change is material, we will ask everyone with an account to review and accept it before continuing, as described in the Terms.
13. Contact
Privacy questions or requests: support@dopplernav.com.