The app is private by design.

WeatherNext is built for a small authorized guest list. The public site does not sell accounts, run ads, or invite open signups. Access is controlled through Google sign-in and an allowlist in the app code. If you are not on that list, the dashboard should not expose the private weather interface to you.

The app may use browser storage for preferences such as theme, saved locations, selected units, and dashboard settings. Browser storage is tied to the device and browser you use. Clearing site data, switching browsers, or using private browsing can remove local settings.

WeatherNext uses provider-backed services for authentication, map rendering, and weather or environmental data. Those services may process technical request details such as IP address, user agent, requested URL, approximate location query, authentication state, and timestamps so the app can load and protect the dashboard.

The public pages can be read without signing in. The private dashboard requires JavaScript because the app depends on client-side authentication, browser state, and interactive map controls. If JavaScript is disabled, the project should still explain its purpose, but it should not expose saved dashboard data or private app controls.

Location and forecast data

Weather data depends on the location or map area you choose inside the app. Avoid saving locations you do not want associated with your browser profile. The app is meant for personal weather awareness and planning, not for storing sensitive location histories or emergency-response records.

Forecasts, alerts, air quality, pollen, and map layers come from external data sources and can be delayed, incomplete, or unavailable. For emergencies, use official alerts and local guidance first.

Treat saved locations like any other personal planning data. They may be ordinary places, but repeated checks can still reveal routines. WeatherNext is designed for convenience, not for keeping a sensitive location history.

Public trust pages

The current infrastructure and data-provider disclosure is published on the WeatherNext subprocessors page. If the app changes providers or adds a new production service, that page should be updated.

Contact about the public project surface should go through Jonathan's main website. The WeatherNext app itself is not a public support portal or emergency communication channel.