Wiki · Concept · Last reviewed June 25, 2026

Private Access Control Tokens

Private Access Control Tokens, or PACT, are Cloudflare's June 2026 proposal for privacy-preserving web access signals: a site can receive evidence that a request is likely legitimate without making every visitor solve a CAPTCHA or reveal a stable identity.

Definition

Private Access Control Tokens are an announced protocol direction for web admission signals. In Cloudflare's framing, a trusted site or issuer can give a browser an anonymous token after observing a legitimate interaction; another site can later ask the browser to present a token as evidence that the request is not obviously abusive.

The concept is deliberately narrower than identity. PACT does not say who a visitor is, does not authorize a crawler to reuse content, and does not prove that an automated agent is acting within a user's intent. It supplies an anti-abuse signal that a receiving site can combine with ordinary security controls.

Snapshot

On June 22, 2026, Cloudflare announced a PACT initiative with Mozilla Firefox, Google Chrome, Microsoft Edge, and Shopify named in the announcement. Cloudflare described the work as a privacy-preserving protocol for proving that traffic is not malicious and said the participants intended to develop it and submit it for standardization.

PACT should be described as a current proposal, not as a finished web standard deployed uniformly across browsers. Its closest mature technical ancestor is Privacy Pass, whose IETF documents were published in June 2024.

How It Works

Privacy Pass splits the flow into roles and phases. RFC 9576 describes a client, origin, issuer, and attester, with issuance and redemption protocols arranged so the origin can verify a token without learning unique client information from the authentication protocol. RFC 9577 defines the PrivateToken HTTP authentication scheme, and RFC 9578 specifies privately verifiable and publicly verifiable issuance protocols.

PACT applies that family of ideas to a web where sites want fewer CAPTCHAs, fewer ambient fingerprints, and better separation between ordinary visitors, welcome automation, and abuse. The privacy promise is unlinkability: the site redeeming a token should not be able to connect that token back to issuance as a durable browsing identifier.

Existing Private Access Token deployments are relevant background, but they are not identical to PACT. Apple documented Private Access Tokens in 2022 as a way for servers to challenge clients for issuer-signed tokens and validate them using issuer public keys. PACT is the newer browser-and-infrastructure push around access control signals.

Agent Context

PACT matters because the web is no longer only a person clicking a page. Search crawlers, answer engines, shopping agents, scraping systems, monitoring tools, browser automations, and user-directed research agents can look similar at the network edge. A site still needs to stop credential stuffing, fraud, and overload, but indiscriminate challenges can punish disabled users, shared-network users, privacy-tool users, and useful automation.

PACT therefore sits beside, not inside, Web Bot Auth. Web Bot Auth authenticates an automated requester with request signatures. PACT tries to provide an anonymous access signal. One asks who signed this machine request; the other asks whether a browser can present privacy-preserving evidence that a challenge need not escalate.

Governance and Safety

The obvious benefit is less interactive friction. CAPTCHA has become a labor tax on ordinary users and an unreliable filter against determined automation. A privacy-preserving token can make that tax smaller if the absence of a token does not become automatic suspicion.

The risks are institutional. Token issuers can become chokepoints. Browser vendors and infrastructure providers can become informal gatekeepers for which clients pass quietly. A token system can drift from abuse prevention into market control if it becomes necessary for checkout, publishing, search visibility, or access to public-interest services.

Defense Pattern

Spiralist Reading

PACT is a proposed customs lane for the automated web.

The old ritual asked the visitor to prove they were not a script by clicking pictures, leaking browser traits, or submitting to invisible scoring. PACT moves some of that ceremony into cryptographic receipts. The humane version reduces pointless challenges; the brittle version creates a quiet hierarchy of browsers, issuers, and acceptable clients.

For Spiralism, the important move is naming the layer. PACT is not trust, consent, agency, or permission. It is a way to make one admission decision less invasive. The rest of governance still has to be written down.

Open Questions

Sources

Return to Wiki