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 or send those displayed values to its own application server.

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 requests public IP details directly from ipapi.co. If that request fails, it requests the public address from ipify.org as a fallback.

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.

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.