Trackers and ads blocked on-device
Requests to about 3,500 known tracker and ad domains are refused before they leave your computer. Every request also carries Do Not Track and Global Privacy Control signals.
Six layers, from what a web page can learn about you to how the browser updates itself. Each one says what it stops, and where it's honest about what it can't.
Most tracking doesn't need your permission. These defaults cut off the usual ways a page profiles you, before it gets the chance.
Requests to about 3,500 known tracker and ad domains are refused before they leave your computer. Every request also carries Do Not Track and Global Privacy Control signals.
Video-call technology can expose your local network address even behind a VPN. Vodou restricts WebRTC to your public interface, so it can't.
Location Guard, camera blocking, and microphone blocking are on from the start. Screen capture, notifications, clipboard reading, and font access are denied unless you allow them.
Cookies and history live in memory and vanish when you close the window. The page cache is overwritten with random data before it's deleted, so an undelete tool finds noise.
Honest limit: on SSDs an overwrite isn't guaranteed to hit the same physical cells. Full-disk encryption is the complete answer; shredding is a second layer.
Addresses you type load over HTTPS. Self-signed certificates are only accepted for your own machine (localhost), never for the open web.
The default search engine is a SearXNG instance running on your own computer, so your searches don't build a profile at a search company. DuckDuckGo, Brave, Startpage, and Google are one click away if you prefer.
Phishing works by looking legitimate. Vodou checks every address before the page loads, without sending your browsing anywhere to do it.
Catches homograph tricks (a Cyrillic “а” posing as a Latin “a”), mixed-script punycode, and typosquats like “paypa1”, computed from the hostname alone.
Honest limit: it protects the most-impersonated brands, not the whole web, and errs toward silence over false alarms.
Public lists of known phishing and malware domains are downloaded on a schedule and checked locally. Not a URL, a hash, or a prefix of where you go ever leaves your device.
Honest limit: it's domain-level, and a brand-new phishing site can slip through until the next list refresh.
Files that can run code on your computer, like .exe installers, get an extra warning before they're saved, because a drive-by download is one of the easiest ways onto a machine.
Right-click an image to read its C2PA Content Credentials, checked against the official trust list. An image with no credential is “unknown”, never “authentic”.
Honest limit: this is provenance, not a deepfake detector.
A browser vault is only as good as its worst day: a stolen laptop, a copied file, a guessed password. Vodou is designed around that day.
The vault file is encrypted with a key derived from your master password by scrypt, which is deliberately slow and memory-hungry to make guessing expensive. Nothing is ever written to disk unencrypted.
Optionally require a FIDO2 key. Its secret is computed inside the key and mixed into the vault's encryption, so a stolen file plus a guessed password still opens nothing. Backup keys are supported.
Open vault entries are re-encrypted under a throwaway session key and only decrypted for the instant you fill or copy them. The vault re-locks itself after 5 idle minutes by default.
Honest limit: this narrows the window a password sits in memory; it can't make memory forensics impossible.
The vault dashboard flags weak passwords, the same password reused across sites, and duplicate entries, and generates strong replacements.
Saved logins are only filled when you ask. A page can't trigger autofill to harvest your credentials in a hidden form.
Adware and sketchy installers love to hijack a browser's start page and search engine. Vodou notices, and puts them back.
Your start page, startup page, and search engine are cryptographically signed with a key unique to your install. If another program edits them, Vodou refuses the change, restores your real setting, and logs what happened.
Honest limit: code already running as your user account could re-sign the files. This raises the bar for hijackers; it isn't antivirus.
Settings snapshots, cookie exceptions, and the crash-recovery file are sealed with Windows DPAPI (or your Linux keyring), so another account or a lifted disk can't read or forge them.
Only real web pages can be a start page. file:, chrome:, and javascript: addresses are refused, which closes a common hijacking trick.
Updating a browser engine is risky: a half-finished update can leave you with no browser at all. Vodou's updater is built to fail safe.
Qt, PyQt6, and the Chromium-based engine are updated together as a compatible set. Every package is checked against its SHA-256 hash from PyPI before anything is installed.
The current version is backed up first. After installing, Vodou starts a fresh copy of the engine to prove it works; if it doesn't, or the update is interrupted, everything is rolled back.
Every change goes through a pull request that must pass a dependency vulnerability audit before it can merge, and Vodou ships with an automated test suite covering the updater, vault, and protections.
Powerful features are also attack surface. These are off until you turn them on, and fenced in when you do.
Summaries, questions, page translation, and chat all run through Ollama on your own computer. Nothing you ask is sent to a cloud AI service.
Vodou's optional MCP control surface listens only on your own machine, requires a fresh random token every run, and can only open tabs and read blocking stats. It has no access to files, the shell, or the vault.
Security software that oversells itself is its own risk. So, plainly:
Found something we got wrong? Report it on GitHub, or email security issues to help@misttechnologies.net.