Local processing
What stays in your browser?
Photos picked in the editor are processed in this browser, not sent to a server.
Photos you pick directly in the editor are read into memory, then covered and saved on your device. Face finding runs on the device too. Normal editing has no photo upload feature, remote translation, ads or payment screen.
Loading the page isn't sending your photo
Opening the page downloads the screens, the program and the face model from the site. Your photos, file names and covered areas are never part of those requests. Browser extensions, the operating system and device backups are outside what GarimPic controls.
Where your work lives, and clearing it
Normal edits to photos picked directly in the editor stay in memory. Refreshing or closing the tab may lose them. If GarimPic remains in an earlier installed app’s share menu, do not use it; pick files directly in the editor. See the privacy notice for the on-device photo cache an earlier share may leave behind.
My output settings keeps only the short names and save options you chose to store, up to ten. No photos, file names, covered areas or titles. Delete one or all there; clearing photo work is separate. Private windows or clearing browser data may remove them, and they never sync to another device.
"Clear photo work" lets the app let go of your photos. It does not promise they cannot be recovered from the device.
What's left in a saved photo?
A covered photo is saved as a new file from new pixels. Camera details (EXIF), the location inside them, comments and embedded thumbnails are left out. The saved file is opened again to check its size and that every cover is solid. PNG and WebP keep transparency; JPEG goes onto white. Whether everything sensitive is covered is still yours to check.
Saved photos are new files. Covers stay solid; colour and compression may differ slightly from the original.
Blur and mosaic can't promise nobody is recognisable. Look at the whole photo and its context too.