Skip to the privacy policy
ExifInfoViewer

Legal

Privacy Policy

ExifInfoViewer reads and removes photo metadata entirely inside your browser. Your photos never leave your device, so there is very little data for this policy to be about — but here is all of it, in plain language.

Last updated 18 August 2026

The short version

We do not receive your photos. Both the EXIF viewer and the EXIF remover run as JavaScript on your own device. The file you choose is read from local memory, parsed locally, displayed locally and discarded when you close or refresh the tab. Nothing is uploaded to a server, nothing is stored, and nobody at ExifInfoViewer can see the images you open or the metadata inside them.

We do not ask you to create an account, we do not run analytics or advertising scripts, and we do not set cookies.

Your photos and their metadata

When you drop a photo onto the tool, your browser hands the file to the page as an in-memory object. The metadata is extracted with a library that runs in the same tab. Results are rendered straight into the page. No copy of the file, of a thumbnail or of the extracted metadata is transmitted anywhere.

The same is true of the EXIF remover: the cleaned file is assembled in your browser and saved through your browser's own download mechanism. Your original file is never modified and never sent.

Because the processing is local, clearing a photo or closing the tab is enough to remove it completely. There is no server-side copy to delete and no retention period to wait out.

Cookies and local storage

ExifInfoViewer does not set cookies and does not write your photos, metadata or preferences to localStorage or sessionStorage. There is no consent banner because there is nothing to consent to.

Analytics and advertising

We do not run Google Analytics, advertising pixels, fingerprinting scripts, session recorders or third-party trackers of any kind. Fonts are self-hosted from our own domain rather than loaded from a font CDN, so that opening the site does not announce your visit to another company.

The optional map

If a photo contains GPS coordinates, the viewer shows those coordinates as text and offers an optional map. The map is not loaded until you ask for it. When you do, your browser requests map tiles from OpenStreetMap, and that request necessarily includes the coordinates being displayed and your IP address, both of which are handled under OpenStreetMap's own privacy policy. If you would rather not share the location with anyone, simply do not open the map — the coordinates are already shown on the page without it.

Server logs

The site is a set of static files served by a hosting provider. Like every web host, ours records standard request information — IP address, timestamp, requested URL, referrer and user-agent string — for security, abuse prevention and the basic operation of the service. Those logs cover page requests only. They cannot contain your photos or their metadata, because those are never sent.

Email you send us

If you write to frontendedy@gmail.com, we receive your email address and whatever you put in the message, and we keep it long enough to reply and to keep track of the issue. We do not add you to a mailing list and we do not pass your message to anyone else. Please do not attach photos you consider sensitive — you almost certainly do not need to send us a file for us to help.

Children

The service is available to everyone and collects no personal information from anyone, including children. We do not knowingly hold any data about a child because we do not knowingly hold data about any individual user.

Your rights

Regulations such as the GDPR and the CCPA give you rights to access, correct, export and delete the personal data a service holds about you. In our case, the honest answer is that we hold none from ordinary use of the tools: no account, no profile, no photo, no metadata. If you have emailed us and want that correspondence deleted, tell us at frontendedy@gmail.com and we will remove it.

Changes to this policy

If the way the site works ever changes — for example, if a feature were to require a network request — this page will be updated before that feature ships, and the date at the top will change with it. The client-side, no-upload design is the point of the project, so any such change would be described here explicitly rather than quietly.

Contact

Questions about this policy can go to frontendedy@gmail.com, or through the contact page.