Data submitted to LE59
To perform detection, your browser sends to the LE59 backend: your public IP (taken by the server from the connection), timezone, browser language, and the WebRTC candidate addresses collected in your browser (up to 16, used to judge whether WebRTC leaks a public address). This data is used only to generate the result on the fly.
How WebRTC addresses are handled
WebRTC candidate addresses are collected locally and uploaded for consistency analysis. They are not used for profiling or resale, but note they often contain LAN/public IP fragments and are sensitive.
DNS probe records
DNS leak detection issues real queries in your browser and records the queried domain and its resolution, to judge whether DNS goes through a proxy/tunnel. We do not repurpose the specific domains you query.
Caching and retention
Results are cached in Redis keyed by "IP + environment observation" for about 10 minutes to improve responsiveness, then expire automatically. We do not write results to a long-term database; after a page refresh the result cannot be recovered from the server. Server access logs (IP, time, path) are kept only as needed for security and operations.
Third-party data services
Geolocation, ASN, and risk scores come from third-party intelligence services (e.g. IP geo databases, risk scoring). We only relay their aggregated conclusions and do not control their accuracy; treat them as reference only.
Contact and data deletion
For privacy or data-handling questions, email privacy@le59.com to request clarification or deletion. privacy@le59.com