INTEGRITY Cloudflare Docs

Privacy Pass

Privacy Pass, an IETF standard that Cloudflare helped pioneer in 2017, offers a way for users to prove something about themselves–that they have passed a CAPTCHA, are of age, are part of a subscription class–to the site they are accessing, without revealing an identifier. The main mechanic is Privacy Pass tokens, which are the cryptographic tool that lets a service provider verify information about a user without learning who that user is or being able to track them across requests.


What is in these docs


Why it matters

Verifying users on the Internet usually forces a trade-off between user experience and privacy, coming at the cost of either time spent solving CAPTCHAs or privacy lost to a trackable identifier. Privacy Pass eases that trade-off: a user proves a claim once, and receives tokens that can be redeemed later without revealing their identity or linking their activity.

So far, the main use cases have been providing a privacy-preserving CAPTCHA alternative, such as through Turnstile and verification for Cloudflare's Privacy Proxy and Privacy Gateway products. However, by adjusting the deployment, Privacy Pass tokens can attest to any other information a service provider wants to prove.


Use cases

Every Privacy Pass use case comes down to the same idea: let clients prove something to an origin server without revealing any other information. Some examples include:


Why Cloudflare operates Privacy Pass infrastructure


Privacy Proxy

A MASQUE-based forward proxy that uses Privacy Pass tokens to authenticate users without revealing their identity.

Privacy Gateway

Implements the Oblivious HTTP (OHTTP) standard for request-level privacy, hiding client IP addresses from application backends with Privacy Pass authentication.

Turnstile

Cloudflare's smart CAPTCHA alternative that can be embedded into any website, using Privacy Pass tokens as one of the signals used to decide whether or not a challenge is shown to a visitor.