Privacy policy

Last updated: 2026-06-03

This policy covers what data the AgentPKI Chrome extension and the verify.agentpki.dev verifier service handle. The short version: as little as possible, and never sold.

1. What the AgentPKI extension does

The extension watches webpages you visit for signals that an AI agent is present — a <meta name="agentpki-passport"> tag, an AgentPKI-Token: response header, an RFC 9421 outbound signature, or known agent-framework JavaScript globals — and shows a coloured toolbar badge that tells you whether the agent is verified.

2. What we send across the network

The extension makes network requests to exactly one place: verify.agentpki.dev. The payload of each request is:

• Verification (POST /v1/verify) — the opaque PASETO token that the agent itself published on the page. We do not send the page URL, the page content, or any other context about your browsing.
• Trusted-issuer list (GET /v1/trusted-issuers) — fetched at most once every five minutes. No request body.
• Reputation lookup (GET /v1/passport/:id/reputation) — sent only when a verified token is present. The "id" is the passport's jti (claim ID), which is itself a random identifier minted by the issuer; it is not derived from your identity.
• Abuse report (POST /v1/abuse/report) — sent only when you explicitly click Report abuse in the popup. Includes the passport's jti, the agent's agent_id, your category/severity/description, the page URL (only if you check the "include evidence" box), and a random UUID generated once per install that identifies the extension installation (not you).

3. What we store on your device

All of these live in chrome.storage on your machine and never leave it:

• Installation UUID — generated on first run, used as the reporter field on abuse reports.
• Your own / blocked / whitelisted agents and issuers — managed through the popup and Activity & Settings page.
• Activity log — a rolling 200-entry buffer of detection events for your reference.
• Settings — your optional verifier-base override, if you set one.

Use the Clear all local data button on the Activity & Settings page to wipe these at any time.

4. What we store server-side

• Public issuer directory. When an issuer registers with AgentPKI, their public key and metadata are cached on the verifier for fast verification. No user data.
• Abuse reports. Reports you submit are stored for 14 days in Cloudflare KV under verify.agentpki.dev, keyed by passport jti and report ID. They include the UUID you sent (which we cannot link to you) and the page URL only if you opted to include it as evidence.
• No request logs. Cloudflare Workers retains edge-level access logs for ~30 days for abuse/security purposes per Cloudflare's standard policy. We do not run additional logging or analytics on these requests.

5. What we never collect

• Your name, email, or any account information — the extension has no login.
• Page content, page URLs (except via your explicit "include evidence" opt-in), DOM contents, or form data.
• Browsing history.
• Persistent cross-site identifiers beyond the per-install UUID.
• Telemetry. Anonymous telemetry is permanently disabled in v0.1 and the toggle is greyed out.

6. Third parties

The verifier runs on Cloudflare Workers. Cloudflare may retain edge logs as described above. We do not share data with anyone else.

7. Children

The extension is not directed at children under 13. We do not knowingly collect data from anyone.

8. Open source

Every line of the extension and verifier is MIT-licensed and visible:

• github.com/agentpki/extension
• github.com/agentpki/verifier

9. Changes

We will date this page each time it changes. Material changes will be announced in the GitHub repository's CHANGELOG.md and on /why.

10. Contact

Privacy questions: [email protected].