Privacy, in plain language.

Your image stays on your device. The compressor does not upload the image, file name, local path, pixel dimensions, preview, or image-derived content to an application server.

Local image processing

Decoding, resizing, JPEG encoding, candidate comparison, and download creation happen in your browser using JavaScript, Web Workers, WebAssembly, Canvas, and IndexedDB.

Recent results

If you create an output, the browser may keep that output—not the original—in IndexedDB so you can return and download it. At most three outputs are kept. Each is automatically deleted exactly one hour after its own creation. You can clear all outputs at any time.

First-party measurement

The browser creates a random first-party identifier and rotates it every 30 days. If analytics is enabled at deployment, events are limited to an allowlist such as page viewed, processing started, processing succeeded, and downloaded. They may include broad target, format, result, and duration buckets. They cannot include image bytes, file names, paths, pixel dimensions, or content.

No advertising trackers

The launch version does not use third-party advertising pixels, session replay, heatmaps, remote fonts, or cross-site tracking cookies.

Clearing local data

Use “Clear all” under recent results or clear this site’s storage in your browser. Browser private mode may remove data sooner.

Contact

A public privacy contact address must be added before production deployment. Until then, this build is not presented as a live public service.