Privacy, by design.

Unmeta processes your images locally. We built it to work without receiving them.

What happens to your images

Image inspection, decoding, re-encoding, verification, and ZIP generation happen in your browser. The application has no image upload endpoint and does not send your images or their metadata to external services. No account is required.

Temporary browser memory

Your selected files, previews, and processed outputs exist in memory for the current session. Unmeta does not save image data in cookies, localStorage, sessionStorage, or IndexedDB. Removing an image, clearing the workspace, or leaving the page releases application references and object URLs. Browser and operating-system memory handling, swap, extensions, and downloaded files are outside the application’s direct control.

Website requests and hosting

Your browser requests the static website files from the hosting provider. That provider may receive standard connection information such as IP addresses, request times, browser headers, and requested URLs, according to its own policies. These requests do not contain images selected through the application. Unmeta includes no advertising, analytics, third-party tracking scripts, or error-reporting services.

Downloads and sharing

Downloads are saved where your browser places them. The original image is unchanged. Only share the processed output if you want to avoid sharing the original embedded metadata. Browser encoders may add technical information, and the inspector cannot detect all possible metadata or pixel-based watermarks.

Your control

You can remove individual files or clear the workspace at any time when processing is idle. Cancel pending work to stop a batch after its current image finishes. Refreshing the page starts a new, empty session.