Privacy

Last updated 16 November 2026

The short version: your photos are processed in your browser. No copy of them is sent anywhere.

What happens to a photo you drop in

The page reads the file from your device with the browser's file API. It is decoded into an in-memory canvas, drawn at the size you chose, and encoded again. The result is kept as a blob held by the page. When you close or reload the tab, the blob and the file reference are released and nothing is left behind.

The page sets a content security policy that allows no connection to any other origin. When you run a batch with the developer tools open, the network panel stays quiet; that is the policy working, not an omission in the log.

What is stored on your device

What the server sees

Loading the page is a normal request for HTML, JavaScript, a stylesheet and a font. Like any web host, the delivery network records the request: the IP address it came from, the browser's user agent, the time and the path. That record is about the download of the page, not about the photos, which never appear in a request.

Metadata in your photos

Re-encoding removes the EXIF, XMP and IPTC blocks, so coordinates, device model, capture time and software version do not travel with the output file. The studio shows what it found in each file in the tray. This is a side effect of writing new pixels, and it is also deliberate: a photo of your home should not carry your home address into a message.

The downloaded file carries a modified date, as every file on a computer does. That is the time of the download, not of the original capture.

Third parties

There are none in the page. No analytics script, no advertising tag, no social embed, no font or library loaded from another domain. Inter, JetBrains Mono and Pretendard are served from this host.

Contact

Questions about this policy go to [email protected].