Veilprint

Present websites with a stable, internally consistent browser identity.

Veilprint presents ordinary websites with a stable, capability-constrained Chrome identity. It aligns supported browser-visible identity, region, device, rendering, font, worker, and WebRTC signals without claiming to change the real browser kernel, host operating-system family, or network stack. Main features: - A Balanced preset applies supported identity fields at document start. - Region data can be refreshed independently of the generated identity. - Protection can be disabled globally or paused for a hostname across HTTP and HTTPS, including all ports. - The hosted Settings interface provides Overview, Identity, Protection, Diagnostics, Site Exceptions, and Settings sections. - Diagnostics report each supported signal as aligned, partial, unavailable, or conflict instead of presenting unsupported contexts as protected. - Safe overrides are limited to timezone, locale, languages, location accuracy, logical processors, and device memory. Chrome 138 or later is required. After installation, the user must enable Allow User Scripts on Veilprint's extension details page. Protection remains off when the User Scripts API is unavailable. Veilprint reads the URL and hostname of the current or open tabs locally only when needed to capture a browser baseline, apply a hostname exception, or reload affected pages after a settings change. It does not read or store page text, form contents, cookies, or passwords, and it does not retain a complete browsing record. For a requested region refresh, the extension contacts the region and map providers listed below directly from the browser. Those providers receive the connecting public IP address or approximate coordinates and standard request metadata needed to return approximate region information. An optional IPinfo token is stored locally and sent only to IPinfo when that provider is used. Veilprint has no analytics, advertising, telemetry, account, or payment system. Known limitations: Veilprint does not claim to change TLS, HTTP/2, DNS, the real Chrome kernel, or the host operating-system family. about:blank, srcdoc, and Blob frames, Shared Workers, and Service Workers remain residual contexts and are reported as unavailable where appropriate. Results may remain detectable or conflict with another extension or browser policy.