I built a zero-server image anonymizer: Privacy tools shouldn't store your data.

Hey all,

I wanted to share a project I just pushed live: EXIF B Gone.

The Issue I've had:

Every time you take a photo with a smartphone, a hidden EXIF data profile is baked into the file. It caches your exact GPS coordinates, camera serial numbers, and specific timestamps. If you upload these raw images to public marketplaces, forums, or community platforms, you are giving away your physical location data.

Most online "metadata cleaners" force you to upload your personal photos to their remote cloud servers to process them. To me, that completely defeats the point of a privacy tool.

My Answer to that:

I built EXIF B Gone to fix this. It’s an entirely serverless web application that handles image scrubbing completely inside the user's local browser sandbox.

- You upload nothing. Your photos never touch a remote server, API, or external database.

- When you drop an image, a local HTML5 canvas script isolates the visual pixel plane from its historical file wrapper, reconstructing a clean asset from scratch and instantly vaporizing the hidden tracking payload.

- There's no account registration, no payload limits, and a clean dark-mode UI.

This is just Phase 1. Now that the core image processing architecture is live and stable, I’m mapping out a Phase 2 upgrade to introduce more privacy features.

The project is live at exifbgone.com.

I’d love for you to try dropping an image in to see how the local processing speed feels on your machine and would love to hear your thoughts, feature requests, or any feedback on the UI/UX!

#privacy #own-your-data #build-in-public #side-projects