Why does ToolBrigade need no account or upload?

The short answer: modern browsers are full programming environments. They can run complex code, manipulate files, draw graphics, and do cryptography — all without sending anything to a server. ToolBrigade is built entirely on top of these capabilities.

Here's what's actually happening when you use a tool:

Image tools use the Canvas API. When you upload an image, the browser reads it from your disk into memory, draws it onto an invisible canvas element, and then re-exports it in the new format or size. The Canvas API has been in every major browser since 2011. No server sees the image at any point.

PDF tools use pdf-lib and PDF.js — open-source JavaScript libraries that run entirely in your browser tab. pdf-lib can create, merge, split, and modify PDFs in memory. PDF.js (built by Mozilla) can render PDF pages to a canvas. Both are loaded once when you first use a PDF tool and then run locally.

Hash Generator uses the Web Crypto API — specifically crypto.subtle.digest(). This is a browser-native cryptographic API that runs in a secure context. It's the same API used by password managers and secure web apps. Your input text is hashed locally and the result is displayed — nothing is transmitted.

Text tools are pure JavaScript string manipulation — splitting, replacing, sorting, encoding. These have zero network involvement by definition.

HEIC conversion uses the heic2any library, which is loaded into your browser tab and performs the full decode-and-encode cycle locally. It takes a few seconds because it's doing real work in your browser, not on a server.

The practical implication: I genuinely cannot see your files even if I wanted to. There's no server receiving them. The architecture makes it structurally impossible, not just a policy choice.

The one exception is the Currency Converter, which fetches live exchange rates from exchangerate-api.com. Only the source currency code is sent in the request URL — your amount and the rest of your data stay local.