Weather widget data paths

Where WordPress weather plugins send visitor data

A weather widget can show a forecast by asking an outside weather service for data. Some plugins make that request from your WordPress server and cache the result, so the visitor browser does not call the weather service. Other plugins load an outside weather page in the visitor browser. Requests to that service include an IP address and browser information. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group weather plugins

We compare the weather widget setups named below. A plugin that fetches the forecast on your WordPress server is different from a plugin that loads an outside weather page in the visitor browser. Looking up a visitor IP on the server is a different setup from a browser location permission prompt. Map tiles belong on the map plugin privacy page. We have not tested consent timing or how long weather-service logs are kept.

Weather plugins

No paid placement. Forecast fetched on your server first, then outside weather services, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented service domainsHow long data is keptBefore consentLinksSource
Location Weather

This row covers Location Weather when a city, zip, or coordinates are saved and the forecast is fetched on your WordPress server. The owner API key stays in plugin settings. OpenWeatherMap and WeatherAPI are the documented sources. A setup that looks up the visitor on each view is a different setup and is not this row. Consent timing is not tested here.

Forecast fetched on your serverNo outside weather page documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Weather Atlas Widget

This row covers Weather Atlas Widget when the forecast is fetched on your WordPress server and rendered as HTML with local weather icons. Links to Weather Atlas pages are not a site-wide weather script. Consent timing is not tested here.

Forecast fetched on your serverNo outside weather page documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Weather Forecast Widget

This row covers Weather Forecast Widget when a city or coordinates are saved. The page asks your WordPress site for the forecast; your server then calls OpenWeatherMap and may cache the result. The owner API key stays in plugin settings. A never-cache setting is a different refresh rate, not a visitor-browser call. Consent timing is not tested here.

Forecast fetched on your serverNo outside weather page documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
wp-forecast

This row covers wp-forecast when a location is saved and the forecast is fetched on your WordPress server from Open-Meteo or OpenWeatherMap. AccuWeather is no longer a documented source. The optional visitor-location setting that sends the visitor IP to ipstack.com is a different setup and is not this row. That IP lookup is not a browser location permission prompt. Consent timing is not tested here.

Forecast fetched on your serverNo outside weather page documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
30YearWeather Widget

This row covers 30YearWeather Widget when a city shortcode or block is published. The page loads an iframe from 30yearweather.com, so the visitor browser contacts that host. This is not a server-side cached forecast. Consent timing is not tested here.

Outside weather service30yearweather.comNot assessedNot tested
  • None

What this table does and does not prove

This table describes the named weather widget setups. It does not show what loads on your site. Where no outside weather page is documented, that applies only to the setup described. Other page requests are not covered. A server-side forecast fetch uses the site server, not a visitor-browser call to the weather vendor. Looking up a visitor IP on the server is not the same as a browser location permission prompt. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long weather-service logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-weather-plugin-privacy