Privacy

Your photos

They are read in your browser and stay there. They are not sent anywhere, not stored, not logged, and not held in memory beyond the tab.

The tool runs in a sandboxed frame served with the HTTP header:

Content-Security-Policy: connect-src 'none'

That instruction tells your browser to block every outbound request that frame could make — fetch, XMLHttpRequest, WebSocket, and beacons. It applies to all code on the page including code I might add later by mistake. You can verify it: open your developer tools, select the Network tab, and drop in a photo.

The frame is also sandboxed without allow-same-origin, which means it cannot read this page, its cookies, or its storage.

What the tool tells the page around it

The frame cannot open a connection, so the only thing it can do is speak to the page that contains it. It says two kinds of thing. Four events — a file was opened, it was inspected, a strip finished, a download was taken — each carrying a format name, "jpeg" or "png", and nothing else. And its own height in pixels, because the page has no other way to size a frame it is deliberately forbidden from reading. No filename, no coordinates, no count of what was found in your photo, no image data.

What is counted

Nothing, currently. No analytics is configured on this site, so nothing is counted and the events above are received and discarded. If that changes it will be cookieless, and this page will say exactly what it records before it records it.

The one thing that leaves your browser, if you ask

When a photo contains coordinates, the tool shows them as text and offers a button that opens OpenStreetMap in a new tab. Pressing it sends those coordinates to OpenStreetMap. Nothing is sent unless you press it, and the warning sits next to the button.

There are no embedded map tiles anywhere on this site for the same reason — loading a tile would announce a photo's location to a tile server without anyone choosing to.

Email

If you type an address into the form under a result, it is used to reply to you about this tool and the Mac app. It is not sold, rented, or used to build a profile. Unsubscribing is a reply. If you never type an address, no address is collected.

That form is the only thing on this site that reaches a server, and it goes to mine rather than to a form service, so no third party holds the list. Four things are stored: the address, the time, whatever you typed in the second box, and which page you were on — the last so I know which pages are worth writing more of.Your IP address is not recorded, and neither is your browser or device.

The form sits on the page around the tool, never inside the frame. The frame still cannot open a connection to anything, including to this.

How this is paid for

Worth answering directly, because "free privacy tool" is a sentence that should invite the question. It is made by one independent developer. There is no company, no investor and no advertising behind it.

It costs very little to run, and that is the whole answer. Your photos are never processed here — the site serves static files and the work happens inside your browser — so there is no per-photo cost that has to be recovered from you somehow. A tool that uploaded your images would have server bills to pay for, and that is usually what the advertising on those sites is for.

The intended revenue is a paid Mac app, for cleaning whole folders and for the metadata macOS stores outside the image file. Nothing on this site is funded by advertising or by selling data — and there is no data here to sell.

What is not here

• No accounts, and no way to make one
• No advertising, and no third-party ad or tracking scripts
• No cookies set by this site
• No uploads, no photo storage, and no server-side processing of images at all