Privacy policy

Your images

The image tool on this site runs entirely in your browser. When you select a file, it is read into your browser's memory using the File API, parsed there, and rewritten there. The cleaned file you download is created in the page from an in-memory copy.

No part of your image is sent to our servers. There is no upload endpoint for image data, no temporary storage, and therefore no retention period or deletion schedule for your files — because we never receive them. You can verify this by opening your browser's network tab while using the tool, or by disconnecting from the network after the page has loaded and cleaning an image anyway.

If a future feature requires server-side processing for a file type the browser cannot handle, that feature will say so explicitly at the point of use, and this policy will be updated before it ships.

Your metadata

The metadata values read from your file — camera model, GPS coordinates, timestamps, prompts and everything else — exist only in the page while your tab is open. They are not transmitted, not written to storage, and not included in any analytics event.

Metadata values and filenames are never placed in the URL, so they cannot appear in browser history, referrer headers or server access logs.

Analytics

This site uses Google Analytics 4 to measure how many people visit, which pages they land on, and which tools they use. That means your browser loads a script from Google and sends measurement data to Google's servers, and Google acts as a data processor for that information.

Alongside page views, a small number of product events are recorded: a tool being opened, a file being selected, metadata being detected, metadata being removed, a download, and processing errors.

Those events carry only non-identifying facts: the image format, a coarse file-size bucket (for example “1–5 MB”), a count of metadata fields, an error reason, and which page the tool was used on. The payload is filtered against a fixed list in code, so image content, metadata values, GPS coordinates and filenames cannot be included even by mistake — there is no field capable of carrying them.

Google Analytics collects its own standard information as part of a page view, including your IP address (which Google truncates before storage), approximate location derived from it, device and browser type, referring page, and an identifier stored in a cookie. We do not use Google Signals, we do not link this property to Google Ads, and no remarketing audiences are built.

Browsers that send a Do Not Track signal are excluded from the product events described above.

Cookies

Google Analytics sets cookies in your browser — typically `_ga` and `_ga_<id>` — to tell repeat visits apart from new ones. They contain a randomly generated identifier, not anything you have typed or uploaded, and Google's default retention for the associated data applies.

The site sets no cookies of its own, uses no local or session storage, and loads no advertising cookie or cross-site identifier.

You can block these with any browser content blocker, by using Google's official opt-out add-on, or by enabling Do Not Track. None of it affects the tools: every one of them runs entirely in your browser and works with analytics blocked or the network disconnected.

Third-party services

Two companies are involved in serving this site. Vercel hosts it and, like any web host, processes requests and may keep short-lived operational logs including IP addresses. Google receives the analytics data described above.

Fonts are served from this site's own domain rather than a third-party font service. No advertising network, session recorder, heat map, chat widget or social media embed is loaded.

Your images and PDFs are not part of any of this. They are never uploaded, so they never reach Vercel, Google, or us.

What this tool cannot protect you from

Removing metadata reduces what a file discloses. It does not make you anonymous. It cannot affect copies of a file you have already shared, information visible in the picture itself, or data collected by any service you upload to afterwards.

Changes and contact

This policy will be updated if the way the site handles data changes, and the date below will change with it. Questions can be sent to hello@deleteimagemetadata.com.