Nothing about your photo leaves your device.
Written field by field, because a privacy page that describes a category rather than a codebase is not worth reading.
Your photo
The file you choose is read by your browser with the File API and parsed on the page you are looking at. There is no upload, no server-side pipeline, and no copy of your image anywhere but in the tab. Cleaning or editing produces a new file, also in the tab, which your browser then saves the way it saves any download. The file on your disk is never modified. Closing the tab is the end of it.
What the analytics counts
Page views are counted by Umami, which sets no cookie and no identifier and cannot follow you to another site. Alongside that, using a feature records six fields and no more: which feature it was, the file type as your browser reports it, whether the file carried GPS, and whether it was a JPEG that could be edited. The file itself, its name, the coordinates and every tag value stay in the tab. Whether a photo had a location is recorded as true or false; where that location was is not recorded at all.
Advertising
Guide pages can carry advertising from Google AdSense. No page with the workspace on it does, and that is not a matter of restraint: the list of surfaces allowed to serve an ad script lives in one file, defaults to refusing, and a test fails if a workspace page is ever added to it. Where no publisher id is configured, no advertising script is requested at all — not hidden with styling, not loaded and left unused.
There is nothing to submit
No accounts, no sign-in, no forms, no newsletter, no comments, no uploads. Nothing asks you for an address or a name, so there is nothing of that kind to store, leak or hand over. Typefaces are served from this domain rather than from a font network, so opening a page does not announce the visit to a third party before you have done anything.
What is outside this page
The server that hands you these files sees a request the way every web server does — an address, a time, a user agent — because that is how HTTP works. Where an advertising script does run, what Google does with it is governed by Google, not by this page. Saying otherwise would be claiming authority over something outside the code, which is the failure this whole site is built to avoid.