The parameters you send (state, name, entity_id, domain), your API key or x402 payment, and your IP address.
What we keep
Usage ledger, one row per verification: time, request ID, rail (API key, x402 or MCP), API key ID, state, result, whether it was charged and the price, whether it was reported to Stripe, and for x402 the settlement status and transaction hash. The ledger does not store the name, entity ID or domain you asked about.
API keys: only a SHA-256 hash of each key, a label, and a Stripe customer ID if you are billed through Stripe.
Cache: registry responses are kept in memory for up to an hour, then dropped.
Rate limits: your IP address or API key ID is counted in memory for one minute.
No retention schedule or automatic deletion is set up yet. The ledger is kept as the billing record.
Who else sees what
State open-data portals (Colorado, Connecticut, Texas, New York, Oregon) receive the name or entity ID being looked up, sent from our server.
Stripe receives your Stripe customer ID and one usage event per charged answer, with its time.
The x402 payment facilitator (Coinbase CDP or PayAI) receives your payment to verify and settle it.
The website you name in domain receives a request from our server.
Our hosting platform may record standard request metadata under its own terms.