What we store, and what we never do

• Your email address — your account identity and where pairing links are sent.
• A TOTP secret — proves human presence for sensitive actions. Stored encrypted and never shown again after enrolment.
• Agent keys — bearer tokens stored as SHA-256 hashes, along with the name you gave each agent so you can recognise and revoke it.
• Vault secrets— credentials you explicitly store, encrypted with AES-256-GCM under a per-workspace data key. One workspace can never decrypt another's secrets, even with database access.
• An audit log — every mutating tool call and every vault fetch, recorded with tool name, timestamp, and redacted arguments, scoped to your workspace.

• We don't sell or share your data with third parties.
• We don't read your vault values except as required to execute a tool call that you or your paired agent explicitly made.
• We don't use your data to train models.

Tool calls you make are forwarded to the provider you target (Stripe, GitHub, Cloudflare, and so on) using the credentials in your vault, under that provider's own terms. Infrastructure: Vercel (hosting), Neon (Postgres, with secrets encrypted at rest), and Resend (transactional email for pairing links).

Vault secrets are deleted immediately when you delete them (vault_delete) and are unrecoverable. To delete your whole workspace — keys, secrets, and audit history — email hello@pablomcp.com from your account address. Questions: the contact page.