Why In-Browser Tools Keep Your Data Private
When you paste sensitive text into an online formatter or hand a file to a converter, where does that data actually go? For many web tools the answer is 'to a server you can't see.' AZ Tools takes a different approach: the work happens in your browser, on your device. This guide explains what that means, why it matters, and how you can confirm it for any tool.
Server-side vs client-side tools
Broadly, a web tool can do its work in one of two places. A server-side tool sends your input over the network to a computer the operator controls, processes it there, and sends the result back. A client-side tool ships a small program to your browser along with the page, and that program does the work locally — your input is never transmitted.
The difference is invisible in the interface: both show a box to type in and a result below. But for anything sensitive — passwords, API keys, personal documents, proprietary code — it is the difference between your data staying on your machine and handing it to a third party.
What 'runs in your browser' actually means
Modern browsers are capable computers. They can parse and format JSON, hash files, resize images on a canvas, do arbitrary-precision arithmetic and generate QR codes, all through standard JavaScript and Web APIs — with no server round-trip required.
On a site like this, each tool is a small self-contained program delivered together with the page. Once the page has loaded, the tool keeps working even if you disconnect from the internet, because there is nothing left for it to fetch.
Why this matters for privacy and security
None of the points below require you to trust a privacy policy. The guarantee comes from where the computation physically happens, not from a promise about what a server will or won't do with what it receives.
- Confidentiality: data that never leaves your device can't be logged, cached, breached or handed over from a server.
- No accounts: there is nothing to sign up for, so there is no profile to track you with.
- Works offline: once the page is loaded, sensitive work can be done with the network switched off.
- Compliance: keeping data local sidesteps a whole category of data-transfer and retention concerns.
How to verify it yourself
You don't have to take anyone's word for it. Open your browser's developer tools (F12 on most desktops), switch to the Network tab, and use a tool while you watch. A client-side tool produces no network requests carrying your input — you'll see the page and its scripts load, and then nothing further as you type or process a file.
You can go further and turn off your network entirely after the page has loaded: a genuinely client-side tool keeps working. If a tool stops working offline, or you see your data going out in the Network tab, then that tool is doing its work on a server.
The trade-offs
Client-side tools aren't the right choice for everything. Work that needs huge datasets, secret server-side keys, or coordination between users genuinely belongs on a server. But for the vast majority of everyday utilities — formatting, converting, encoding, calculating, generating — the browser is more than capable, and keeping the data local is simply better for you.
That is the bet this site makes: do the work where your data already is, and never ask for more than that.