Privacy Policy

Information WeatherGeo handles

You can browse public WeatherGeo pages without creating an account. Optional features process the information needed to provide those features.

• Browser preferences and saved places: Your temperature unit, saved and recently viewed cities, and cities selected for alerts are stored in browser or WebView local storage.
• Android home-screen widget: If you add the WeatherGeo widget, the city you select and its temperature-unit preference are stored in the app on your device. The widget periodically requests current conditions and that city's daily high and low from the WeatherGeo API. It does not use background GPS. The app caches the last successful weather response on your device so the widget can display it when offline. WeatherGeo's API may receive and log the selected city identifier and standard request information when the widget refreshes.
• Location lookup: If you choose "My location" and allow location access, your latitude and longitude are sent to the WeatherGeo API to find a nearby listed city. The Android app requests foreground location only; you can search for a city instead or deny permission.
• Weather alerts: If you opt in, WeatherGeo stores your browser push endpoint, push encryption keys, selected city, and alert delivery timestamps so it can send that city's daily forecast alert.
• Forecast email form: Submitting the form sends your email address, selected city, and frequency to the WeatherGeo API. The current API does not store or start email subscriptions; unless the service explicitly confirms your sign-up, you are not subscribed.
• Operational logs and city totals: API logs can include request method, URL, response status, and duration. Location coordinates can appear in a request URL. Production web-server logs may include IP address, user agent, and referrer. WeatherGeo also stores daily city-level page-view totals for its popular and trending location features.

Maps and service providers

Interactive map requests occur when you open a map. Depending on the selected layer, your browser may request map tiles from CARTO or Esri. WeatherGeo also requests radar metadata and tiles from RainViewer. These providers may receive your IP address and the map or radar tile requested by your browser; their own privacy notices apply.

A third-party hosting provider operates the production server for the WeatherGeo website and API and may process standard request information as part of that service.

WeatherGeo sends Web Push notifications directly to the push-service endpoint supplied by your browser. The browser push-service operator receives the subscription endpoint and encrypted delivery request needed to deliver an alert. WeatherGeo does not use a separate push-messaging vendor.

• CARTO Privacy Notice
• Esri Privacy Statement
• RainViewer Privacy Policy

Security and transmission

Connections from the website and Android app to WeatherGeo public services use HTTPS/TLS. The website redirects HTTP requests to HTTPS and enables HSTS. The Android app is configured to block cleartext HTTP.

Storage and retention

Browser preferences and saved or recent places remain in local storage until you remove them or clear WeatherGeo site data in your browser. You can turn off an alert in WeatherGeo or disable notifications in your browser. WeatherGeo removes a server-side push subscription when it receives an unsubscribe request, when the push endpoint is no longer valid, or after five consecutive delivery failures.

WeatherGeo stores aggregate page-view totals by city and date for its popularity and trending features. No automatic expiry is currently configured for these aggregate rows; they remain in the database until removed by an administrator or the feature or data store is removed.

Production Nginx and WeatherGeo application logs are rotated daily and compressed, with up to seven rotated archive files retained per log. Size-based rotation can shorten how long a log entry remains. These logs may include the request information described above.

WeatherGeo has no separate database-backup schedule configured on this server. Any infrastructure-level backup or snapshot made by the hosting provider, if enabled, is controlled by that provider and may have a separate retention period.

Your choices and requests

You can decline location permission and use search, clear browser storage, and turn off push alerts through WeatherGeo or your browser settings. Depending on where you live, privacy law may give you rights to request access to, correction of, or deletion of personal information. Contact WeatherGeo to make a request; we may need to verify it before responding.

Changes to this policy

WeatherGeo may update this policy as features or data practices change. The latest version and its update date will be posted on this page.