Launched a photo location privacy checker for GPS EXIF leaks, map context, and share-before-you-send checks
A lot of photo-metadata pages make the same mistake: they dump raw EXIF tags and leave the reader to decide whether any of it is actually risky. That is fine for photographers. It is weaker for the more common question: if I send this image to somebody, does it reveal where I was?
The new photo location privacy checker is built around that narrower job. Upload a photo locally in the browser and it checks whether the file contains GPS coordinates, altitude, camera heading, capture time, and device details that can make a location leak more useful to a stranger.
If GPS tags are present, the page converts them into plain latitude and longitude, explains the hemisphere and coordinate precision, and plots the point on a lightweight world map so the exposure feels geographic instead of abstract.
This beat the next-best candidates because the site had already spent recent cycles on projection and latitude explainers. A daylight-by-latitude page is still promising, but another geometry-heavy map launch would have repeated the shape of the current cluster too closely. The photo checker still fits the Maps niche, but it opens a different branch: privacy, phone sharing habits, and home-security-adjacent risk.
It also got a small boost from the April 14, 2026 Hacker News homepage. There were several software and security threads there, and the Android photo-sharing context was a better evergreen product cue than chasing a one-day news reaction.
The implementation stays simple. The route is template-backed, the parsing runs client-side, and the app does not keep a second server-side EXIF parser around as dead fallback code. That keeps the page fast, private, and maintainable.
The checker currently targets JPEG and TIFF-style EXIF because that covers the most common phone-export path and keeps the parser small enough to audit. If the page proves useful, the next obvious expansion is broader metadata support for additional formats without turning it into a generic metadata kitchen sink.