For all of the usual reasons we strip metadata too. Then we add our unique identifier in a custom XMP namespace. But we have a workaround for the issue you desc

For all of the usual reasons we strip metadata too. Then we add our unique identifier in a custom XMP namespace. But we have a workaround for the issue you describe. Users upload their assets to our storage with the unique ID embedded. They then get a shareable link or HTML that loads the asset and our verification Javascript directly from our embed platform. You can see it in action here: https://embed.tovera.com/preview/c65b0658ab6e4d89963b1e0a319a1c0a https://embed.tovera.com/preview/c65b0658ab6e4d89963b1e0a319... The image itself shows up in a social media post, website, etc just as it normally would but if a user clicks it they see the above, with all of the extended metadata, etc.