Privacy policy

The short version

This page reads the file you pick, changes its pixel dimensions inside the tab you are looking at, and writes the result to your downloads folder; there is no server behind it to send anything to.

That is not a promise about our conduct, which you would have to take on faith. It is a description of the architecture: the site is static files, there is no endpoint to receive an image, and no code of ours runs anywhere except in your browser. You can check it — open your browser's network panel, resize something, and watch nothing leave.

What happens to a file you open

• The browser reads the file from your disk into memory in this tab. The first 128 kilobytes are examined to work out what the file really is and whether it carries an orientation tag.
• The pixels are decoded, rotated if the browser has not already done it, and held as a bitmap in memory.
• Resampling and encoding run in a worker thread in the same tab.
• The result is written to your downloads folder by your browser, from memory.
• Closing or reloading the tab discards all of it. Nothing is written to local storage, session storage or a database, and nothing survives the tab.

That list has one exception and it is worth stating precisely. Opening a HEIC makes the page fetch its decoder — a WebAssembly module — from the same server the rest of the site came from. Code travels to you; nothing travels back. Your file is not attached to that request, is not named in it, and is decoded in the tab like every other format once the module has landed.

What we count

Cloudflare Web Analytics counts aggregate page visits and loading performance for this domain. Its cookie-free beacon records the requested path, referrer, coarse country, browser and device category on a property that is not shared with the other tools.

The beacon sets no cookie, builds no cross-site profile and receives nothing about the file you opened, the dimensions you entered or the file you saved. All resize work remains inside the browser tab.

Advertising

This site is built to carry Google AdSense, in positions chosen by hand rather than wherever an automatic script would drop them. It is not serving anything yet: the account is still waiting on review, so no advertising code loads and no unit appears on the page you are reading. The terms below are the ones that apply the day it is switched on, written down in advance because you should be able to read them before they bind you rather than afterwards:

• Once units are live, Google is able to set cookies or read device identifiers in order to choose and measure ads, subject to whatever consent your jurisdiction requires and your browser settings allow.
• Google would see the address of the page an ad sat on, which for this site tells it you were on a resizing page. It cannot see your file, its name, its dimensions or anything else about it, because none of that leaves your browser and none of it is written into the address.
• An ad blocker changes nothing about whether the tool works, before or after that switch. The resize runs the same either way.
• You can manage what Google personalises at its own advertising settings page. We have no control over that and cannot change it on your behalf.

Hosting logs

The files are served from a content delivery network, and like every web server on earth it records requests: an IP address, a timestamp, the file requested, a user-agent string. That is the ordinary operation of serving a web page and it happens whether or not you use the tool. Those records are the host's, kept to their retention schedule, and they contain requests for HTML, CSS, JavaScript and fonts — never a picture of yours, because a picture of yours is never requested from anywhere.

Children, accounts and contact

There are no accounts, no sign-in, no email collection and no form on this site. Nothing is knowingly collected from anybody of any age, because nothing personal is collected from anybody at all. If a genuine privacy question about this site is not answered above, the answer is almost certainly that the thing you are asking about does not exist here.

Changes

If this policy ever changes it will be because the site changed, and the change will be described here rather than summarised. In particular, if any part of this tool ever stopped running locally, that would be stated on the tool itself and not buried on this page.