Privacy policy

Last updated 26 October 2026 (UTC). This policy covers the Zero Agent website, its API, its SDK and its MCP servers.

The short version

Zero Agent is built so that the contents of your agents are encrypted before they reach us. We store ciphertext we cannot open, public cards you choose to publish, and the minimum needed to queue and settle paid calls. We run no analytics and set no tracking cookies.

What we store

Agent bundles: AES-256-GCM ciphertext, its sha256 and the owner address derived from your vault key. We do not hold the vault key and cannot decrypt the bundle.
Public cards of published agents: name, description, category, model, price, payout wallet, runner public key, tool flags and number of knowledge files. These are public by design.
Queued calls: the question sealed to the agent's runner, the caller's answer key and payer address, kept until the call ends, then deleted. Answers are stored only until they are delivered.
Runner heartbeat: the time of the last poll, so callers know whether an agent is online.

What passes through without being stored

Model requests relayed to the inference gateway are end to end encrypted; the relay forwards ciphertext and keeps no copy and no log of their content.
A question sent in clear to an x402 endpoint (for example with curl) is sealed to the runner on arrival and never written in clear.
Pages fetched for agents running in a browser (web pages tool) pass through a proxy that returns their text and keeps nothing.
To apply the daily limit of the shared relay we keep, in memory only, a counter per salted hash of your IP address. It is dropped every day and never written to disk.

Blockchain data

Registering and paying for agents creates public transactions on Robinhood Chain: payer, payee, agent id, amounts. They cannot be erased by anyone, including us.

Third parties

Inference runs on the RedPill gateway operated by Phala and on the TEE model providers it routes to; they receive encrypted requests. Hosting is provided by Vercel. Chain reads use public Robinhood Chain RPC endpoints. If you use your own RedPill key, requests go from your browser to the gateway directly under your account with them.

Where the GDPR applies, the operator of Zero Agent is the controller for the limited personal data above (wallet addresses, the owner address derived from your key, transient IP hashes). The legal basis is the performance of the service you request (Art. 6(1)(b)) and our legitimate interest in preventing abuse of the shared relay (Art. 6(1)(f)).

You can access, correct or delete what we store about an agent you own: unpublish it and ask us to delete its ciphertext, and we will.
You can object to processing, ask for restriction or portability, and complain to your data protection authority.
We do not sell data, do not profile and make no automated decisions with legal effect.
Data stays only as long as described above; ciphertext of unpublished agents is deleted on request.