Privacy Policy

1. Introduction

Smarter Weather LLC (“Smarter Weather”, “we”, “our”, or “us”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and protect your information when you use our website and services.

2. Information We Collect

The categories of information we collect depend on how you use the Service.

All visitors

• Analytics Data: We use Google Analytics to collect aggregated information about how visitors use our site. This includes usage data such as pages visited, time spent, and referring URLs.
• Server Logs: Our servers automatically log standard request information such as the URL requested, your IP address, browser or client type (user agent), and the date and time of access.

Consumer account holders (web and mobile apps)

• Account Information: When you create a consumer account (for example, to receive personalised alerts or to use the Chat experience), our authentication partner Clerk collects and stores identifiers such as your email address, display name, and authentication metadata on our behalf.
• Preferences and Locations: Saved locations, including a home address if you provide one, units, and notification preferences you configure inside the app.
• Feature Usage: Aggregated counters of how often you use metered features (for example, Chat messages) for rate limiting and abuse prevention.

Developer account holders

• Account Information: Developer accounts are issued through Clerk and include the same identifiers as consumer accounts, plus developer-specific metadata (organisation name if provided, subscription tier, and billing customer ID).
• API Keys and Tokens: We store a cryptographic hash of every API key and OAuth token you issue, along with metadata (name, prefix, scopes, last-used timestamp). We never store the raw key value after creation; it is shown to you once and not retrievable thereafter.
• Billing Information: Payment method, Hosted Checkout session data, invoice history, subscription status, and metered usage totals are processed by our billing provider, Stripe. For keyless x402 payments we also process wallet and payment-network identifiers through Stripe, and we record the paying wallet address as the account identifier on the usage records for those calls. We do not store full payment credentials on our systems.
• API and MCP Usage Telemetry: For each request we log the API key identifier (not the raw key), the endpoint or tool called, timestamps, response status, latency, the client's user agent, and the request's query parameters (including those an MCP tool sends to our API), plus counters used for billing and abuse detection. Request logs for our API record coordinates rounded to two decimal places (about 1 km) and replace place names, addresses, ZIP codes, and unrecognized parameters with a placeholder. Some diagnostic error and trace data may still contain precise locations, for up to 30 days, while we extend this rounding to it. Request bodies are not logged by default. Agent-initiated MCP and REST calls generate the same telemetry as human-initiated calls and are attributed to the account whose credentials or x402 payment settled the request.
• Trial Keys: When an app, or the sandbox key button on our developer portal, requests a keyless trial key, we store with that key the app name it reports (or, if it reports none, only the product name from its user agent, such as "curl", never the full user agent string) and any version it reports. If the key is claimed into an account, these stay with the key like other API key records; otherwise they are scheduled for deletion when the trial's claim window ends (currently 7 days) and are typically removed within a few days after. For abuse limits we keep a keyed hash of your IP address (IPv6 addresses are first shortened to their /64 network), never the address itself; it is scheduled for deletion after about two days and typically removed within a few days after that. The portal keeps a sandbox key in your browser's session storage, which clears when you close the tab.

3. How We Use Information

• To provide, operate, and improve the Service.
• To authenticate your account, authorise requests, and enforce rate limits and quotas.
• To meter usage, calculate invoices, and process payments through Stripe, including Hosted Checkout for paid developer tiers and keyless x402 (USDC on Base) for pay-per-call access.
• To analyse usage and trends, and to operate, secure, and improve the Service using de-identified and aggregated telemetry. We do not sell personal information.
• To detect, prevent, and address technical issues, security incidents, or abuse.
• To communicate with you about service changes, incidents, billing events, and policy updates.

4. Information Sharing and Disclosure

We do not sell your personal information. We share information only with the service providers (subprocessors) listed below, who act on our behalf to operate the Service, and as otherwise required by law.

Our current subprocessors are:

• Amazon Web Services (AWS) — hosting, storage, and compute for our services, including a first-party product event lake (pseudonymous identifiers and product usage events; no message or prompt text; not sold). All production data processing happens in the us-east-1(Northern Virginia) region.
• Clerk — user authentication, account management, and identity for both consumer and developer accounts.
• Stripe — billing, payment processing, Hosted Checkout, subscription management, usage-based metering for paid developer tiers, and keyless x402 settlement. Full payment credentials and wallet / payment-network identifiers are processed by Stripe, not stored as payment credentials by Smarter Weather.
• Google Analytics — aggregated site and app usage analytics.
• OpenAI — large language model inference for some AI features (including weather-data enrichment). Only the information required to produce the result (for example, source text and relevant weather context) is sent to OpenAI; your account identifiers are not shared for model training.
• Anthropic — large language model inference for the Chat experience, flagship agent, and related AI features. Only the information required to answer your query (for example, your question and relevant weather context) is sent to Anthropic; your account identifiers are not shared. Per Anthropic's commercial terms, API data is not used to train Anthropic models.
• TypeSafe AI — System One (Jev) structured decision inference for agent routing, response evaluation, trigger significance gating, and selected weather-product classification. Only the information required for an enabled decision is sent to TypeSafe: 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 are shared. Per TypeSafe's Master Customer Agreement, input is not used to train TypeSafe models.

We may also disclose information if required by law, regulation, or valid legal process, or to protect the rights, property, or safety of Smarter Weather, our users, or others. A canonical, versioned list of subprocessors intended for enterprise buyers and developer customers is maintained at /legal/subprocessors.

5. Data Retention

• Analytics data is retained according to Google's data retention policies.
• Server logs are kept for security and troubleshooting and then deleted automatically: API request logs after 14 days, and most other server, network, and firewall logs within 90 days; some operational logs are kept longer. Requests our firewall blocks, challenges, or flags as suspicious are logged with the full request, including the URL, IP address, and request headers.
• Account data (consumer and developer) is retained for the life of your account and deleted within a reasonable period after account closure, subject to legal and tax retention requirements.
• API key records, x402 usage records, and usage telemetry are retained for the life of the key, and historical metered usage is retained for as long as required by billing, tax, and audit obligations (typically seven years).
• Billing records held by Stripe are retained according to Stripe's policies and applicable financial regulations.

6. Your Rights

Depending on your location, you may have the right to access, correct, or delete your personal information, subject to applicable law. To exercise these rights, please contact us at alex@smarterweather.com.

7. Data Residency and International Transfers

Smarter Weather is based in the United States. All production data for the Service — including consumer account data, developer account data, API key records, usage telemetry, and billing metadata — is processed and stored in AWS us-east-1 (Northern Virginia). We do not currently offer data residency in other regions.

If you access the Service from outside the United States, your information will be transferred to and processed in the United States by Smarter Weather and its subprocessors. By using the Service, you consent to this transfer.

8. Children's Privacy

Our services are not directed to children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe we have collected such information, please contact us.

9. California Residents

If you are a California resident, you have rights under the California Consumer Privacy Act (CCPA). We collect limited categories of personal information, such as identifiers (e.g., IP address) and usage data. We do not sell your personal information.

10. Cookies and Tracking Technologies

We use cookies and similar technologies provided by Google Analytics to analyze usage of our website. You can control cookies through your browser settings.

11. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the last updated date above.

12. Contact Us

If you have any questions about this Privacy Policy, please contact us: