Privacy policy

Effective October 23, 2026. This covers https://cryptofeed402.site, its HTTP API and its remote MCP server at /mcp.

What we do not collect

• No accounts, sign-ups, API keys, emails or passwords.
• No cookies, trackers, analytics scripts or ads on our pages.
• We never see or hold your wallet's private keys. Payments are signed by your own x402 client.

What we log

• Web server access log: IP address, time, requested URL, user agent and referrer. Authorization, cookie and payment headers are removed before logging. Kept for up to 7 days, then deleted.
• Application log: path, status, response time, user-agent family and an optional ?ref= tag. No IP addresses.
• Payment ledger: for each settled payment, the route, amount, asset, network, transaction hash, payer wallet address, user-agent family and ref tag. This information is already public on the Base blockchain.
• Free feedback and coin requests (POST /request/asset, POST /feedback/schedule): what you send, plus a salted one-way hash of your IP used only for rate limiting and de-duplication. Only aggregates are published.

How we use it

To run and secure the service (rate limits, abuse prevention, debugging), to count usage by route and referral tag, and to issue signed receipts. We do not sell, rent or share this data for advertising.

Third parties

• Payments settle in USDC on Base through the Coinbase Developer Platform x402 facilitator, which receives the signed payment you send.
• Market data comes from public sources (Hyperliquid, OKX and public news headlines). Your requests are not forwarded to them.

Changes and contact

If this policy changes, the effective date above changes too. Questions or deletion requests: open an issue on our GitHub. Please do not post wallet keys or other secrets there.

cryptofeed402 | /llms.txt | Privacy | Support