Privacy & how it works

Your files stay on your device. Everything is processed locally in your browser. No uploads, no tracking. Below is an honest split between what is guaranteed for your files and what is expected for app resources.

Your files (guaranteed by design)

When you pick a file in a converter, the browser grants this page temporary access to that file only. Conversion runs in the page sandbox (and Web Workers / WASM where needed). Fluxed does not provide a file-upload API for conversion, does not store your selected file contents on a server, and does not require an account. Output is assembled locally and offered as a download.

App resources (expected network use)

Loading Fluxed still uses the network for HTML, JavaScript bundles, WASM engines (for example FFmpeg or libarchive), optional decoders, and (on first use of background removal) a local ML model. These requests retrieve software assets. They do not include the bytes of the file you selected for conversion. After assets are cached by the service worker, many tools continue offline.

Architecture (local tools)

For conversion tools, your file stays in the browser. The network is used for software assets, not for uploading documents to a conversion API.

┌──────────────┐     file pick (local)      ┌──────────────────────────┐
│  Your device │ ─────────────────────────► │  Browser tab (Fluxed)    │
│  (disk)      │ ◄──── download result ──── │  Workers / WASM codecs   │
└──────────────┘                            └────────────┬─────────────┘
                                                         │
                              app assets only            │  HTML, JS chunks,
                         (not your file bytes)           │  FFmpeg / libarchive
                                                         ▼
                                              ┌──────────────────────┐
                                              │  fluxed.dev (static) │
                                              │  no conversion API   │
                                              └──────────────────────┘

No analytics or tracking

Fluxed does not ship analytics SDKs, advertising pixels, or behavioral tracking cookies. Ordinary web-server access logs may still record technical request metadata (such as IP address and requested asset path) when you fetch pages or engines, not the contents of files processed in your browser.

Local storage and offline cache

A service worker caches application code and converter engines to support repeat visits and offline use. Heavy engines (FFmpeg, libarchive, background-removal models) use network-first caching so deploys are less likely to stick on a stale WASM build; icons and small assets may still be cache-first. Those caches hold Fluxed software, not the documents you convert. Clear them anytime via your browser's site-data controls.

More product context: About Fluxed · FAQ.