I’m having the same problem and I need to remove every metadata from the document because it is leaking information to a possible attacker.
I don’t want to show what library and version I’m using because that can be exploited to target specific known bugs of the platform (.NET) or the library.
Giving back to the client browser a PDF file that contains the text “Aspose.PDF for .NET 22.4.0” is cancelling all the effort that I put into removing every .NET reference in the rest of the output, like OWASP reccomends:
I can imagine that this is required in the free version but I do have a Developer OEM key so I was expecting to have no watermarks in the produced files.
Is this behaviour mentioned in the EULA / License? Do I have to pay an additional fee to have this watermark removed?