Privacy

Last updated: October 1, 2026

This page describes the data handled by Agent EVM State Batch when a customer or software agent requests read-only blockchain data or sends a support message.

Data Used to Provide a Batch

Your request contains the checks you choose, including any public wallet, token, spender, or contract addresses you provide. We validate the request and send supported read-only JSON-RPC calls to dRPC public nodes. We store a request fingerprint, the completed response, payment transaction details, payer address, status, and timestamps so the paid result can be delivered and recovered. The request body itself is not stored as a raw body.

Paid result data is available for 30 days through its request ID. The request ID is a bearer recovery key: anyone who obtains it may retrieve that paid response while it is retained. Keep it private. Settlement records remain after the response expires for service accounting and reconciliation.

Wallet and Payment Data

The checkout page connects to your chosen wallet to request public account information and, only after you approve, a payment authorization for the quoted Base USDC amount. The page does not receive your private key or recovery phrase. The service processes the payer address, transaction hash, payment amount, recipient, and network needed to verify and reconcile settlement.

Support Messages

If you use Support, we receive the message and any reply email address you choose to include. The reply address is used to respond and is not shown publicly. Do not include passwords, private keys, recovery phrases, or other secrets.

Service Providers and Retention

Cloudflare hosts the site, Worker, database, rate limiter, and support email delivery. dRPC provides upstream blockchain RPC responses. The dRPC API key and support destination are kept in server-side configuration and are not included in public page code. Request and result payloads expire after 30 days; account and settlement records may be retained longer where needed for reconciliation and service accounting.

Data Quality and Security Limits

Blockchain reads are provider-reported responses, not cryptographic proofs. Public addresses and blockchain transactions are visible on their networks. No online service can promise absolute security; the service is designed not to request or store wallet secrets.