The provider list is intentionally small.

WeatherNext depends on a short set of infrastructure and data providers to deliver the private weather dashboard. These providers support hosting, authentication, map display, weather lookups, browser app delivery, and basic request handling. The app does not use a payment processor, ad network, or public account marketing stack.

This page is a practical disclosure, not a legal contract. It records the services a user or crawler should expect to see when the production app loads. If the app changes providers, the disclosure should be updated before relying on the new service for normal production traffic.

The important boundary is between the public explanation pages and the private dashboard. Public pages are static and informational. The dashboard is interactive, authenticated, and dependent on provider requests for maps, forecasts, alerts, and environmental signals.

Current providers

Cloudflare: static hosting, CDN delivery, DNS, request handling, and security headers.
Google Firebase: Google sign-in, authentication state, and allowlist-gated access.
Mapbox: interactive map rendering, map tiles, geocoding context, and map controls.
Weather and environmental APIs: forecast, alert, air quality, pollen, solar, and astronomy context.
Google Fonts: public font files used by the WeatherNext interface.

Data involved

Provider requests may include technical metadata such as IP address, browser user agent, requested route, timestamp, authentication state, and selected map or weather location. Location-related requests are necessary for forecast and map features, so users should avoid entering locations they do not want processed by the underlying weather or map providers.

Browser preferences and saved locations are intended to stay local where possible. The authenticated app boundary exists to keep the dashboard private, while these public pages explain the infrastructure that supports the project.

Because weather and map features depend on live provider data, disabling every third-party request would disable the app's main purpose. The goal is to keep the provider list understandable and limited, not to pretend a live weather dashboard can run without external weather, auth, and map services.