Privacy

A file you open is read by the browser into memory, worked on there, and written back out when you press save. It is never transmitted. It is never written to storage of any kind — not a database, not the browser's own local storage, not a cache. Close the tab and every trace of it is gone, and so are the settings you had reached unless you chose to keep them (below).

Three actions put something somewhere, and only when you press them. Save writes a file to your own downloads. Copy image puts a PNG on your own clipboard. Keep camera data, which is off unless you turn it on, copies the original JPG's EXIF block and colour profile into the saved file — and EXIF can include where a photo was taken, which is why it is off. A signature fitted for a form is handled the same way as any picture: in memory, gone when the tab closes.

The Save station has a switch, Keep my settings on this device, which is off unless you turn it on. When it is on, recipes you name and the settings of your last save are kept in this browser's own database (IndexedDB) on this device: the slider numbers and the name you typed, never the picture, its file name or anything measured from it. Nothing is created before you turn it on, nothing is sent anywhere, and recipes leave the device only as a file you export yourself. Turning the switch off deletes them, and so does this button:

Open the network panel in your browser's developer tools before you open a photograph. You will see the page load, the fonts load, and — the first time a HEIC arrives — a WebAssembly decoder load. You will not see a request carrying image data, because there is no code in this site that could make one. A build-time audit fails the release if any module that touches an image buffer references a network or a storage API, and a second audit fails it if a server route appears at all; this site is a set of static files with no server behind it.

If you prefer a stronger test: load the page, then disconnect from the network completely, then open a photograph and sharpen and save it. Everything works, because nothing in the operation needed the network in the first place.

This site counts its visitors with Cloudflare Web Analytics, and only on sharpenpicture.com itself. A small check in the page looks at the address it was served from; on the live domain it adds Cloudflare's cookie-free beacon, and anywhere else — a local copy, a preview build — it adds nothing and no analytics request is made.

The beacon records aggregate page views, the referring page, coarse country, browser and device type, and page-load timing. It sets no cookie, builds no cross-site profile, and receives nothing about the photograph, the controls you move or the file you save. Cloudflare receives your IP address as part of the request, as any server does; the figures this site sees are totals.

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. If that ever changes, this page will say so on the day it does, and before the change goes live.

This is a general-audience utility with no account system and nothing to sign up to. The one place personal information is asked for is the contact page, and only what you type there is sent, described below. The cookie-free analytics described above measures page use in aggregate and nothing else.

The contact page holds a short form. Pressing its send button posts four fields to a Google Form: the name, email address and message you typed, and the domain sharpenpicture.com. Nothing is posted until you press it, the page requests nothing from Google while it loads, and the form has no field that could carry a photograph. None of the sharpening passes talk to Google.

If the architecture ever changes — if any feature is added that sends a file somewhere — it will be labelled where it appears, not only described on this page, and this policy will say so plainly on the date it happens. As it stands there is nothing of the sort in the build.