A step-by-step privacy check for public IP, DNS, WebRTC, cookies, fingerprinting, permissions and saved data.

Check the public IP first

Record the public address visible in a normal session. If a routing feature claims to change the network path, enable it and check again. Ordinary private mode is not expected to change this address.

Test DNS against the intended route

A DNS test can show which resolver infrastructure answered specially generated queries. Compare that with the DNS path you intended rather than treating every unfamiliar resolver name as a leak.

Inspect WebRTC carefully

WebRTC tests can report public, private, relay or obfuscated addresses. The key question is whether WebRTC exposes a public route that bypasses the privacy path you intended.

Check cookies and local storage

Create temporary site state, close the privacy session and reopen the browser. Confirm whether the state survived and whether that behavior matches the mode's promise.

Look at fingerprinting signals

Fingerprint tests are useful diagnostics, but uniqueness scores depend on the test's own sample. Compare actual observable signals between modes.

Review permissions and downloads

Inspect which sites retain camera, microphone, location and notification permissions. Then check the Downloads folder for files saved during private sessions.

Repeat after major updates

Browser privacy behavior changes. Re-run a small baseline after major browser, operating-system or network changes.

Related Voryqe guides

Frequently asked questions

Does private browsing make me anonymous?

No. Private browsing mainly changes local browser-session storage. Network routing, account identity and fingerprinting are separate layers.

Should I trust one privacy score?

Use scores as diagnostics, not guarantees. Compare the actual signals a browser exposes and test the specific layer you care about.

Can websites still recognize a signed-in account?

Yes. If you sign in, the service can associate activity with that account even when the browser session is private.

The takeaway

Privacy works best when each layer is clear and testable. Local browser data, website tracking, permissions and network routing are related, but they are not the same thing. Voryqe is designed around making those differences visible instead of presenting one magic privacy switch.

Explore Voryqe for Windows on Microsoft Store

Editorial note: Voryqe does not claim that ordinary private browsing makes users anonymous. Network-routing features should be evaluated separately from local browsing modes.
Explore Voryqe Privacy → Run the Privacy Test → See browser features → More privacy guides →

Privacy should be visible, not mysterious.

Explore Voryqe for Windows and choose the browsing mode that matches what you want to protect.

Get Voryqe on Microsoft Store →