Skip to content

Privacy Policy

Privacy Policy: Zero File Uploads

Your videos never touch a remote server. Vidto runs 100% client-side in your browser using WebCodecs GPU acceleration and local FFmpeg.wasm.

Updated:

1. Your media files never leave your device

When you drop or select a video in any of Vidto's 43 tools, the browser exposes a local File reference through standard File APIs and BlobSource streaming. Video demuxing, remuxing, WebCodecs hardware encoding, and FFmpeg.wasm WORKERFS fallback processing execute strictly inside your device memory and web workers.

Output files are generated locally as in-memory Blobs or streamed directly to disk via File System Access when supported. Closing the tab immediately discards temporary memory buffers.

2. What browser storage Vidto uses

Vidto stores only minimal client-side preferences locally on your device and never transmits them for ad profiling:

  • Theme preference (dark or light mode) saved in localStorage.
  • Optional PWA install banner dismissal state in localStorage.
  • Static app shell assets and optional on-demand /ffmpeg/* WebAssembly cache in the Cache API (vidto-ffmpeg-v1) so tools work offline.

3. Static hosting & network requests

Vidto is served as a static website over HTTPS with HSTS enabled. Loading a page fetches only static HTML, CSS, JavaScript, fonts, and—only when a legacy codec or filter requires it—the split FFmpeg.wasm runtime from the same origin.

No video frames, filenames, metadata headers, or exported clips are ever POSTed or transmitted over the network.

4. Changes & questions

If we update how local caching or browser APIs behave, we document every change publicly with its effective date above and in our product changelog.