Why privacy matters for photo tools
Photos can contain faces, storefronts, homes, vehicles, job sites, customer information, or private location context. A geotagging tool should not require uploading originals unless server processing is clearly necessary.
GeoTag Photos is designed around browser-side processing. The app uses local browser APIs and a worker pipeline to read metadata, write GPS data, resize, watermark, build ZIP files, and generate reports.
What still needs a server
A real product still needs server routes for login, plan limits, payment webhooks, usage records, address search, and saved location presets. Those flows do not require the original image files.
Address search is the main exception to a purely local workflow because a geocoding provider needs the search query to return coordinates.
How to verify that originals are not uploaded
Open your browser developer tools, process a photo, and inspect the Network panel. You should not see the original image file posted to an upload endpoint.
In our testing, export workflows are checked to make sure no server upload route receives original image data.
Practical privacy habits
Even with local processing, keep good file hygiene. Do not email sensitive originals unless support asks for a minimal sample. Keep source files and exported files in separate folders. Review metadata before publishing if location privacy is sensitive.
Geotagging is powerful because it adds location context. Use that context only when you have the right to publish it.