It doesn't explicitly say it, but there is hardly any other reason why it would add server generated ID (from authenticated session) to the saved file.
We've probably lost the fight over GenAI marks, at least for now, and I do understand the need for them. However the same technology that can embed an invisible watermark that survives a round of photographing, printing, crumbling and scanning back - can be used to embed more information than just "it's AI generated". Encoding GUID is just a harbinger; as a next step, why not encode the app that produced the image? Also a hash of its license key? Hell, what's stopping an app from doing it itself, watermarking its own window before passing the pixels to OS for compositing?
"Robust GenAI watermark" today is "robust general-purpose DRM watermark" tomorrow :).
All the slippery slope nonsense on this page has failed so many times it’s not worth debating. If you don’t like this tool, use another. When they embed your social security number and face and address in the mark get back to me.