Privacy policy

Results stay in the page session

Public IP details, WebRTC candidates, and browser fingerprint values are held in page memory while the check is open. VeilVerify does not create a result database.

Closing or reloading the page clears the in-memory results. VeilVerify does not create user accounts, set cookies, or write diagnostic results to local storage.

Requests to diagnostic providers

Your browser first requests connection details from a same-site endpoint running on Cloudflare. Cloudflare derives the public IP, approximate location, network organization, ASN, and time zone from the normal request it receives while serving the site. The endpoint returns those selected fields to the page without storing them in an application database.

If the same-site endpoint is unavailable, the browser requests full IP details from ipwho.is. If that request also fails, it requests the public address from ipify.org as an address-only fallback.

When you submit an address to the IP lookup or IP WHOIS tools, the address passes through a same-site VeilVerify endpoint. Geolocation lookups are sent to IPAPI.is. Registration lookups are sent through the RIPE Database RDAP service, which may redirect the request to the authoritative regional registry. VeilVerify returns selected result fields without storing the submitted address in an application database.

During the WebRTC test, the browser contacts Google's public STUN service as part of connection candidate discovery. The browser fingerprint check runs locally and does not need an external fingerprint database.

During the DNS resolver check, the browser requests a random hostname under astrr.in. Cloudflare's authoritative DNS analytics returns the recursive resolver address that requested that hostname. The random hostname is short-lived in the page session and is not stored in an application database. Cloudflare controls its own DNS analytics logs and retention.

These providers receive normal network requests, including the source information required to answer them. They control their own logs, retention, security, and privacy practices. VeilVerify does not control those provider systems.

Scripts and monetization at launch

No analytics, advertising, or affiliate scripts are active at launch. VeilVerify does not render affiliate links or advertising placements while those features are disabled.

If that changes, this policy and any required disclosures will be updated before the related scripts or links are enabled.

Browser and network controls

Your browser, privacy extensions, firewall, DNS settings, or network policy may block part of a diagnostic request. An unavailable result is handled inside the page and does not cause VeilVerify to bypass those controls.