Privacy

A file you open is decoded by the browser, measured, filtered and written back out, all inside the tab. It is not transmitted, not queued, not cached on a disk under our control and not retained, because none of those things has anywhere to happen: this is a static site with no server-side code, no API route and no storage attached to it.

Closing the tab ends it. There is no account to delete and no export request to make, because nothing was ever held.

The file is read through the browser’s own file interface into memory. Orientation is established from the header, the pixels are decoded, and the resampler runs in a Web Worker — a second thread inside the same tab, with the same absence of network access being used here. The export is assembled as a blob in memory and handed to the browser’s download machinery through a temporary object URL that is revoked a few seconds later.

One request is conditional and worth naming: opening a HEIC photograph causes a WebAssembly decoder to be fetched, because no browser decodes that format natively. That fetch carries the decoder to you. It does not carry your photograph anywhere.

No advertising unit is rendered on this page yet. Google AdSense is the intended supplier, and the four placements this site uses are already written out by hand in its own source with automatic placement switched off — but the switch that draws them is off until the domain is approved, so a visit today requests nothing from Google and sets no advertising cookie.

Once AdSense has approved the domain those bands fill, and what the frames inside them can observe is worth stating before it happens rather than after: cookies they set and read themselves, and the facts any HTTP request carries — the address of the page, an IP address, a user agent, a referrer. The one thing they cannot reach is the file you opened. It exists as an object in this page’s memory, and an advertising frame is a separate origin with no route across into it.

Traffic is not measured here either. Cloudflare Web Analytics is the intended instrument because it needs no cookie and builds no cross-site profile, but no property has been registered for this domain, the token in the source is still a placeholder, and the layout refuses to emit the beacon while it reads as one. Nothing records a page address, a referrer or a performance figure for this site today.

No account, no email address, no image, no filename, no dimension, no resolution and no record that a particular file was opened. The measurements on the panel are computed for the screen and discarded when it is redrawn. If a support question ever requires a file, it will be asked for explicitly and by email; nothing on this site collects one on its own.

The site is a utility with no social features and is not directed at children. Where this policy changes it will change in the text above, dated by the repository that publishes it; there is no mailing list to be notified through because there is no mailing list.