Privacy

The short version

• No file you queue is sent anywhere. The queue runs on your machine. Nothing leaves it.
• There is no account, no sign-in and nothing to create.
• Nothing about your pictures is stored between visits. Saved recipes hold rules and nothing else.
• No visit counter is switched on today, and no advertisement has been served here yet. Both sections below say what is off, what would change, and when.

What happens to a file you queue

When you drop a folder, the browser reads the first sixty-four kilobytes of each file to find out its format, its dimensions, its orientation and whether it is animated. When you start a run, each file is decoded into memory inside this tab, drawn at the sizes your rules asked for, encoded, and appended to an archive that also lives in this tab. Then it is handed to your browser’s download machinery.

At no point is a picture, a filename, a dimension or a byte count transmitted. There is no server behind this site: it is a set of static files, and the part that does the work is JavaScript running on your own processor. Closing the tab discards everything, immediately and without a copy.

You can check this rather than take our word for it. Open your browser’s developer tools, keep the network panel open, and run a job. What you will see is this page, its stylesheet, its fonts and its icons — and as this is written, nothing else at all, because the two third parties described below are both switched off in the code that builds these pages.

What is kept on your device

One thing: saved recipes. A recipe is a named set of rules — targets, fits, formats, quality values and filename templates — stored in this browser’s local storage on this device. It holds no filenames, no dimensions of anything you processed and no record that a run ever happened. It never leaves the device and it is not readable by us. Deleting a recipe on the page removes it; clearing site data in your browser removes them all.

Analytics

Nothing here is measuring visits at the moment. No measurement property has been set up for this domain, the token in the build is still the placeholder it shipped with, and the page renders no beacon at all — so your arrival on this page was not recorded, tallied or attributed anywhere.

The intention is to turn measurement on, using Cloudflare Web Analytics on a property held by this domain alone and pooled with nothing else. That product was chosen because it needs no cookie and assembles no profile. Were it live, it would receive the page address, the referring address, and coarse facts about the browser and the country. It would still see nothing of the working surface: not how many files were queued, not one of their names, not a single dimension, not whether a run was ever started. This section gets rewritten on the day that switch is flipped, not afterwards.

Advertising

Resizly is built to pay for itself through Google AdSense, and nothing from Google is being requested yet. The domain has not been through AdSense review, the master switch in the code sits at off, and while it does no placement renders — no band, no label, no reserved gap. This disclosure is here in advance because the arrangement is real and approval will not come with an announcement.

Once units do render, they sit below the reading material, never above the tool and never inside it. Google is a separate company: serving an advertisement lets it set its own cookies or device identifiers, and Google’s own advertising policies are what describe the collection and the controls. Personalised advertising can be switched off in Google’s ad settings.

A served advertisement would hand Google what any third-party request carries: your IP address, the address of the page it appeared on, and your browser’s user agent. Nothing about your files is in that list and nothing about them could be, because this page never holds anything about them to send.

Children

Resizly is a general-purpose utility and is not directed at children. It asks nobody of any age for a name, an address, a birthday or an email, and it keeps no account to attach such a thing to. The only party that could ever receive something about a visitor here is the advertising above, on the terms above.

Changes, and how to ask

If this policy changes, the change will be on this page. We cannot send an announcement, because the site keeps no subscriber list of any kind. Questions about the site go to the team described on the about page.