How Ping123 handles browser privacy

Ping123 separates the server IP assessment from browser observations. Browser WebRTC addresses, DNS resolver addresses and fingerprint components are kept in the current browser session and are not included in the diagnostic API request body. This does not mean that checks are offline.

What starts a connection?

Entering the modern home, IP risk, privacy or latency page starts a shared automatic session. WebRTC contacts STUN services; DNS checks contact external resolvers. API and map requests are separate network connections. The old language homepage shows an IP profile and starts extra browser checks with their own buttons.

Steps

1. Read the explanation before opening a diagnostic page.
2. Inspect IP risk and browser observations separately.
3. Use the current policy draft to identify the operator, contact and retention facts still awaiting approval.

FAQ

Does this prove that no service keeps logs?

No. Keeping raw browser observations out of the diagnostic request does not establish provider logging or retention. Operator and policy facts remain pending.

Related diagnostics

Modern home, IP risk, privacy and latency pages start a shared session automatically, including external DNS and STUN connections. Direct entry to tools, method or policy pages does not start a session; an existing session may continue. Old language homepages show an IP profile and use separate buttons for extra browser checks. Guides are explanations, not test results.