Privacy

Account data. Your email address, a username, a salted password hash held by our authentication provider, and the organizations you belong to with your role in each.

Agent identities. The Ed25519 public keys you register, their fingerprints, names and descriptions, and the capabilities you grant them. We never receive or store an agent’s private key.

Authorization requests. Every signed action request an agent submits: the action, its parameters, the signature, the nonce and expiry, the decision we made, the reason code, who approved or denied it, and when. Denied and rejected requests are kept too, because a complete record is the point.

Audit chain. A hash-linked sequence of events per organization. Events are append-only: neither you nor we can edit or delete an individual entry without breaking the chain.

Connections. Tokens you provide so Passport can execute actions on your behalf (today, Vercel). They are encrypted at rest with a key that is not stored in the database.

Operational logs. Request metadata such as IP address, user agent, timestamps and error traces, retained for a short period for security and debugging. Rate-limit counters key on a one-way digest of your address, not the address itself.

• The private keys of your agents or their runtimes.
• The prompts, model context or conversation of any agent.
• Your plaintext password.
• Anything from the systems an action targets beyond the result of that action.

Passport is built on the assumption that the model is untrusted input. We authorize what a runtime signs; we do not observe what a model thinks.

To make and record authorization decisions, execute allowed actions, sign receipts, publish the audit head, sign you in, send account emails (confirmation, password reset), and keep the service secure. We do not sell data, build advertising profiles or train models on your data.

Members of your organization see its agents, requests and audit events according to their role. Signed receipts are designed to be shared: anyone holding one can verify it against our published public key, and the receipt contains only the claims needed to do so.

Our infrastructure providers process data on our behalf: Vercel (hosting, edge network, logs) and Supabase (database and authentication). Data is stored in their US regions. We disclose data to authorities only when legally compelled and will tell you when we are allowed to.

Authorization requests and the audit chain are retained for as long as the organization exists, because their value is that they cannot be quietly removed. Operational logs are retained for 30 days. Connection tokens are deleted the moment you revoke the connection.

Organization owners can export everything the organization holds — agents (public keys only), projects, grants, rules, every request and decision, and the signed audit chain — and delete the organization outright, from the dashboard’s Settings tab. Deletion is immediate and removes the audit chain too; receipts already handed to other systems keep verifying because they are signed, not looked up.

To delete your personal account, email privacy@agentpassport.dev. We remove personal data within 30 days. Audit events in organizations you leave behind remain but are anonymized: actor identifiers are replaced with a fixed tombstone so the hash chain stays verifiable.

Wherever you are, you can ask us to access, export, correct or delete your personal data, or object to how we process it. Residents of the EU, UK, and jurisdictions with similar laws have these rights by statute; we extend them to everyone. Contact the address above and we will respond within 30 days.

We set only the cookies needed to keep you signed in. There is no analytics, advertising or third-party tracking cookie on this site.

When this policy changes we update the effective date above and, for material changes, email account holders before they take effect.