Privacy architecture
Processed in your browser.Kept on your device.
PrivateTools runs the selected task in your browser. Application code is downloaded, but the source file is read, processed, and exported on this device.
Local processing path
Updated July 30, 2026. This describes the default local-processing architecture, not a claim that the page makes zero network requests.
File lifecycle
What happens
- 01
Open
The browser receives permission to read the file you selected from this device.
- 02
Process
Browser APIs and downloaded runtimes perform the edit, conversion, preview, or export locally.
- 03
Save
The result is created in the browser session and downloaded back to this device.
Network boundary
What can cross the connection
Local processing protects the source file from an upload workflow. It does not mean the web application is offline or network-free.
Source contents and filenames
Not uploaded
The selected source and its name stay inside the local browser process.
IP, device, and browser data
Not stored
The usage record has no IP address, hardware identifier, device model, user-agent, browser name, or browser version.
Application code and media runtimes
Downloaded
JavaScript, WebAssembly, and supporting assets must reach the browser before they can run.
Browser capabilities
What performs the work
- File APIs read only the files you select.
- Canvas and ImageData handle image pixels and compositing.
- Web Workers keep heavy work away from the main interface.
- WebAssembly and media libraries handle formats the browser cannot process alone.
- WebCodecs can provide accelerated media paths when the browser and codec support them.
Practical limits
What local does not guarantee
- A browser can run out of memory or storage during a large export.
- Codec and hardware support varies by browser and device.
- Cached runtimes can be removed by the browser, so offline reuse is not guaranteed.
- A downloaded result remains on your device until you delete or move it.
- Local processing reduces file transfer exposure; it is not a substitute for device security or backups.
Questions
FAQ
01How does local processing work?
The page loads code into your browser, then file reading, processing, and export happen locally on your device.
02Can PrivateTools see my files?
No. The files are not uploaded to PrivateTools servers, so we do not receive their contents.
03Is this safer than cloud-based converters?
It changes the privacy boundary: the source file is not transferred to a conversion server. Overall safety still depends on your device, browser, network, and how you store the exported result.
04Does it work offline?
It may work after the application code and required runtimes are cached, but offline reuse is not guaranteed because the browser can evict cached assets.
05What happens to my files after conversion?
Working data is held by the browser session and is normally released after the page closes. Downloaded exports remain on your device, and browser caches may keep application assets.
06Does PrivateTools use analytics?
If analytics is enabled, PrivateTools records anonymous usage events. These records do not contain file contents, filenames, IP addresses, hardware identifiers, device models, user-agent strings, browser names, or browser versions.
Inspect the tools, then choose one for the file.
The use-case directory links each task directly to its working browser tool.