Docs navigation
REST API
Weather MCP
Agents as developers
Subprocessors
Last Updated: 2026-09-21
Smarter Weather LLC uses the third parties listed below to operate the developer platform and the consumer apps. This list is maintained for developer due diligence and enterprise procurement review. It supplements our Privacy Policy and our Developer Terms. Agent-initiated MCP and REST calls generate the same operational telemetry as human-initiated calls and are attributed to the account.
Current subprocessors
| Subprocessor | Purpose | Data processed | Processing region |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Hosting, compute, storage, networking, and operational logging for the Developer Platform. | All Developer Platform data in transit and at rest, including account records, API key records, usage telemetry, cached weather responses, and first-party consumer/app product events stored in the same AWS account (S3/Athena) — not a third-party analytics system of record. | United States — us-east-1 (Northern Virginia) |
| Clerk, Inc. | User authentication, account management, and identity for both consumer and developer accounts, including support for MCP OAuth 2.1. | Account identifiers (email, name, authentication metadata), sign-in events, and session tokens. | United States |
| Stripe, Inc. | Billing, payment processing, Hosted Checkout, subscription management, usage-based metering for paid developer tiers, and keyless x402 (USDC on Base) settlement. | Billing contact information, payment method details and Hosted Checkout session data (stored by Stripe, not by Smarter Weather), invoice history, subscription state, metered usage totals, and wallet / payment-network identifiers for x402 settlements. | United States |
| Google LLC (Google Analytics) | Aggregated site and app usage analytics to understand how the marketing site and developer portal are used. | IP address (anonymised), user-agent, page views, referrers, and interaction events. No API request bodies or account identifiers are sent to Google. | United States and other Google processing regions |
| OpenAI, LLC | Large language model inference for some AI features, including weather-data enrichment. | The information required to produce the enrichment or feature result, including source text and relevant weather context. Account identifiers and API keys are not shared. Per OpenAI's API data policy, data sent to the API is not used to train OpenAI models. | United States |
| Anthropic, PBC | Large language model inference for the Chat experience, flagship agent, and related AI features. | The information required to answer your query, including your question and relevant weather context. Account identifiers and API keys are not shared. Per Anthropic's commercial terms, API data is not used to train Anthropic models. | United States |
| TypeSafe AI, Inc. | System One (Jev) structured decision inference for agent routing, response evaluation, trigger significance gating, and selected weather-product classification. | The information required for an enabled decision: a single user turn, a scored conversation excerpt, an operational summary (triggered conditions and plan settings), or a public weather-product excerpt. No account identifiers, API keys, full conversation history, or coordinates. Per TypeSafe's Master Customer Agreement §4.1, input is not used to train TypeSafe models. | United States |
Data residency
All production data for the Developer Platform — including developer account records, API key records, usage telemetry, and cached weather responses — is processed and stored in AWS us-east-1 (Northern Virginia). We do not currently offer processing in other regions; if you have a data-residency requirement that this does not meet, contact us before provisioning an account.
Upstream data providers
The following organisations supply the underlying weather data that the Developer Platform derives responses from. They are upstream sources rather than subprocessors of your personal data, but are listed here for transparency and are acknowledged on our Acknowledgements page:
- National Oceanic and Atmospheric Administration (NOAA) and the National Weather Service (NWS) — public-domain observations, forecasts, model output, and alerts.
- NOAA Open Data Dissemination on AWS — bulk access to NOAA datasets.
- OpenStreetMap contributors — geospatial reference data, used under the Open Database License.
Requests you make to the Developer Platform are fulfilled from our derived datasets and caches; we do not proxy your identity, API key, or request body to these upstream providers.
Change notification
We will update this page before engaging a new subprocessor that processes developer or customer personal data, except where a same-day replacement is required to maintain the service. You can subscribe to change notifications by emailing alex@smarterweather.com with the subject “Subscribe to subprocessor updates.” We retain the previous three versions of this page in our source-control history for audit purposes.
Data Processing Addendum (DPA)
A Data Processing Addendum covering our processing of customer personal data, including an up-to-date subprocessors list, is available on request for customers who need one for GDPR, UK GDPR, or CCPA purposes. Email alex@smarterweather.com with the subject “DPA request” or use the contact form.