Skip to main content
WeatherXM

Privacy policy

Last updated: November 2026 · WeatherXM AG & WeatherXM Entities

1. Introduction & Scope

WeatherXM ("we", "our", or "us") provides meteorological hardware, mobile applications, web explorer interfaces, forecast accuracy benchmarking (fact.weatherxm.com), AI Model Context Protocol (MCP) connectors (fact.weatherxm.com/mcp), data APIs, and decentralized physical infrastructure services. This Privacy Policy explains what data we collect, the purposes of processing, categories of recipients, data retention timelines, and the controls available to you when you visit weatherxm.com, use our mobile apps, operate a WeatherXM station, or query our AI/MCP tools.

2. Station Location & Privacy Masking

Weather observations (temperature, pressure, humidity, wind, rainfall) are public physical environmental metrics. However, to protect the private residential addresses of station owners:

  • Exact GPS installation coordinates are never published on public explorer maps or public REST APIs.
  • Public station locations are obfuscated and aggregated using Uber’s H3 geospatial hierarchical hexagonal indexing system (typically H3 resolution 7, ≈5.2 km²).
  • Only cell-level hexagon centroids are displayed publicly to prevent identification of private homes and rooftops.
  • Authenticated station owners can view their own station's exact configured coordinates within their private mobile app account for installation management and alignment.

3. Personal Information & Categories of Data We Collect

We collect only the minimum data necessary to deliver our services, process hardware orders, or answer benchmark queries:

  • Account Data: Email address, encrypted password hash, and user preferences when registering an account on our mobile or web applications.
  • Order & Shipping Data: Name, billing/shipping address, and contact phone number when purchasing hardware through our official store. Payment card credentials are processed directly by PCI-DSS certified payment processors (Stripe) and are never stored on WeatherXM servers.
  • Device Metadata: Station serial numbers, firmware versions, battery voltage telemetry, and signal strength (RSSI/SNR) for device health and diagnostic support.

4. FACT Benchmark & AI MCP Connector (fact.weatherxm.com/mcp) — Tool Inputs, Outputs & Telemetry

The WeatherXM FACT MCP Connector and REST API provide public, unauthenticated, read-only access to historical weather forecast accuracy benchmarks across 45 numerical and AI weather models.

  • Current Tool Inputs Collected: When you or an AI assistant invoke our MCP tools (get_best_forecast_model, get_fact_leaderboard, check_ground_truth_coverage, and get_model_head_to_head), the service receives only the task-specific parameters required to compute the benchmark response: geographic coordinates (lat, lon), ISO-2 country code (country), weather parameter (variable: temperature, wind_speed, wind_direction, precipitation, humidity), forecast lead time (lead_day: all or 0–7), commissioned-model filter (exclude_commissioned), model list (models: up to 10 model IDs), or public station/report identifier (station_or_report_id).
  • Tool Outputs Returned: The tools return only aggregated, non-personal meteorological benchmark data: model accuracy rankings, Mean Absolute Error (MAE), Root Mean Square Error (RMSE), categorical precipitation skill scores (HSS, POD, FAR, CSI), win rates, H3 cell identifiers, and ground-truth station coverage counts.
  • H3 Spatial Quantization & Anonymous Demand Heatmap Logging: Exact lat/lon coordinates passed to MCP tools are quantized in-memory at the network edge into a coarse Uber H3 Resolution 7 hexagon (h3_cell_r7, ≈5.2 km² area) solely to look up pre-computed benchmark shards. Raw lat/lon coordinates are immediately discarded and are never written to disk or databases. To identify global weather-observation blind spots and prioritize where new weather stations are needed, we log an anonymous demand record (mcp_demand_logs) containing only transport, tool, h3_cell_r7, country, variable, lead_day, exclude_commissioned, station_or_report_id, coverage_status, and champion_model.
  • No Personal Identifiers or Chat Logs: The FACT MCP server does not require sign-in and never collects, logs, or stores user names, email addresses, account tokens, IP addresses, browser cookies, or AI conversation transcripts.

5. Local-First Station Operation

The WeatherXM D2 Mesh weather station supports local-first operation. You can consume your weather telemetry entirely via local LAN REST endpoints and MQTT topics without creating a cloud account or transmitting data to WeatherXM servers.

6. Purposes of Processing & Categories of Recipients

We process data strictly for the following purposes and share it only with essential service recipients:

  • Purposes of Use: (a) Fulfilling hardware store orders and customer support; (b) Operating weather station telemetry and quality-of-data (QoD) verification; (c) Serving historical forecast accuracy benchmarks via web and AI/MCP tools; (d) Aggregated, anonymous H3 coverage-gap heatmap analysis to guide station network expansion; and (e) Infrastructure security, rate limiting, and abuse prevention.
  • Categories of Recipients: (a) Cloud & Edge Infrastructure Providers: Cloudflare (Pages, Workers, and D1 edge database hosting weatherxm.com and fact.weatherxm.com/mcp) and Google Cloud / AWS for core telemetry storage; (b) Payment & Fulfillment Partners: Stripe (payment processing) and international shipping carriers (DHL, FedEx, UPS) strictly for hardware order delivery; (c) Scientific & Forecast Partners: Aggregated, anonymized H3 meteorological observations shared with climate researchers and forecasting institutions. We never sell personal data or share MCP tool query logs with advertisers or data brokers.

7. Data Retention Timelines

  • Raw MCP Tool Coordinates (lat/lon): 0-day retention (ephemeral). Processed exclusively in volatile worker memory to resolve the H3 Resolution 7 cell and discarded immediately after the HTTP response.
  • Anonymous MCP Demand Heatmap Logs (mcp_demand_logs): Because these records store only coarse H3 Resolution 7 hexagons (≈5.2 km²) and benchmark query parameters with zero personal or network identifiers, they are retained as de-identified spatial demand telemetry for ongoing seasonal and long-term station coverage planning.
  • Edge Security & Access Logs: Standard Cloudflare edge security logs are retained for up to 30 days for DDoS mitigation and abuse prevention.
  • User Account Data: Retained for as long as your mobile or web account remains active, and permanently deleted within 30 days of a verified account deletion request.
  • Hardware Order & Billing Records: Retained for the statutory tax and accounting period required by Swiss and EU law (up to 10 years).

8. User Controls, Privacy Rights & Contact

You have clear controls over your data across all WeatherXM products and integrations:

  • AI & MCP Connector Controls: Because the WeatherXM FACT MCP connector is unauthenticated and stores no personal identifiers or IP addresses, you can disable or disconnect the plugin at any time directly within your AI client settings (ChatGPT, Claude, Gemini, or Codex) without needing to request account deletion.
  • Station & Account Controls: You may operate supported stations in local-only LAN mode, mask station coordinates via H3 cells, or delete your mobile app account at any time from within the WeatherXM app settings.
  • GDPR & Data Subject Rights: Under GDPR, Swiss FADP, and applicable privacy laws, you have the right to request access to, rectification of, erasure of, restriction of processing of, or portability of your personal data, as well as the right to object to processing. To exercise these rights or ask privacy questions, contact our privacy team at hello@weatherxm.com.