How privacy works
Why “nothing leaves your browser” is a literal, verifiable claim — not a marketing line.
- Your file
- Uploaded over the internet
- Processed on their server
- Downloaded back to you
Your file leaves your device.
- Your file
- Opened by your browser
- Processed on your device
- Saved by you — locally
Every step happens on your device.
The browser is a powerful computer
Most online tools were designed in an era when web browsers could not do much on their own, so the work had to be done on a server. That era is over. A modern browser can decode and re-encode images with the Canvas API, read and rewrite PDF files, hash text with the Web Crypto API, generate QR codes, parse spreadsheets, and — through WebAssembly — even run heavyweight engines like FFmpeg for video. ToolJutsu is built on this capability. When you use a tool, the code that does the work is downloaded once and then runs locally, the same way a desktop app runs on your machine.
What this means for your data
Because the processing happens in your browser, there is no step where your file is sent to ToolJutsu. There is no upload endpoint, no server that receives, queues, scans, or stores your files — not because of a promise not to look, but because the architecture provides nothing to look at. The result a tool produces is created on your device and saved by you. Once a tool's page has loaded, most tools keep working even if you disconnect from the internet, which is a useful way to see that no network is involved.
Verify it yourself
You do not have to take this on trust. Every browser ships with developer tools that show exactly what the page sends and receives:
- Open any ToolJutsu tool page.
-
Open developer tools — press
F12, or right-click the page and choose Inspect. - Select the Network tab. Tick Preserve log so nothing is cleared.
- Use the tool: choose a file, run the action, and download the result.
-
Review the list of network requests. You will see the page's own assets, and
— for some tools — a one-time download of a processing library. You will
not see a request that uploads your file. Sort by size, or
filter to
Fetch/XHR, to confirm nothing the size of your file was sent.
ToolJutsu versus traditional online tools
| Typical online tools | ToolJutsu | |
|---|---|---|
| Where files are processed | On the company's servers | In your browser, on your device |
| Files uploaded over the internet | Yes | No |
| Account or sign-up | Often required | Never |
| Works offline | No | Yes, once the page has loaded |
| File-size limits | Common, often behind a paid plan | Limited only by your device's memory |
| Can you verify the privacy claim? | Not really | Yes — watch your own network tab |
Being honest about the edges
A few things are worth stating plainly. Some tools need a one-time download of a larger library — for example, the video tools download a WebAssembly build of FFmpeg before they can run; that library is code, not your data. Tools that use your camera or microphone trigger a browser permission prompt before any access is granted, and the captured media still stays on your device. And like any website, ToolJutsu is delivered over the internet, so your browser does request the page's own files. None of this changes the core point: the files you process are never among the things that get sent.
For the full picture of what is and is not collected, read the Privacy Policy. Questions? Use the contact form.