Privacy Policy

The short version

Your images are never uploaded. Every file you select is decoded and re-encoded by WebAssembly codecs inside your browser, and the bytes never cross the network. That guarantee has no exceptions and no asterisks.

The site does collect anonymous performance analytics — page paths, load timings and Core Web Vitals — so we can tell whether the tool is fast enough. It does not receive your images, your file names, or anything that identifies you. The details are below, written to match what the code actually does rather than what sounds reassuring.

Your images

ImageAlchemy runs entirely client-side. Images you select are decoded and re-encoded by WebAssembly codecs inside your browser and are never transmitted over the network. We operate no server that receives image data, so there is no store of your files to lose, subpoena or leak.

This extends to the Pro website audit, with one deliberate exception: to audit a page you do not own, a request has to be made to fetch that page's HTML. That request fetches the public URL you type in — never your images, and never any file from your device. See Pro audit below.

Analytics we do run

The site loads a lightweight, privacy-oriented analytics script that records aggregate, non-identifying information: the page path you visited, the referring URL, your browser's user-agent string, a country derived from your browser's locale setting, page-load performance metrics (including Core Web Vitals timings), and a random identifier generated per visit.

That random identifier is created in your browser, is not tied to any account, and is not used to build a profile across other websites. We do not run advertising pixels, we do not sell or share this data with data brokers, and we do not attempt to identify individual visitors.

We are describing this explicitly because vague privacy copy is worse than none. If you would prefer not to be measured at all, any content blocker or the browser's tracking-protection setting will suppress the script, and the tool will continue to work exactly the same — it is client-side and requires no network access to function.

What is stored on your device

Two categories of data live in your browser's local storage, both on your device only:

Your preferences — the theme you picked (light or dark), the compression preset you last used, the auto-compress toggle, and your Pro licence key if you have purchased one. These exist so the tool remembers your setup between visits.

A queue of pending analytics events — the analytics script buffers measurements locally before sending them, and flushes the queue once it can reach the endpoint. This contains the performance and page-path values described above, never image data or file names.

Nothing in local storage is shared with other websites. Clearing your browser's site data removes all of it, and the tool will simply start from its defaults.

Pro website audit

The Pro audit is the only feature that makes a network request on your behalf. When you submit a URL, the page's HTML is fetched by our proxy so it can be parsed — browsers block a page from reading another origin's HTML, so this step cannot happen client-side.

The proxy receives the URL you typed, fetches only public HTTP and HTTPS addresses, and refuses private, loopback and internal network ranges. Parsing, measurement and scoring all happen back in your browser; the fetched HTML is not retained as a corpus, and no audit results are stored on a server after the response is returned.

Hosting and delivery

The website itself — HTML, CSS, JavaScript and the WebAssembly codec binaries — is delivered over HTTPS. The hosting platform necessarily processes standard request metadata such as timestamps, IP addresses and requested paths in order to serve the page and protect against abuse, under its own privacy terms. Your image data is not part of those logs, because it is never sent.

Your controls

You can block the analytics script without affecting any feature. You can clear local storage at any time to remove your preferences and the pending event queue. Because we hold no account and no personal record, there is nothing to request, correct or export — there is no profile to retrieve.

Changes to this policy

If the instrumentation or data handling changes, this page changes with it in the same release. The guarantee that your images never leave your device is structural — it follows from the architecture, not from a promise — and will not change while the tool remains client-side.