Privacy
Just Tool It is built so your files, text, and activity never need to leave your device.
Core principles
We process documents, images, and text in your browser using Web APIs, Canvas, WebAssembly, and Web Workers. There is no account system and no server-side file pipeline for tools.
- No file uploads to our servers for tool processing
- No accounts, login, or user profiles
- No advertising or third-party analytics trackers
- Tool work stays in memory for the session unless you download a result
What stays local
When you open a tool and choose a file, that file is read by your browser only. Conversion, compression, encryption, and editing run on-device. Closing the tab discards in-memory data.
What may leave your browser
Pages may load open-source libraries from CDNs (with Subresource Integrity where used), fonts, and the app shell via a service worker. The currency converter may fetch public exchange rates. Those requests do not include your personal files.
Local storage
localStorage stays on this device. We store theme, language, pinned and recent tools, plus optional tool state (todos, drafts, calculator settings). The TOTP authenticator stores account secrets encrypted with a passphrase you set (AES-GCM via Web Crypto). Exporting accounts downloads those secrets in plaintext — treat the file as a credential backup. None of this data is sent to a server.
Questions
If you have a privacy question about this site, open an issue on the project repository or contact the maintainers listed there.