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
- Your browser downloads the page — HTML, styles and a small piece of JavaScript (plus a lightweight analytics tag; see below). None of that traffic carries your files or the values you enter.
- 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).
- 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'll see the page load (and, if you've accepted analytics, a request to Google) — but no request that carries your files or the values you type into the tool.
- 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 measure (and what we don't)
We use Google Analytics to measure page visits — which tools are popular and roughly where visitors come from — but only if you accept our cookie banner. It's off by default (Google Consent Mode), so no cookie is set and no data is sent until you consent; you can decline or opt out at any time. Crucially, analytics only ever records that you visited a page — we never see what you type into a tool, what files you process, or any content you work with, because that never leaves your device. You can also choose to give a tool a star rating, stored anonymously (just the tool name and star value, no IP, no cookie, no identifier). See the privacy policy for the complete picture, including the standard access logs every web host keeps.
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.