Privacy Policy

x402-safety-kit · Operator: MK Career Planning · Last updated: 2026-11-01

1. What we handle

• Payer wallet address and transaction hash of each paid call (x402, USDC), with the tool name, price, network and time.
• Results of paid calls (the response body), so that you can fetch them again with get_receipt if the response was lost after payment. The stored result includes the inputs you sent (for example the dates and places of an itinerary).
• Retry check value: while a paid result is kept, we also keep a keyed one-way value of the tool name and the arguments (HMAC-SHA256 with a secret key), used only to recognise a retry with the same payment. It cannot be turned back into the inputs without the key, and it is deleted together with the result. Calls that are not settled (paused, refused or failed) keep no such value. Records made before 2026-11-01 may hold an unkeyed SHA-256 hash of the arguments instead, which is deleted on the same schedule.
• Free tool usage: daily counts per tool and channel, and a daily estimate of distinct callers computed from a one-way hash of the first three parts of the IP address with a key that changes every day. We do not store free tool inputs in our database.
• Request logs: we do not keep Cloudflare's automatic request logs, so caller IP addresses, locations derived from them, and User-Agents are not logged by us. For fault investigation we keep only the log lines our own code writes (errors and summaries of background jobs), which are written not to include IP addresses, request headers, query strings or request bodies; Cloudflare may attach basic details of the call to them, such as the request method and the path without the query string (values inside the path, for example a receipt_id, can appear). Cloudflare Workers Logs keeps these lines for up to 7 days. Cloudflare may still process connection data to deliver the service under its own policy.
• MCP responses: when you use the MCP endpoint, a response (which can include your inputs) may be held briefly in Cloudflare Durable Object storage until it has been delivered, so that a dropped connection can resume. It is normally removed as soon as it has been delivered.
• IP addresses: we do not store IP addresses in our own database. Cloudflare, which hosts this service, processes IP addresses and request metadata to deliver the service and may keep them in its logs, under Cloudflare's own policy. To enforce per-client rate limits on free calls, we pass a one-way hash of your IP address and the first 64 characters of your User-Agent to Cloudflare's rate-limiting counters, which only count requests over about a minute; we do not store either.

We do not ask for names, email addresses or accounts to use the API.

2. Why

• To process payments, prevent double charges (idempotency) and let you re-fetch a paid result.
• To keep accounting records and to enforce daily limits.
• To measure aggregate usage. Our own monitoring payments are excluded from customer figures.

3. Third parties

• Cloudflare (hosting, storage, logs).
• Payment facilitator that verifies and settles x402 payments: Coinbase Developer Platform (api.cdp.coinbase.com), or PayAI (facilitator.payai.network) or Dexter (x402.dexter.cash) as a fallback. When a paid HTTP endpoint is settled through Coinbase, Coinbase may list that endpoint (not you) in its public x402 Bazaar catalog. The facilitator receives the signed payment, which includes your wallet address.
• Public blockchain: payments settle on Base. Wallet addresses, amounts and transaction hashes on a public blockchain are public and permanent; neither we nor anyone else can delete them.

We do not sell personal data and do not use it for advertising.

4. Retention

• Results of paid calls and their retry check values: 30 days after settlement, then deleted together (get_receipt then returns RECEIPT_NOT_FOUND).
• Payment records (wallet address, transaction hash, amount, tool, time): 7 years for accounting, then deleted.
• Free tool daily counts: kept as aggregate statistics.
• Deleted data: after we delete data (at the end of a retention period or on request), it can remain recoverable through our database provider's point-in-time recovery (Cloudflare D1 Time Travel) for up to 30 days, after which it is gone.
• Request logs: up to 7 days (Cloudflare Workers Logs). Other Cloudflare logs: according to Cloudflare's retention settings.

5. Requests and contact

To ask about or request deletion of data linked to your wallet address, contact: mk.career.planning@gmail.com
Please send the wallet address and, if possible, the receipt_id or transaction hash. We can delete stored results; payment records required for accounting are kept for the period above, and data on the blockchain cannot be deleted.

6. Disclaimer

This service reads the x402 payment request you send (and, where a comparison tool is offered, the values you supply). It gives no financial, investment or security advice and makes no judgement on authenticity or whether to pay. It does not sign, approve or move payments and never holds keys. The payment request you send is processed in memory; for paid calls only a hash of the arguments and the result (for get_receipt) are stored, as described above. See the Terms of Service.

7. Changes

We will update this page and its date when this policy changes. See also Support and the Terms of Service.