What we don't do
- No accounts. No sign-ups. No login anywhere on the site.
- No cookies set by paweather.com.
- No server-side logs we can access — this is a static site served from a CDN.
- No analytics scripts (Google Analytics, Plausible, Fathom, etc.).
- No ad networks, no ad-tech trackers, no fingerprinting.
- No "share with marketers" anything. There is no marketer to share with.
What we do store
Two kinds of things, both entirely in your own browser:
- localStorage preferences. If you pick a default city on the forecast page, we might remember that so you don't have to re-select it next time. It stays on your device.
- In-memory caches. While a page is open, we cache API responses briefly (30–90 seconds) so we don't hammer the upstream APIs. The cache dies when you close the tab.
You can clear either by clearing site data in your browser. There is nothing on the server side to wipe, because there is nothing on the server side.
What we fetch from other services
When you load a page, your browser talks directly to the public APIs listed on our sources page — Open-Meteo, the National Weather Service, RainViewer, USGS, and so on. Those services see your request (your IP address, the URL you asked for, roughly the time). They each have their own privacy policies. We do not proxy these requests, which means we never see them.
Embedded resources (fonts from Google, Leaflet CSS from unpkg) are fetched directly by your browser from those providers. Again, we never see these requests.
Location
We never ask for your geolocation. City pages use predefined lat/lon points; the ZIP lookup feature uses a number you type in. Nothing is geolocated automatically.
Children
This site is safe for readers of all ages. We don't collect data from anyone, including children under 13, because we don't collect data at all.
Changes to this policy
If the technology changes (we add, say, a server-side component), we'll update this page and note the date. The "Last modified" value in the page metadata reflects the most recent change. As of the current publication date, no server-side changes are planned.
Contact
Questions about privacy? Email [email protected] or use the contact page.