How it works: privacy by architecture

The short version: LazyTools has no processing servers. Your data cannot be uploaded, because there is nowhere to upload it to.

What happens when you use a tool

1. Your browser downloads the page — HTML, styles and a small piece of JavaScript. This is the only network traffic involved.
2. When you type a value or pick a file, the tool's code runs on your device, using your browser's built-in JavaScript engine (and WebAssembly for heavier tools like image or PDF processing).
3. The result is computed locally and shown to you. Nothing you entered ever leaves your machine.

How to verify this yourself

• Watch the network tab. Open your browser's developer tools (F12 → Network), then use any tool. You will see no requests carrying your data — the page loads once, and that's it.
• Go offline. Load a tool, then switch off Wi-Fi or enable airplane mode. The tool keeps working, because nothing it does requires a server.

How that differs from most "free online tools"

Most tool websites work by uploading your file to their servers, processing it there, and letting you download the result. Their privacy protection is a policy ("we delete files after one hour"). LazyTools' privacy protection is an architecture: the processing code comes to your data, instead of your data going to the code. A policy requires trust; an architecture can be verified.

What we still measure (and what we don't)

We use privacy-respecting, cookieless analytics to count page visits — so we know which tools are useful. We never see what you type into a tool, what files you process, or any content you work with. See the privacy policy for the complete picture.

Technical stack, briefly

The site is static HTML generated ahead of time. Interactive tools are small Preact components; heavier future tools (images, PDF, media) will use WebAssembly builds of proven open-source libraries running in your browser. Source attributions are listed on the licenses page.