Public data
Wallet addresses, listing metadata, keyword bids, payment amounts, transaction identifiers, and timestamps are public by design. They are published because they explain and reconstruct ranking.
Operational data
The service processes request identifiers, coarse server timing, error details, and keyed hashes of network addresses for rate limiting. Raw payment authorizations and credentials are not written to application logs. Expired rate-limit records are removed automatically.
What is not requested
DefaultBench does not require a human name, email address, telephone number, account profile, advertising cookie, or cross-site tracking identity. It does not use invasive client analytics.
Infrastructure
Hosting, PostgreSQL, Base RPC, and the x402 facilitator process the data necessary to deliver their services. Their independent policies apply. Retention is limited by operational, security, legal, and backup requirements.