What happens to your files

Nothing leaves your device. When you drop a file, the browser reads it from disk and processes it in memory, on a separate thread. The result is downloaded from that same memory.

There is no server receiving anything, because there is no server: the site is a set of static files.

How to check in ten seconds

Open your browser's developer tools (F12 in most), go to the network tab, clean a file and look at the list of requests. There will be none.

If you want to be stricter, turn on airplane mode and reload the page: it will keep working, because the whole thing is stored on your device the first time you visit.

The technical guarantee

The page declares a Content-Security-Policy containing connect-src 'none'. That directive makes the browser block any attempt at an outgoing connection, wherever it comes from. It is not our promise: it is the browser preventing it.

You can see it in the page source, in the <meta http-equiv="content-security-policy"> tag.

What we do not do

The full list, no small print:

No third-party analytics: nobody outside sees where you go. We count which pages get read and how fast they load on our own server, with no cookies and nothing that identifies you.
No cookies. No storage beyond remembering whether you prefer light or dark mode.
No fonts, icons or scripts loaded from other domains.
No IP address is logged, because there is nothing to receive them.

The one exception, and we flag it

If a file contains GPS coordinates we show them on a map drawn in the page itself, without requesting anything from a map server.

There is a button to open that location in OpenStreetMap. That link does leave KillEXIF and shares the coordinates with another website, which is why it sits behind a warning and needs you to click it.

Getting in touch

If you have a question about this policy or about what happens to your files, write to [email protected]. Messages are used to reply to you and nothing else: no list, no marketing, no sharing with anyone.