Privacy policy

Last updated: 2026-08-30.

Your images

• Images are never uploaded to our servers. All processing happens in your browser.
• We do not store your original images in localStorage, cookies, or any database.
• Processed results are created only when you download them, and object URLs are released when you remove a file or close the page.
• EXIF and GPS data are never transmitted anywhere; the Metadata Remover strips them locally.

Browser storage

We store a single preference — your light/dark theme choice — in localStorage. No image data or filenames are ever stored.

Analytics

This site runs Google Analytics 4 with IP anonymization enabled. It is on by default, and it is the one third-party script the site loads out of the box. It records page views and a short, fixed list of events about how the tools are used.

That list is an allow-list in our code, and anything not on it is discarded rather than sent:

• tool_open — which tool page was opened.
• process_start, process_success, process_error — that a run began, finished or failed.
• output_format — the output format chosen, e.g. “webp”.
• batch_size — a bucket such as “2-5” or “11-plus”, never an exact count.
• A file-size bucket such as “1-to-5mb”, never an exact byte count.

Image content, file names, image hashes, dimensions, EXIF and GPS data are never sent. There is no code path that could send them: an automated test processes an image and asserts that no request leaves carrying the file name or any payload larger than a few kilobytes.

Blocking analytics — with an extension, a content blocker or Do Not Track — has no effect on any tool. Everything works identically with the script blocked.

Advertising

If advertising is enabled by the operator, third-party ad scripts (such as Google AdSense) may set cookies subject to their own policies. The tools work fully with ads and analytics disabled or blocked. See our cookies page for details.

Error logs

We operate no server that receives your files, so there are no server-side logs of image content, and we run no error-reporting or session-replay service. When something fails, the message is shown to you in the page and goes nowhere else. Those messages are written by us and never contain image bytes, metadata values or a raw stack trace.

Contact

Questions about privacy? Email [email protected].