Privacy
Privacy at MyLeaks
MyLeaks processes browser and network signals to show what its tests can observe during the current visit.
What stays in your browser
The detailed measurements for these browser-exposed fingerprint surfaces are calculated and displayed in page memory:
- Canvas
- WebGL
- WebGPU
- Audio
- detected fonts
- ClientRects
- Canvas TextMetrics
These detailed measurements are processed in the page. Network and protocol tests require connections to MyLeaks and are covered below.
What reaches MyLeaks servers
MyLeaks receives the network requests needed to deliver the page and run the selected tests. Depending on the test, this may include:
- the public source IP address and IP version;
- HTTP request and TLS connection metadata, including browser-sent request headers;
- DNS resolver-egress IP addresses that query randomized test names;
- the network source IP address and port of a STUN request;
- TLS ClientHello characteristics;
- HTTP/2 connection behavior;
- QUIC and HTTP/3 characteristics; and
- characteristics of the initial IPv4 TCP SYN that reaches MyLeaks.
Technical definitions and limitations are documented in the methodology.
Temporary processing
Some observations are kept temporarily so MyLeaks can match test requests, limit abuse, and return results.
MyLeaks does not maintain a permanent visitor-results history. Short-lived operational data expires automatically; retention may vary by test. Contact MyLeaks if you need details about a specific test.
Third-party services
For the VPN and proxy check, MyLeaks sends the current public IP address to proxycheck.io and receives network classification information. Browser fingerprints, WebRTC candidates, DNS observations, and protocol fingerprints are not sent to proxycheck.io.
This product includes GeoLite data created by MaxMind. MyLeaks uses this data locally for approximate location and network information.
DNS test
The DNS test uses unique test names. MyLeaks can observe the resolver or resolver-egress IP address that queries them.
This address may belong to a recursive resolver or a resolver egress point. It is not necessarily the exact DNS server manually configured on the device. A resolver using a different public IP or ASN is informational and is not automatically proof of a DNS leak.
WebRTC test
The browser’s ICE candidates are analyzed in the page. The WebRTC test connection reveals its network source IP address and port to MyLeaks so the test can return a result.
Cookies and browser storage
- The audited MyLeaks application does not create application cookies.
- Test requests do not intentionally send credentials or cookies.
- LocalStorage and SessionStorage are tested only for capability with temporary keys, which the page attempts to remove immediately.
- The audited production application contains no analytics or advertising SDK.
These statements concern the audited MyLeaks application, not browser extensions or infrastructure outside MyLeaks’ control.
Analytics and advertising
MyLeaks currently does not use analytics or advertising tracking in its application. This does not describe the independent practices of the IP-intelligence provider.
Logs
MyLeaks does not intentionally maintain visitor access/request logs or logs of successful fingerprint results in production. System or service operational messages may exist independently of visitor tracking. No retention period for those operational messages is stated here.
Contact
For privacy or technical questions, email myleaksnet@proton.me.
Last updated: