Privacy

Last updated 2026-11-03

This policy covers MoneyTools services: the x402 API and MCP server (api.moneytools.dev, mcp.moneytools.dev, x402-pay-precheck.moneytools.workers.dev) and this guide site (moneytools.dev, agent-guide.moneytools.workers.dev). They are run on Cloudflare Workers.

What we store

Free-tier counter: a per-day count keyed by a truncated SHA-256 hash of your IP address (IPv6 grouped per /48) and the endpoint name. Rows older than about one day are deleted automatically.
Demo rate limit: an in-memory per-IP counter for the current hour. It is not written to storage.
MCP free allowance: a per-day count of free MCP tool calls, keyed the same way as the free-tier counter (truncated SHA-256 hash of your IP, IPv6 per /48; never the raw IP). Rows older than about one day are deleted automatically.
Prepaid credits: when you buy credits we store a SHA-256 hash of your API key (never the key itself), the pack, the remaining balance, call count, timestamps (created, activated, last used, expiry), and the paying wallet address and settlement transaction hash (needed for support and disputes; both are also public on-chain). We keep these records while the key is valid and for accounting afterwards; unpaid/unsettled pending keys are deleted after about one day.
Paid calls: x402 payments settle on a public blockchain (USDC on Base) through the PayAI facilitator. The payer wallet address and transaction hash are public on-chain. If you pass a ref referral address, we keep a ledger entry with that address, the payer address, the endpoint, the price and the time, so the referral share can be paid.
Referral link clicks (/go/<id>): one integer per link per UTC day, plus the aggregate usage statistics below. No IP, raw user agent, cookie, full referrer or query string is stored.
Aggregate usage statistics (API, MCP and /go links): daily counters only, one row per UTC day × endpoint × client category × HTTP status × source tag, holding a number. The client category is a coarse label derived from the User-Agent header (for example ai:claude, python:urllib, cli:curl, browser); the raw User-Agent is not stored. The source tag is the value of a utm_source, src or ref link parameter (a wallet address is recorded only as wallet-ref), or else just the hostname of the referring site. For MCP and A2A we also count the JSON-RPC method and tool name, never the arguments. No IP address, IP hash, cookie or request content is part of these statistics. Rows are deleted after 180 days.
Pay Gateway (pay.moneytools.dev, /v1/gateway): for each relayed payment we store a SHA-256 hash of your payment header (never the header, signature or authorization itself), your API key's 10-character prefix, the seller's hostname (not the full URL), network, amount, our fee, the seller's HTTP status and timestamps. The seller's payment terms are cached for up to 15 minutes, keyed by a hash of the method and URL. Request and response bodies pass through and are not stored. Our log lines contain only the seller host, status, fee and the first 16 characters of the hash.
Web-to-Markdown results: fetched public pages may be cached for up to 1 hour.
Email: if you write to support@moneytools.dev, we keep your message to answer it.

What we do not do

No accounts, no cookies, no advertising trackers, no sale of data.
Request contents (URLs, addresses, emails you ask us to check) are processed to answer the request and are not kept, except the 1-hour page cache above.

Third parties

Cloudflare (hosting; Cloudflare Workers Logs is enabled for debugging, so Cloudflare keeps request metadata such as URL, method, status and request headers, which can include IP address and user agent, for a few days per its own retention and policy; our own log lines contain no IP or user agent), PayAI (payment facilitator), public blockchain RPC providers, and the pages or APIs you ask us to check. Referral links lead to third-party sites with their own policies.

Contact

support@moneytools.dev — ask for deletion of any ledger entry or email that relates to you.