Last updated: September 2026.

ImgResize does its work where your files already are: inside your browser. This page lists, in plain terms, the data involved in using the site — and which of it never reaches us.

Data that stays with you

Every image you open. Resizing, cropping and format conversion happen in the tab you have open: the file is read from your disk, drawn onto a canvas and encoded again, all by JavaScript on your own machine. You can confirm it in the browser’s network panel — or by cutting the connection after the page loads: no upload request ever fires. Orientation metadata from the source file is used to draw the preview correctly and then discarded with everything else; the copy you download carries no EXIF at all.

The numbers you type — a target width, an aspect ratio, a format — live only in the page’s memory.

Data the infrastructure sees

• Cloudflare (hosting): ordinary request metadata — your IP, user agent, the URL requested, when — used to serve pages, resist abuse and measure aggregate traffic. There are no accounts and no forms storing data, so there is nothing for those logs to attach to.
• Google AdSense (advertising): if ads are running, the network may set or read cookies to count impressions and, where permitted, personalise them. Opt out in Google’s Ads Settings or by blocking third-party cookies — the resizer is unaffected.

Data we simply don’t have

We can’t see, keep or leak your images because we never receive them. File names, pixel counts and resized results aren’t transmitted either, so they can’t be logged, sold or breached here.

Controls and contact

• Everything except the tool works with JavaScript off.
• Cookies and ad personalisation are governed by your browser settings.
• Questions about this policy: hello@photopassport.online.

Revisions to this policy are posted on this page with a new date.