Blog/Privacy
Privacy

Why Your Files Never Leave Your Browser

Local processing is one of the simplest privacy wins on the web. Here is what it means, when it applies, and how to check.

The short version

Many AnonLift tools run entirely in your browser. When you compress an image or remove a background, the file is read by JavaScript on your device and the result is created there too. There is no upload step.

That matters because uploads create copies on someone else’s computer, travel over the network and may be retained in logs or storage.

What local processing means

A browser is a small application platform. Modern APIs can decode images, draw to a canvas, read PDFs, generate ZIP files and even run machine-learning models. If a task can be done with those APIs, it does not need a server.

Tools that use local processing on AnonLift include the Image Compressor, Image Resizer, Image Converter, PDF Tools, ZIP Tools and several AI tools.

When a server is still needed

Some tools genuinely need a server: DNS lookups, IP information, currency rates, translation and grammar checking. In those cases the minimum necessary text or query is sent to a service, and the tool page explains it.

Local-first does not mean “never uses the network”. It means the file you care about is not uploaded just to perform the task.

How to check for yourself

Open your browser’s developer tools, go to the Network tab and run a local tool. You should see the page assets load, but no request carrying your image or PDF. For tools that use an API, you will see the request and can inspect exactly what is sent.

A practical rule

Before uploading a sensitive file to any website, ask: does this task really need a server? If the answer is no, prefer a tool that runs locally. Your data stays under your control, and the result is often faster too.