Privacidade

What happens to your files

Your selected files are processed locally in this browser and are not uploaded by FileSlimmer. When you choose a file, its bytes are read by JavaScript running in this tab and handed to a Web Worker, WebAssembly module, or — where your device supports it — the WebGPU or WebCodecs APIs built into your browser. The result is written to a local Blob or to a file location you pick yourself.

FileSlimmer has no server component that could receive a file. There is no upload endpoint, no API, no database and no server-side function anywhere in the deployment. The site is a collection of static files.

How long anything is kept

There is no account

FileSlimmer has no sign-up, no login, no profile and no user database. Nothing you do here is associated with an identity, because there is no identity to associate it with, and nothing is carried between visits except the two preferences described below on this device. FileSlimmer is intended for people aged 16 and over; no age is asked for or recorded, and no one is profiled, including children.

What the hosting provider sees

The static files are served by Cloudflare, which processes the ordinary web requests any website receives: the address requested, the response status, an IP address, a user agent and a timestamp, handled by Cloudflare as the hosting provider under its own terms. That is a request for an HTML, CSS, JavaScript, WebAssembly or model file — never for your file, because your file is never requested from anywhere. The deployment declares no code entry point at all, so nothing of ours executes on Cloudflare's side — only static files are handed out — and it holds no KV store, D1 database, R2 bucket, queue or service binding. You can check that: the deployment configuration is wrangler.jsonc in the published repository, and it has no main.

What this statement does not claim

This is a statement about FileSlimmer's own behaviour. It is not, and cannot be, a claim about the following, all of which are outside any website's control:

• browser extensions you have installed, which can read page contents;
• your operating system, which can inspect any file you open;
• your network operator or DNS resolver, which sees that you visited this site;
• the hosting provider's own request logs for the static files themselves.

The methodology page describes how the local-processing property is tested, so you can verify it rather than take it on trust.

What FileSlimmer stores in your browser

• Your chosen language and theme, in localStorage.
• Application assets, WebAssembly modules and AI models, in the browser cache used by the service worker. These are FileSlimmer's own files, never yours.

Your files and the outputs generated from them are never written to localStorage, never written to the service-worker cache, and never written to IndexedDB without an explicit action by you. You can clear everything FileSlimmer has cached from the workspace at any time.

Analytics and advertising

At launch FileSlimmer loads no analytics and no advertising. There is no tracking script, no tag manager, no pixel and no consent platform, because there is nothing to consent to. If advertising is ever enabled, it will not appear on file-processing workspaces, and this page will be updated before it does.

Error reports

FileSlimmer sends no crash or error reports. Errors are shown to you locally with an error code and a short message. They never contain file contents, document text or metadata read from your files.

Operator

The controls that exist, and the ones that do not exist because there is nothing for them to control, are listed under privacy choices. The browser storage this site writes is itemised on the cookie statement.