Your location is for your forecast, not our filing cabinet.

Frontend privacy

What happens when you use this page

Location search

Cached-city searches stay in the page. If no cached place matches, a town or county query is sent to Open-Meteo geocoding, while a postcode is sent to postcodes.io. The result is held only in this tab's memory, and the page URL keeps only the chosen cached-city ID—not the searched place, postcode or coordinate.

“Use my location”

The browser asks permission only after you choose the button. If allowed, JavaScript compares the supplied coordinates with 12 cached city centres, reports the nearest one, and discards the coordinates. WeatherChart does not place them in local storage, a URL, Cloudflare Web Analytics or another network request.

Local storage, accounts and analytics

WeatherChart creates no account, stores no preferred city and sets no analytics or advertising cookie. A cookie-free Cloudflare Web Analytics beacon records aggregate page-view and page-performance information without using cookies, local storage or other browser storage. WeatherChart stores one necessary local-storage record named weatherchart.privacy.v1 containing the privacy-policy version, whether you allowed optional maps, the decision time and its expiry. It expires within 180 days and can be cleared or changed at any time.

Third-party connections

Cloudflare Web Analytics loads on each page and receives a small performance beacon. Uncached place searches contact the named geocoder only after you search. The Leaflet library and OpenStreetMap tiles are requested only after you allow the optional interactive map. Those services receive ordinary connection information such as an IP address and browser headers under their own policies. Rejecting the map leaves forecasts, warnings, charts and accessible tables available. Direct source and community links leave WeatherChart when selected.

Community data

Cards contain permitted public post text plus explicit platform, author, time and direct-source attribution gathered server-side. Public items expire within 48 hours, and no synthetic replacement is shown when current posts are unavailable. The aggregator must never retrieve private messages, private profiles, deleted content through workarounds, EXIF coordinates or a precise location inferred from an image.