[ Web Proxy ]
URL:
Viewing: https://developers.cloudflare.com/privacy-proxy/concepts/how-it-works/ [Back]  [Original]

How Privacy Proxy works Cloudflare Privacy Proxy docsSkip to content
SearchCtrlKLog in
  1. Home
  2. /Privacy Proxy
  3. /Concepts
  4. /How Privacy Proxy works

How Privacy Proxy works

Last updated Apr 21, 2026Copy as MarkdownView as MarkdownAgent setup
OverviewTraffic flowMASQUE protocolsPrivacy separationRelated resources

Privacy Proxy uses the MASQUE protocol suite to create encrypted tunnels between clients and destination servers. This page explains the protocol mechanics and how privacy is preserved.

Traffic flow

      1. Connect + Auth            4. Connect        
                                      
  Client        2. CONNECT request       Privacy       (Egress IP)        Destination 
              Proxy                              Server    
                                                                 
                3. 200 OK                              5. Connected                   
                                                           
                                                                                      
             6. Encrypted data tunnel                
                                                     

            Client IP hidden  Cloudflare Egress IP visible 
  1. The client establishes an HTTP/2 or HTTP/3 connection to Privacy Proxy and presents credentials (PSK or Privacy Pass token) in the Proxy-Authorization header.
  2. The client sends a CONNECT request specifying the destination hostname and port.
  3. The proxy responds with 200 OK to confirm the tunnel is ready.
  4. The proxy opens a connection to the destination using an egress IP address selected based on the client's geolocation.
  5. The client sends encrypted data through the tunnel. The proxy forwards bytes without inspection.

Throughout this process, the proxy learns the destination but not the content. The destination learns the egress IP address but not the client's real IP.

MASQUE protocols

MASQUE (Multiplexed Application Substrate over QUIC Encryption) defines methods for proxying traffic over HTTP. Privacy Proxy supports two MASQUE methods:

Method Transport Use case
HTTP CONNECT TCP Traditional HTTPS traffic
CONNECT-UDP UDP QUIC-based traffic, real-time applications

Both methods create encrypted tunnels where the proxy forwards traffic without inspecting the content. The proxy sees only the destination hostname and port, not the actual requests, paths, or data exchanged.

Privacy Proxy accepts connections over HTTP/2 (TLS over TCP) and HTTP/3 (QUIC), selecting the appropriate protocol based on client capabilities.

For a technical deep dive into how these protocols work, refer to our blog post .

Privacy separation

Privacy Proxy creates a privacy boundary between user identity and user activity:

Information Who knows it
User identity (IP address, account) Authentication service, first-hop proxy (if using double-hop)
Destination server Privacy Proxy, destination server
Request content Client, destination server only

The proxy authenticates users to verify they have permission to use the service, but authentication happens separately from proxying. Once authenticated, the proxy forwards traffic without linking individual requests to specific users.

PreviousOverviewNextDeployment models

Was this helpful?

YesNo
Edit pageReport issue
[]

Web Proxy Viewer  |  New URL  |  Original Page