Privacy
Privacy is not a footnote for DivXpress; it is the reason the tool works the way it does. This page explains, plainly, what happens to your files and your data.
The short version: your video is processed inside your own browser and is never uploaded to any server. We never receive it, see it, or store it, because it never leaves your device.
Your files
When you choose or drop a video, it is read directly by the code running in your browser and converted on your device using a WebAssembly build of ffmpeg. The input and the output exist only in your browser's memory and on your own computer. Nothing about the file, its name, its contents, or its output, is transmitted to us or to anyone else. Closing or refreshing the tab clears it.
The conversion engine
The first time you convert, your browser downloads the conversion engine (roughly 30 MB) from a public code delivery network so the tool can run. That download is the engine code itself, not your file, and it is cached so later conversions start quickly. Downloading a script from a network is a normal, standard request; it does not send your video anywhere.
Analytics
To understand which tools are useful, we use privacy-friendly, aggregate analytics that record page views without cookies and without building a profile of you. This data is anonymous and counts events like "the compress page was viewed," never anything about the files you convert. We do not sell data, and there are no advertising or cross-site tracking cookies on this site.
What we do not do
- We do not upload, copy, or store your video files.
- We do not require an account, email, or any sign-up.
- We do not use tracking cookies or sell any data.
- We do not add watermarks or embed anything in your output.
Changes
If this policy ever changes, for example if a future paid feature needs a server, we will update this page and make the change clear before it applies to you. Thestandards page covers the same ground from the other side: where the encoding behaviour comes from, what the converter cannot do, and how the site is funded. Questions are welcome at[email protected].
Verify it yourself
Further reading on in-browser processing
A privacy promise is worth more when you can check the mechanism behind it. These three pages describe how a browser reads a file and runs an encoder without sending anything out.
- MDN Web Docs: WebAssembly. The browser technology that lets compiled code encode video at usable speed on your own device.
- MDN Web Docs: File API. How a page reads a file you hand it without sending that file anywhere.
- ffmpeg.wasm. The open-source project that compiles FFmpeg to run inside a browser tab.