Privacy

Choosing a photograph hands it to the browser, not to us. It is decoded into memory, measured, corrected and — if you press Save — written back out as a new file by the same tab. None of it travels over the network, because there is nowhere for it to travel to: this site is a set of static files with no server, no database and no address that would accept an image. The site counts page views on its live domain with a cookie-free service, described below; that count never includes anything about a picture.

The picture becomes a bitmap held in the tab’s memory and a second, smaller copy for the screen. Both are discarded when you open another picture, close the tab or navigate away. The picture itself is never written to the disk, to local storage or to a cache by this site — there is no “recent files” list here and no way to build one. Your original file is never modified; saving produces a new file, named after the old one.

The saved file carries pixels and nothing else: location (GPS) and camera details are not in it, and the orientation is baked into the pixels rather than written back as a tag. The one exception is a density (DPI) figure, written into the JPEG header only when a form target you chose asks for one. A receipt or recipe file you save holds numbers only; the receipt leaves out the file name unless you tick the box that includes it.

Four things can be kept, all in your own browser and none of them containing a picture. A recipe you choose to save is a name you type plus slider positions, strength and switches, in local storage; Delete in the Recipes panel removes it. A custom form target you keep is a name and the numbers you typed, also in local storage. Export → Storage counts both and clears each, or everything, with one button. If you open a HEIC, its decoder is code the browser may keep in its ordinary HTTP cache. And if you agree to download a local AI model on the AI photo enhancer, the model file is kept in the browser’s Cache Storage so it does not download twice; the AI panel shows how much is held and removes it with one button. Clearing this site’s data in your browser settings removes all four.

• The pages, scripts, fonts, the image engine and the AI runtime come from this domain.
• The HEIC decoder comes from this domain, and only when you open a HEIC.
• A local AI model file comes from our model file server, and only after you press the button that names its exact size. The request asks for the model file and nothing else; your photograph, its pixels and its measurements are never part of it. The model then runs inside your tab.
• The analytics beacon, on enhancepic.com only, as described next.
• The contact form, only when you press its send button.

This site uses Cloudflare Web Analytics, with a property that belongs to this domain alone. Its small script loads only when the page is served from enhancepic.com — never on a preview copy or on your own machine. It records page views: which page was opened, the page you came from, your country, and the broad class of browser and device. It sets no cookie, stores no identifier in your browser, and does not follow you between sites.

The half of this that matters most is the half about your picture. Nothing can report what you opened, what the correction decided or whether you saved anything, because the code that would send it does not exist and the build refuses to let anyone write it: a script reads the image code for any network or storage call and fails the publish if it finds one. The analytics script is not given access to the picture and could not reach it if it tried.

There is no advertising on this site and no advertising script on any page.

There is no account and no sign-in, and the corrector itself asks nobody for a name, an address or an age. The one form on the site is the contact page, described next.

The contact page sends exactly what you type into it — a name, an email address and an optional message — together with the name of this site, to a Google Form, and it does so only at the moment you press its send button. Google keeps that response under its own policies. Nothing is sent while you type, no photograph or setting is ever attached, and apart from that one button nothing on this site talks to Google.

If this policy changes, the change will be visible in the page itself rather than announced — there is no mailing list to announce it to. The commitment that will not change is the first one: the correction happens where the picture already is.