Verify it yourself
Don’t take our word for it — watch
Every privacy tool claims it protects your privacy. The difference here is that you can check the claim in about thirty seconds, without any special tools.
Free with a small watermark · £10 one-off to remove it · your video never leaves your browser
The thirty-second check
-
Open the network tab
Press F12 (or Cmd+Option+I on a Mac), choose Network, and leave it open.
-
Load a video and scan it
Pick a file and run a detection pass. Watch the request list while it works.
-
Check the sizes
No request carries your video. Nothing leaves with a payload anywhere near your file’s size, because your file never leaves at all.
-
Or just pull the plug
Load the page and run one scan, then turn off your Wi-Fi, reload, and process another video. It works — which is only possible if nothing was being sent. The first scan is the part that matters: that is when the detection runtime and the model download and are cached, so a visit where you only loaded the page has nothing to run offline with yet.
Every request this site makes
Inviting you to open the network tab is only honest if we tell you what you will find there. The page is not request-free, and pretending otherwise would fail the first check anyone runs. Here is the complete list.
No third-party analytics or tracking script loads on any page here. The little we measure is sent to our own backend, so there is no tracker in the list below.
What you will see in the network tab
- anonymizevideo.app — the page itself, its JavaScript and stylesheet, and the WebAssembly detection runtime, which is served from this same domain.
- cdn.jsdelivr.net and huggingface.co — the detection model files, downloaded once on first use and then cached by the service worker. Hugging Face redirects the download to its own regional CDN, so you may see a second hostname such as us.aws.cdn.hf.co on the same request. These hosts see that a model was requested and your IP address; they never see your video.
- anonymizevideo.app/api/e — a small POST when the page loads, and one for each step of the workflow you reach. It records which page you are on, roughly where you arrived from, how long a scan took, which detection backend ran, and a coarse size band for the video. Never the filename, never any frame of the video. Your IP address is not stored: it reaches our server, as it must for any request to arrive at all, and is discarded rather than written down. Instead of a cookie there is a random number your browser keeps until you close the tab, which lets us tell one visit apart from the next without knowing who you are.
- Sign-in and payment hosts — Amazon Cognito, which sends the email sign-in code, and our own billing API, which starts the checkout. Both are contacted only if you choose to buy watermark removal, and both are named in the policy described below, so you can match that list against this one.
The list above is enforced, not just published
A list of hosts is still only a promise. This one is also a Content Security Policy: view the source of any page here and the second line inside <head>, straight after the character set, is the complete policy — including a connect-src naming every host the page is permitted to contact. Your browser enforces it. A request to anything not on that list is refused before it is made — by your browser, not by us.
That is worth more than a network tab, which only shows what happened during one visit. The policy bounds what can happen, and it would hold even if some library this site depends on were compromised tomorrow. It also means the claim is checkable in a few seconds without running a scan: read the policy, compare it to the list above, and the two should agree exactly.
Why it can work this way
Two browser technologies make local processing possible. WebCodecs gives the page direct access to your device’s own video decoder and encoder, the same hardware a media player uses, so frames can be decoded and re-encoded without a server. WebAssembly runs the detection model at close to native speed in the same sandbox.
The consequence is that the operator of this site cannot see your footage even if asked to. There is no upload endpoint, no processing queue and no storage bucket — not as a policy that could change, but as a property of how the software is built.
Check it for yourself
Open the tool, open your browser’s network tab, and watch what happens.
Open AnonymizeVideo.app →