Privacy at EnlargePicture

Upscaled inside this tab. The original never travels.

There is no account, no sign-in and no server that sees your files. The pages are static files; the enlarging, the clean-up, the model runs and the file-size solving all happen in code running inside your own browser tab, on pixels your browser decoded from a file you chose. No request this site makes carries your picture, its file name, its dimensions, its camera details or the enlargement record. The animated-GIF, pixel-art and TIFF readers and writers are this site’s own code and run in the tab too.

The pages, their code and their fonts, from this domain. When you open a HEIC file — the format an iPhone shoots — a decoder of about two megabytes, also from this domain, because no browser ships one. And, only after you press a button whose label states the size, a trained model and the runtime that executes it:

The model files come from our model file server rather than a public model hub, and the runtime (13,986,063 bytes in all) from this domain. A request for a model file carries what any request for a static file carries — your address, your browser and its language — and nothing about the picture. The same bytes go to everyone who asks. The model comes to the picture; the picture never goes to the model.

Nothing about any picture, ever. Two things can leave your browser, and neither involves a file you opened:

Page-view counts, on enlargepicture.com only. This site uses Cloudflare Web Analytics, which is cookie-free. When you open a page on the live domain, a small script from Cloudflare reports that the page was viewed: the page address, the address you came from, your browser and device type, and a rough country worked out from your connection. It sets no cookie, builds no profile and cannot see the picture in your tab — it reads a web address, not the contents of a canvas. The script loads only on enlargepicture.com; previews, copies of the site and local test servers never load it. Cloudflare describes what it collects in its privacy policy.

A note you send from the contact page. Pressing Send there posts the name, email address and note you typed, with the name of this site, to a Google Form that we read. Nothing goes while you type, and no picture can be attached. No other page sends anything.

Model files, after you press a model’s button: kept in this browser’s cache under a versioned key, so a second visit fetches nothing and works offline. The Enhance panel carries a Delete control for each file and one for both.

Custom form presets, if you save one on the online-form page: the numbers you typed and the name you gave it, in this browser’s local storage. The preset list has a Delete button beside each one. Clearing this site’s data in your browser settings removes both kinds.

One picture, only if you ask. After a model run has started, the Enhance panel offers “Keep this picture if the tab crashes”, off by default. Ticked, it keeps that one picture and your settings in this browser’s IndexedDB for this site, and nowhere else. It is deleted when you save, when you open another picture, when you press “Forget it” on the offer that appears on your next visit, or with the button below.

Otherwise your pictures are never stored: closing the tab releases them, and there is nothing on our side to delete.

Inside the files you save, nothing is added unless you switch it on: the enlargement record written into the file as text, and — for a JPG saved from a JPG — your photo’s camera details, with the location blanked out unless you tick that too. Both are off by default.

Or delete everything this site stored here, in one press; the page says what it removed and how big it was:

Advertising on this site is served by Google AdSense; the ad script loads on the page but never receives your images, file names or anything you do in the tool. Advertising on this site is served by Google AdSense; the ad script loads on the page but never receives your images, file names or anything you do in the tool.

EnlargePicture is run by its own operator. Questions about this page go through the contact page. When the code changes what travels, this page changes in the same release — the build checks that the analytics, the model files and this page agree.