Vev
Download
Privacy & security

Hardened the moment it opens

No switches to flip. Vev ships with the protections other browsers make you hunt for extensions to get — and it's honest about the edges it hasn't closed yet.

Identity

You look like everyone else

Fingerprint resistance

Canvas, WebGL, AudioContext, fonts, timezone, screen, and navigator entropy are pinned to one fixed reference profile — the Tor Browser model of uniformity, not per-session randomization (which is itself a tell). Crucially, the spoof is injected into the main frame and web workers and service workers by a render-process handler, so a background script can't quietly read your real GPU or CPU core count.

WebRTC leak protection

A global policy limits ICE candidates to the public interface and mDNS-masks your LAN IP everywhere. Private windows go further and remove RTCPeerConnection, RTCDataChannel, and device enumeration outright — verified undefined over the DevTools protocol.
Connection & data

Your traffic and your data

Network hardening

DNS-over-HTTPS in secure mode with no plaintext fallback, Encrypted Client Hello so the site name is hidden in the TLS handshake, automatic HTTPS-only upgrades, and third-party cookies blocked by default.

Encrypted vault

History, bookmarks, and passwords are sealed on disk with AES-256-GCM; the key lives only on your machine. Inspect the raw file and you'll find a magic header and ciphertext — nothing readable. Nothing is ever synced to a server.

Ad, tracker & pop-up blocking

Network-layer blocking (adblock-rust) plus a live threat feed and a community-confirmed phishing list. Cosmetic filtering hides leftover slots. Script-spawned pop-unders are blocked outright — only a pop-up you actually clicked ever opens. The Dynamic Island shows the running count and lets you allow anything per-site.

Tor & custom proxy

Arti — Tor implemented in Rust — is compiled in, no external process to install. A network picker in private windows routes the whole browser (DNS included) through Off, Tor, or your own SOCKS5/HTTP proxy such as Mullvad. The engine only takes a proxy at launch, so the picker saves your choice and relaunches to apply it.
Honesty

What Vev does not (yet) do

A privacy browser that overstates itself is dangerous. Vev documents its edges plainly: a few fingerprint surfaces — the screen size reported to CSS media queries, local font enumeration by measurement, and some residual headless signals — still need engine-level changes. Proxy routing (Tor or a custom proxy) is browser-wide and applied at launch, because the embedded engine refuses per-context and runtime proxy changes; per-tab routing isn't possible. Downloads are saved plainly to your Downloads folder — they aren't encrypted, and we don't pretend otherwise. These are limits we're working on, not secrets.

FAQ

Questions about privacy

What is fingerprinting and how does Vev stop it?

Sites can identify you without cookies by measuring subtle differences in your device — how it draws to a canvas, your GPU, installed fonts, timezone, screen size. Vev makes every copy report the SAME fixed profile, so those measurements no longer single you out. The spoof runs in pages and in background workers.

Does Vev leak my IP over WebRTC?

No. WebRTC can expose your real local and public IP even behind a VPN. Vev limits candidates to the public interface and mDNS-masks your LAN address in all tabs; private windows remove the WebRTC APIs entirely, verified undefined.

Is my history and are my passwords encrypted?

Yes. History, bookmarks, and saved passwords are sealed on disk with AES-256-GCM. The raw file contains only a magic header and ciphertext — no plaintext URLs, usernames, or passwords — and the key never leaves your machine. Nothing syncs to a cloud.

Can I route everything through Tor or a VPN proxy?

Yes, browser-wide. A network picker in private windows offers Off, Tor (embedded Arti — no external process), or a custom SOCKS5/HTTP proxy such as a Mullvad endpoint. Every request and its DNS go through your choice. The engine only takes a proxy at launch, so switching relaunches the browser; per-tab routing isn't possible and we document that rather than fake it.

What does Vev deliberately NOT protect against?

Vev is honest about its edges: a few fingerprint surfaces (CSS-media screen size, local font enumeration, some headless signals) still need engine-level work, and per-tab Tor isn't possible with the current engine. These are documented, not hidden.