Privacy and data handling
This notice covers the DopamineDesk Agent Data Arcade website, paid API products, and the companion MCP client.
What the service receives
We receive the request parameters and content you intentionally send to a product. Paid requests may also include a public wallet address, transaction identifier, payment authorization, invoice identifier, amount, and settlement status. If you buy agent credit, we store the agent name you provide, a one-way hash of the bearer token, its balance, status, and expiration.
How request data is used
Request data is used to execute the selected product, return its result, prevent payment replay, enforce limits, secure the service, and diagnose failures. Some products query the external source named on their product page, so the parameters necessary for that query are sent to that source. Do not submit secrets, regulated data, or personal data unless the product clearly requires it and you are authorized to do so.
Payments and public networks
x402 payments settle in USDC on Base through the advertised facilitator. Blockchain transactions and wallet addresses are public by design and may remain visible permanently. The service keeps payment and invoice records needed for delivery, accounting, credit balances, and replay protection.
Analytics and infrastructure logs
Marketplace funnel analytics are stored as daily aggregate counts, including page views, product views, previews, payment challenges, attempts, successes, revenue, and broad actor class. Settled payments are deduplicated using one-way transaction and payer hashes so controlled activity can be separated from external customer sales without storing raw payer addresses in the analytics ledger. We measure repeat purchasing by hashed payer and UTC date. A settlement may retain a recognized campaign label, referring hostname, and broad client-software label. These are unverified source hints, not proof of who referred a buyer. Full referring URLs, raw user-agent strings, request bodies, and payment signatures are not retained in this analytics record. Public metrics expose aggregates, not payer hashes. Our application analytics do not store raw IP addresses. Hosting and security providers may process ordinary request metadata, including IP address and user agent, under their own operational logging and retention practices.
Sharing and sale of data
We do not sell request data or use it to build advertising profiles. Data is shared only with infrastructure, payment, and named product-source providers as needed to operate the service, comply with law, or protect the service and its users.
Retention and security
Aggregate analytics, payment replay records, and agent-credit ledgers are retained as operational records. Other request data is not intentionally stored by the application after the response unless a product explicitly states otherwise. No system is risk-free, so keep credentials out of request bodies and use the minimum data needed.
Your choices
You can inspect a live contract proof before paying, avoid submitting optional personal information, and stop using the service at any time. For a privacy or data-handling question, open a private contact request through the support channel linked from the public MCP repository. Do not post secrets in a public issue.