How local processing works
Last updated: 15 August 2026
When a Utilxen tool is marked local, selected files are read in your browser. Heavy work runs in a Web Worker and/or same-origin WASM module. Downloads are generated from in-memory results. There is no server upload endpoint for these free tools. Files and tool payloads are not uploaded.
“Processed on your device” badge
The badge appears only when a tool’s registry flag privacyVerified is true after a recorded network-egress check: production build, select → process → download (and cancel/error where applicable), with no request carrying file bytes, filenames, QR/form payloads, or credentials. The badge promises that files and payloads are not uploaded. It does not mean the site makes zero network requests. Evidence is stored under docs/privacy/.
What still loads
The page itself, static assets, and same-origin worker/WASM modules may load over the network. That is hosting, not uploading your document. If product analytics is enabled after owner approval, Utilxen may send minimized anonymous operational events (tool ID, route, coarse device/browser/referrer class, size and duration buckets, stable error codes) to Utilxen and store them in its Hostinger MariaDB database for bounded periods. Analytics never includes files or tool payloads. Collection is currently disabled.
Read the Privacy Policy for retention and logging details.