Privacy

The short version: Photos are opened and compressed on this device. Nothing is uploaded. There is no server here that could receive a photograph, and the database this site does use holds file names and numbers.

What happens to a photograph

Your browser opens each file from disk, decodes it, writes a new version of it and hands that back to you as a file or an archive you choose to save. All of that happens inside the tab. This site is a static export — no API, no route handler, no upload target — so there is no address a photograph could be sent to even by mistake.

What is kept in this browser

A long job needs to survive a closed tab, so the state of a job is stored in this browser, on this machine, in a database only this site can read. It contains:

• The rule you chose — the quality position, the long edge, the metadata choice, the skip settings.
• The list of files in the job: each one's name, its path inside the folder, its size in bytes and the time it was last modified.
• What happened to each file already processed: written, skipped or failed, the byte counts, and the reason where there is one.

It contains no image data of any kind. That is not a policy, it is a check that runs before every single write and throws if anything resembling a picture is handed to it, plus a build gate that fails if the code that does the writing ever learns how to. Clearing site data for this domain removes all of it, and losing it costs you a resume and nothing else.

The compressed copies themselves are held in the tab’s memory until you save them, and are gone when the tab closes. In Chrome and Edge you can choose a file to save into as photos finish; that file is on your disk, written by your browser, where you put it.

If you save a recipe, its name and its settings are kept in this browser’s local storage so it is there next time. Nothing else goes in with it: no file name, no path, no picture.

Measurement

This site counts visits with Cloudflare Web Analytics, on its own account. It sets no cookie and builds no profile. On each page view it records the page address, the referring page, the country, and the browser and device type. The counter runs only on compressphotos.com itself: the code that adds it checks the address first, so a copy of the site on any other address, a preview or a local build does not report anything. This build does not yet carry the site's analytics token, so at the moment the counter is not requested on any page.

Nothing about a job can reach it: not a photo, a thumbnail, a file name, a path, a size, a recipe or a result. Those never leave the tab, so there is nothing for a counter to be given.

Advertising

There is no advertising on this site.

Children, accounts and email

There are no accounts and no sign-in. The only place this site takes an email address is the contact page, and only if you choose to write. The site is not directed at children.

The contact page

The contact page is the one part of this site that talks to anyone else. When you press its send button, the name, email address and message you typed, plus the name of this site, go to a Google Form that the team reads — and only then; nothing is requested from Google when the page opens. No photograph, file name or job detail is attached, and no other page here contacts Google or anyone else.

Changes

If this ever changes — if some future feature genuinely needs a server — it will be stated here and labelled on the surface before it runs, not mentioned afterwards. A tool that silently starts sending photographs somewhere has broken the only promise it made.