Privacy policy

Agent402 has no accounts, no signups, no cookies, and no browser trackers or ad trackers on its pages. The entire server is open source, so every claim below is verifiable in code.

What we process, and why

• Tool inputs. The data you send to a tool (text to hash, a URL to render, …) is processed in memory to compute the response and is not stored - with one deliberate exception: the /api/memory tools, whose purpose is storage (see below).
• IP addresses. Used for free-tier rate limiting (kept in process memory for up to one hour) and in standard, short-lived operational logs (request path, status code) for abuse prevention and debugging.
• AI gateway inputs. Prompts and inputs sent to the /v1 endpoints (chat, embeddings, images, speech) and other AI-proxy tools are forwarded to the upstream model provider (OpenAI, or the model operator serving the request via OpenRouter) to generate the response, subject to that provider's own privacy terms. We don't store gateway inputs or outputs beyond short-lived caches (minutes) that make repeated identical calls cheaper.
• Payments. We never see card numbers, names, or emails - there are none. Payments settle in USDC on the public Base blockchain (or Solana, Polygon, Arbitrum, Monad, Stellar, Algorand - or USDG on Robinhood Chain) via the x402 protocol; wallet addresses, amounts, and timestamps are public on-chain by the protocol's design, not collected by us. Payment verification is performed by the payment facilitators (Coinbase CDP and per-chain facilitators).
• Operational telemetry. The server records service events (tool called, payment settled, errors) with metadata - tool name, HTTP status, price, settlement chain, and the paying wallet address (already public on-chain) - in a server-side analytics tool (PostHog). This is used to run the service: reliability, abuse prevention, and knowing what sells. It never includes tool inputs, prompts, outputs, cookies, or browser fingerprints.
• Payment metadata. An x402 payment token can carry optional annotation fields (a resource URL, a description, a reason string) that some buyers use to label a purchase. Agent402 reads only the cryptographically-signed payer wallet address from the token - the exact field the settlement authorization covers, and one that is already public on-chain. Those annotation fields are never parsed, logged, or retained, so a buyer that inadvertently placed personal data in them does not expose it to us. Data-minimisation by construction, not by policy.
• Memory tools. Data written via /api/memory is stored on our server keyed to the paying wallet, readable only by that wallet (or wallets it explicitly grants), until the owner deletes it or its TTL expires. A tamper-evident audit log of accesses is kept for the namespace owner.

Third parties

• Tools that fetch external URLs (extract, render, screenshot, …) contact those sites from our server with the URL you provided.
• /api/search forwards the query to the Brave Search API to produce results.
• Hosting is on Railway. On-chain settlement is on Base (Coinbase CDP facilitator).
• We do not sell or share data with anyone for advertising or any other purpose.

The MCP connector (https://agent402.tools/mcp)

The hosted connector is anonymous: requests carry no identity beyond the connecting IP, which is used only for rate limiting as described above. Tool calls made through it are processed exactly like the HTTP API.

Retention

Operational logs are short-lived (platform default, days not months). Rate-limit counters live in process memory only. Memory-tool data persists until deleted by its owner or TTL expiry. Aggregate, non-personal counters (total calls served per tool) are kept for the public /api/stats page.

Abuse & legal requests

Wallet addresses associated with terms violations may be blocked and retained on a blocklist for as long as needed to enforce the block. We disclose information and preserve records in response to valid legal process, and report content where the law requires it. Requests and abuse reports: mike@agent402.tools.

Operator & contact

Agent402.Tools is operated by Havok Holdings LLC. Contact: mike@agent402.tools, GitHub issues, or @Agent402Tools on X.