Privacy Policy

2.1 Uploading a file or dragging it in

The image is read and processed entirely in your browser using JavaScript (ExifReader and piexifjs). It is never transmitted anywhere. It exists only in your browser's memory for the duration of your session and is discarded when you close the tab, refresh, or upload another image.

2.2 Loading an image from a URL — the one exception

Browsers block a webpage from directly reading pixel data of an image hosted on a different domain (a security restriction called CORS). To work around that for the "load from URL" field, we route the request through tempfile.org, a third-party temporary file host we don't operate:

• What we send: only the URL you typed, not any file already on your device.
• What tempfile.org does: fetches the image at that URL and hosts it briefly so your browser can retrieve it. Our request sets its expiry to 1 hour; per tempfile.org's own privacy policy, it also keeps access logs for up to 30 days and error logs for up to 90 days.
• What tempfile.org does not do: strip metadata. The file comes back exactly as it was at the source URL — all metadata analysis and removal still happens locally in your browser afterward, same as any other upload.
• What tempfile.org says about the file itself: their policy states they don't use hosted file content for advertising, analytics, or profiling, and don't share it with third parties outside legal or abuse-related exceptions. That's their commitment, not ours to enforce — see their privacy policy and terms if you want the full picture before using that field.

If you'd rather avoid this entirely, download the image yourself first and use the regular upload/drag-and-drop instead — that path never leaves your browser.

3.1 Google Analytics — every page

We use Google Analytics to see aggregate traffic patterns: which pages get used, roughly where visitors come from, and general browser/device mix. This runs on all pages, including this one. It does not have access to your images or any metadata extracted from them — it only sees that a page loaded, not what you did with the tool on it.

Opt out via the Google Analytics Opt-out Browser Add-on, or read Google's Privacy Policy.

3.2 Google AdSense — three pages only

We show ads through Google AdSense to cover hosting costs. Ads currently run only on the EXIF Remover, Metadata Viewer, and Privacy Checker tool pages — not on this page, Help, FAQ, Contact, or Terms. AdSense may use cookies for ad personalization based on your browsing across sites; it has no access to the images you process here.

Manage ad personalization at Google Ad Settings.

3.3 Google Maps — two pages, and only if your image has GPS data

If an image you process on the EXIF Remover or Privacy Checker contains GPS coordinates, we embed a Google Maps view so you can see exactly what location the photo exposes. This only loads when GPS data is actually found — no map, no request to Google, if there's nothing to show. Loading the map does send your IP address to Google, the same as visiting any page with an embedded Google Map.

Read Google's Privacy Policy for how they handle that.

3.4 tempfile.org — only if you use "load from URL"

Covered in full in Section 2.2 above, since it's specific to what data actually moves and when — not a generic third-party disclosure.

3.5 Hosting and CDN — Cloudflare

We use Cloudflare as our CDN, mainly for caching static assets and speeding up delivery. Like any CDN sitting in front of a website, Cloudflare automatically logs IP addresses, request headers, and basic access/error data for security and performance — standard behavior for the service, not something specific to what this tool does with your images. See Cloudflare's Privacy Policy for details.