demo · v137

Policy planner

Compose your Reporting-Endpoints, pick which IP signals (client_ip, proxy_ip, source ip_anonymisation) to opt into, and the planner shows the headers, the resulting report shape, and the privacy class each field falls into.

Heads upThis is the planner/preview surface. To actually receive reports you need a public HTTPS endpoint — the “sample” block below is the exact JSON Chrome 137 would POST to report-uri given your settings.

policy controls

Endpoint URL

Endpoint group

Include client IP?

Include proxy chain?

Anonymise reverse-DNS?

Trigger condition (sample)

scenario

Visitor IP (sim)

Visitor user-agent (sim)

Region floor

generated headers

…

sample posted report

…

Policy planner

policy controls

scenario

generated headers

sample posted report

field-by-field schema

see also