How local processing works

Last updated: 14 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 Phase 1 free tools.

“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 suspicious upload or third-party beacon carrying file or payload bytes. 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. Analytics—if enabled—send only allowlisted coarse events.

Read the Privacy Policy for retention and logging details.