Blur Face
We Never Upload Your Photos or Videos — Proof
Inspect how Blur Face processes selected files in the browser and verify the session using offline and Network-panel checks.
We Never Upload Your Photos or Videos
Inspect the browser behavior instead of relying on a privacy slogan.
A Quick Offline Check
This check demonstrates that image processing can continue locally after the required page assets and models have loaded:
Open blur-face.com in your browser and wait for the page to fully load (about 5 seconds).
Turn off your Wi-Fi or unplug your ethernet cable. You are now offline.
Drop any photo or video onto the tool.
Watch it detect and blur faces — with zero internet connection.
Successful offline processing is useful evidence of local execution. For stronger verification, also inspect the Network tab while selecting and exporting a file.
How It Actually Works
When you first visit blur-face.com, your browser downloads the page code, model files, and other normal site assets. Analytics requests may also occur. The image-processing path itself is designed to run in the browser rather than send the selected source file to a Blur Face processing server.
After that, everything runs inside your browser using a technology called WebAssembly (WASM). Your photo or video is loaded directly into your browser's memory and never touches our servers.
When you click Export, the processed image is saved straight to your device — again, no server involved.
What the Network Tab Shows
For the technically curious: open Developer Tools (F12), select the Network tab, preserve the log, and process a test image. Inspect every request rather than only filtering by Fetch/XHR. You should see application assets, model files, and analytics traffic, but no request whose payload contains the selected image.
Expected outbound requests can include:
- The AI model weights (downloaded once, then cached)
- Google Analytics page-view data (we track visits, not your images)
- Normal page assets and third-party resources used by the site
An Honest Note About Analytics
We use Google Analytics to understand how many people visit the site and which tools they use. This tracks page-view behavior — not your photos, not your files, not any personal data from the images you process.
The application code does not intentionally add selected image bytes to analytics events. You can verify the actual requests for your session using the Network instructions above.
Why We Built It This Way
Blur Face uses local processing so the editing workflow does not require sending source images to a Blur Face image-processing server. This reduces one category of exposure while leaving the user in control of the selected file.
When you are blurring faces — whether to protect a child's identity, a journalist's source, a patient's medical record, or a witness's face — the last thing you should have to worry about is whether your sensitive file is sitting on someone else's server.
Use the offline and network checks above whenever you want to verify the behavior rather than relying on this explanation alone.
Want the full legal and compliance breakdown?
Read our Privacy Compliance Guide →Protect your privacy today
Create face redactions locally in your browser, then review every detected and manually added area before export.
Start Redacting Now