Privacy Policy.
Last updated: October 2026 · StormSyncApp.com
Overview
StormSync VT/OI is a free project run by one person. This page says what the website and the download store about you, what the app and my servers record when they connect, what happens if you switch on the optional location sharing feature, who else can see that, and how to get your information deleted. I tried to keep it short and complete. If something here is wrong or unclear, email me.
In short: the website saves only the IP address and time of each download. The app's servers keep short-lived technical logs. Location sharing is off unless you turn it on, and if you do, your position is sent only to my relay server and the weather services listed below, and it can be seen by anyone who has your overlay links.
What the download stores
This section is about the website only. There is no sign-up or access form: the download page is a single button. Browsing the site does not create a record with me. When you download the installer, this is saved:
| Data | Why | How long |
|---|---|---|
| Your IP address at the time you download | To keep the download count honest and see roughly how many people download StormSync. | Until I clear the download log, or the project ends |
| The date and time of the download | Saved next to the IP address, so downloads can be counted by day. | Same as above |
The download itself collects no name, email address or answers, and nothing else is saved with these two items. The log is kept in the site's database and I am the only person who looks at it in the admin area. The site's host and Cloudflare, covered below, also handle ordinary web traffic, including your IP address, whether or not you download anything. The app and its servers are covered separately in the sections that follow.
Cookie and browser storage
The site no longer sets a cookie or saves anything in your browser's storage to make the download work. Earlier versions of the site had an access form, which saved a cookie named ss_client and a local storage entry called ss_client_token. They are no longer used. If you filled in that form, you may still have them, and clearing your cookies and site data removes them.
The old access form. People who used the old form before it was removed have a record from it: the name, email address, answers and IP address they entered, and the time of their last download. I have not used that record for anything new. To have yours deleted, email me from the address you used on the form.
Security and abuse prevention
This is separate from the download log above. To keep StormSync Central and the stream services reliable, and to stop abuse, my servers record a small amount of technical information whenever the StormSync app connects to them. This happens automatically, and you do not need to fill in anything for it to apply.
Each connection can record:
| Data | Why | How long |
|---|---|---|
| Your IP address | Any server sees it when you connect. I use it to spot and block abusive traffic, such as floods of connections or repeated failed attempts. | Connection logs and stream details are deleted automatically after 7 days. If access is restricted for abuse, the address involved is kept until the restriction is lifted. |
| A random install ID, created when you install StormSync | Lets me tell one installation from another, so a problem can be dealt with without affecting everyone else. It is random and is not derived from your name or your files. | Same as above |
| An anonymized device identifier | A one-way hash. It cannot be reversed to find out who you are, your name, or anything about your files. It helps me recognize a device that keeps coming back after an install ID has been reset. | Same as above |
| App version | So I can tell whether a problem comes from an old build, and when it is safe to retire an old version. | Same as above |
| When you connected and disconnected | To keep the service reliable and to investigate outages or unusual connection patterns. | Same as above |
| The number and type of requests made, including failed or rejected ones (and developer logins) | To detect abuse, such as excessive or malformed requests, and to see where the service is struggling. | Same as above |
| If you use StormSync stream overlays: the on-screen details you set in them (stream name, title, social media handles, sponsor names, and the topic or breaking banner text you send from the Streamer Remote), and when your overlays were live | This is information you already show publicly on your stream. I use it only to connect a stream to its StormSync install when enforcing the rules, for example when an abusive install needs to be tied to the stream it is feeding. | Deleted automatically after 7 days. Kept only while a restriction is in place, if the stream is linked to one. |
What I use it for. Only to run the service, to investigate and prevent abuse, and to enforce restrictions on installs, devices or networks that break the terms. This includes the stream overlay details above, which I use only to link a stream to its install. I do not use any of it for anything else.
What I do not do with it. I do not sell this information, use it for advertising, or share it with third parties, except where the law requires it. The one exception is feedback you choose to send from the app, which is described under Other data the app and server handle.
Restrictions. If access is restricted because of abuse, the IP address, network or identifier involved has to be kept for as long as the restriction lasts, otherwise it could not be enforced. Once the restriction is lifted, that information is removed too.
Your NWWS-OI password. It is never sent to my servers. If you use a Private Feed, your app talks to NWWS-OI directly, and the credentials stay on your PC.
Questions or deletion. If you want to ask about, or request deletion of, data tied to your install, email me at [email protected]. Because the install ID is random, it helps if you include it in your message, but the logs are deleted automatically after 7 days in any case.
Location sharing (Stream tab)
StormSync has an optional "Share my location" feature (Stream tab, then Chaser). It lets streamers, often storm chasers, show where they are on their OBS stream overlays: the GPS Location, Live Conditions, Storm Proximity and Chase Map elements, and the optional panels in the Full Stream Overlay. This is the most sensitive thing the app can do, so this section goes into detail.
It is off by default. It only turns on when you switch it on, and you can switch it off at any time. If you leave it on when you close the app, it turns itself back on the next time the app starts.
Where your position comes from. Either the Windows Location service (a laptop's built-in GPS, or Wi-Fi-based positioning provided by Microsoft, which is covered by Microsoft's privacy statement), or a USB or Bluetooth GPS receiver connected to your computer. The app's in-app Warnings Map can also use your GPS. That use stays on your computer and is never sent anywhere.
Services your computer contacts directly
While sharing is on, your computer contacts these services itself. They receive your IP address and coordinates, and each is governed by its own privacy policy, not mine.
| Service | What it is used for | How often |
|---|---|---|
| api.weather.gov (U.S. National Weather Service) | Your position (about 4 decimal places) is used to look up the nearest town, county, state and NWS forecast office. | Again after you move about 1.5 km, or every 10 minutes. |
| api.open-meteo.com (Open-Meteo) | Your position is used to get current weather (temperature, dew point, humidity, wind, pressure, sky, CAPE, lifted index and CIN) and ground elevation. | About every 10 minutes, or after you move about 8 km. Elevation comes with the town lookup. |
What is sent to StormSync's relay server
The relay server delivers your data to your overlays. It is operated by StormSync and hosted by Oracle Cloud Infrastructure in the United States. It receives:
| Data | Detail |
|---|---|
| Whether sharing is on or off | Switched on and off by you. |
| Place details | Town, state, county and NWS office; distance and direction from the nearest town; ground elevation. |
| Movement and weather | Speed and heading, plus the current weather values listed above. |
| Your position | By default, rounded to 2 decimal places (about 1 km). If you choose "Exact (for the Chase Map)", it is sent at full precision (about 1 m) together with the GPS accuracy figure. |
| Your path during the current chase (for the Chase Map) | At the same precision as your position: a point about every 250 m, up to 2,500 points. |
How often. Every couple of seconds while something changes, and at least every 15 seconds. The full path is sent every 30 seconds.
The connection itself. Like any connection to my servers, it is covered by the technical logging in Security and abuse prevention (for example your IP address and install ID, kept 7 days). The location values listed above are not recorded in any log.
How long the server keeps it
- It is kept in the server's memory only. It is not written to disk and not recorded in any log.
- Each update replaces the previous one. Only your latest position, weather and path exist on the server.
- It is cleared immediately when you turn sharing off.
- It is also dropped automatically after 6 hours without activity from your stream, and whenever the server restarts.
Who can see it
Anyone who has your overlay links. Those links contain your private stream key, and the overlays' data feed delivers all of the data above. In practice that means whoever you give the links to, and the viewers of your stream, who see whatever your overlays display.
With "Exact" switched on, your stream effectively makes your precise location public. The app warns you about this when you choose it. Unless you really want to show exactly where you are, I recommend leaving it on the default Approximate setting. Please keep your overlay links private, and do not post them anywhere you would not post your location.
What is kept on your own computer
- Your path is saved to a file in your profile folder (
.stormsync/chase_track.json), with exact coordinates and timestamps, so your chase map survives an app restart. This is true even if you share at Approximate. - A new path starts after 4 hours without movement. The Clear path button deletes it.
- Your on/off, Exact and GPS-source choices are saved in the app's settings file.
What I do not do
I never sell location data, never use it for advertising or analytics, and never use it for anything except showing it on your own overlays.
Other data the app and server handle
Beyond the download log, the activity logs and location sharing described above, the app and my relay server handle the following. The download log and the relay server are separate systems: the relay server does log IP addresses, as described in this policy.
| Data | Why | How long |
|---|---|---|
| Activity log (relay server): connections, app starts, rate limits, rejected requests and developer logins, with your IP address, a random install ID and a device ID | Abuse prevention and troubleshooting. | 7 days |
| Stream profiles (relay server): for each stream, a hashed form of the stream key, the IP address of the computer running the overlays, session start and end times, the details carried in the overlay links (name, title, social handles, sponsors), and the topic and breaking banner sent from the Streamer Remote | To find and help with a given stream, or to stop abuse of it. | 7 days |
| Uploaded stream images (logos and sponsor logos), stored on the relay server under a hashed form of your stream key | So your overlays can show them. | Until you remove them |
| Feedback you send from the app: your message, an optional contact you type in, the app version, operating system, theme and mode, and the first 8 characters of your install ID | So I can read and answer it. It is saved on the relay server and forwarded to a private Discord channel, so Discord's privacy policy applies to that copy. | Until I delete it, or the project ends. Ask me to delete yours at any time. |
| Bans: the IP address, device ID or install ID involved in abuse | To keep restricted access restricted. | On a ban list until removed |
Only send feedback you are happy for me (and the private Discord channel it goes to) to read. Please do not put passwords or other sensitive details in it.
What I do not do
I do not sell, rent or share your information with anyone for marketing, and I do not send newsletters or promotions. The only emails you should ever get from me are a reply to something you sent, or a notice that really does need your attention, such as a security problem.
I do not run analytics or advertising scripts on this site.
Other services that see your visit
The website runs on WordPress hosting and is served through Cloudflare. Both handle network traffic as part of keeping the site online, and both have their own privacy policies and logs that I do not control.
The site's fonts load from Google Fonts. That means your browser contacts Google when a page loads, and Google receives your IP address and browser details, as it would for any site that uses them.
Inside the app
Your alert history is stored in a local SQLite database on your PC. If you use a Private Feed, your NWS username and password are saved on your PC too. I do not receive either of them.
To do its job, the app connects to a few outside services, and each of them can see your IP address, as any server would:
- Central Feed relay (run by me), if you use Central Feed. It carries raw NWS alert text to your app. No user credentials are involved. My servers log the technical connection details described under Security and abuse prevention.
- NWWS-OI directly, if you use a Private Feed.
- Update checks against my server, so the app can tell you when a new version is out.
- Map and radar providers, to draw maps and radar.
- The NWS and the Storm Prediction Center, for outlooks, discussions and archives.
- Discord, if you add a webhook (alerts you choose to forward are sent to the webhook address you entered), and for feedback you send, which is forwarded to my private Discord channel.
- The NWS and Open-Meteo, if you switch on location sharing, as described under Location sharing.
Stream overlays. The overlays themselves run in the streamer's OBS. They load map tiles from Esri, radar from NOAA and Iowa State University (Iowa Environmental Mesonet), and fonts from Google Fonts. Those services see the IP address of the computer running OBS.
Your choices
You can ask me, at any time, to show you what I have stored about you, correct it, or delete it. If you used the old access form, email me from the address you used on it and I will delete your record. For the download log, email me the IP address and I will delete the matching entries.
For data tied to your app install rather than the website, see the last paragraph of Security and abuse prevention. To stop location sharing, switch it off in the app, which clears it from the server straight away. To remove the saved path from your computer, use Clear path.
Children
StormSync is not aimed at children under 13 and I do not knowingly collect their information. If you think a child's information has reached me, for example through the old access form or in-app feedback, email me and I will delete it.
Changes
If the download log, the app, the location feature, my server logging or the services above change in a way that affects your privacy, I will update this page and the date at the top.