No processing API
The production export contains static HTML, JavaScript, Web Workers and self-hosted WebAssembly assets. It contains no API route or upload handler.
Privacy architecture
Your files are browser inputs, not server uploads.
UsefulUtility is a static local-processing application. The browser downloads the application and engine packs; supported jobs then run on your device.
Input stays on the device
Selected files are read with browser File APIs and passed to local workers. Filenames and file contents are not sent to analytics or telemetry.
Local persistence
Completed outputs can be retained in the Origin Private File System, with job metadata and recipes stored through Dexie in IndexedDB.
Explicit network boundary
A future DocDome adapter is a separate, user-triggered export action. Local tools never silently fall back to cloud conversion.
What may remain on your device
- Job records, settings and saved recipes in IndexedDB.
- Input-independent engine assets in Cache Storage for offline use.
- Outputs you choose to retain in OPFS, or IndexedDB where OPFS is unavailable.
- Browser-generated previews and object URLs for the current session.
Clearing site data removes this local workspace. Browsers can also evict non-persistent storage under pressure, so important outputs should be downloaded or explicitly saved.
When network activity can occur
Application update
The browser can retrieve a newer static release or engine pack from UsefulUtility’s own origin.
Explicit DocDome export
A completed output can be sent only after you press the dedicated save action and an adapter is configured.
External reference data
Future live-rate tools must identify the source and cannot use the strict no-network badge.
Limits of a browser-only promise
Processing stops when the page or installed app is closed. Very large media, complex CAD files and proprietary Office rendering can exceed a device’s memory, storage or available browser APIs. UsefulUtility reports those limits instead of uploading a file behind the scenes.