Privacy
BlurVault exists so you can hide what's in a file without handing the file to anyone. This page lists every piece of data the service does handle, and where it lives.
| Data | Where it lives | Why |
|---|---|---|
| Your photos and videos | Only in your browser tab's memory | Detection, blurring and export run on your device. Nothing is sent to BlurVault or anyone else. |
| Email and hashed password | Supabase (our account database) | Only if you create an account. Used to log you in. |
| Plan and Stripe customer reference | Supabase | So the editor knows whether Pro features are unlocked. |
| Card details | Stripe | Entered on Stripe's checkout page. BlurVault never receives them. |
| Anonymous page views | Vercel Web Analytics | Counts visits per page without cookies. No file contents, ever. |
Files the page downloads
To find faces, the page downloads Google's MediaPipe face detector the first time you use it: an 11 MB WebAssembly runtime and a 230 kB model, served from blurvault.vercel.app. If that copy can't be reached, the page falls back to the same files on cdn.jsdelivr.net and storage.googleapis.com. Those are downloads to your device. Nothing about your photo goes with them.
Checking this yourself
Every claim above can be tested in your browser's DevTools. The tutorial shows how.