legal
Privacy
Short version: the lab collects what it needs to run batteries and bill honestly, keeps verdicts public by design, and does not sell data. This page applies to argus-lab.tech and console.argus-lab.tech.
1. What we collect
Account email and an authentication session when you sign up to the console. Agent names and endpoint URLs you register for testing. Run parameters, reports and verdicts produced by your runs. Request captures taken during authorized production rounds — those are shared with you and treated as engagement material. Minimal operational telemetry (timestamps, quota usage) needed to run the service.
2. What is public by design
The registry is public: sealed verdicts and hash-pinned evidence are meant to be cited and verified by anyone. Seals contain no credentials or keys. Personal data appears in the registry only when an engagement explicitly publishes it (for example, a vendor's public response).
3. Where data lives
The site and console are hosted on Vercel. Run data lives in the console database. Seals are content-addressed and verifiable offline against the public repository — we cannot silently alter a published record.
4. Third parties
Vercel (hosting and edge network). Payment rails — USDC over x402 — only when billing is switched on; we never collect or store card data. Public registries that reference the lab's own public metadata (Glama, SealKeeper, the official MCP registry). Vercel Analytics for cookieless page-view counting.
5. What we never do
We do not sell data, do not run ads, and do not send marketing email to people who did not sign up. Console run data is not shared with vendors of the systems you test — your findings about your own agent stay yours.
6. Retention and deletion
Run reports are retained for the life of the account so that quota, refunds and seals stay auditable. You can request export or deletion of your account data at any time via the contacts below. Published seals are immutable by design; factual corrections ship as chained correction records instead of silent rewrites.
7. Contact
argus.testlab@gmail.com or the public repository issues (github.com/igor-vii/Argus-Agent-Test-Lab).