Hi @MiKi,
Welcome to the Docusign Community! Thank you for outlining the security questions around using Docusign Stamps in your B2B workflow.
The short answer is that Docusign Stamps can be appropriate for a workflow in which a customer applies a visual corporate mark to a document, provided the customer understands that the stamp is a reusable image asset, not a secret credential or a cryptographic electronic seal.
How the uploaded stamp is stored and protected
When a recipient uploads a stamp through Manage Profile > Stamps, Docusign treats it as that user’s personal stamp. Docusign’s support guidance distinguishes these personal stamps from account-managed stamps.
Docusign’s public security documentation does not describe or promise a particular encryption implementation solely for the uploaded stamp image. Accordingly, we recommend describing the image as protected under Docusign’s eSignature security and access-control model, rather than making a more specific claim about the underlying image-storage implementation.
Who can access or reuse a personal stamp
The uploaded stamp is associated with the user’s Docusign profile. Docusign support guidance states that an administrator cannot view or manage a stamp uploaded by an end user as that user’s personal stamp. The user can use saved stamps when receiving envelopes that contain a Stamp field, including future envelopes, subject to the account and workflow configuration.
This is different from Managed Stamps. A Managed Stamp is created at the account level and can be assigned by an administrator to selected users or groups. That model is intended for controlled sharing of an organizational stamp or signing authority and should be used only when the customer intentionally wants that level of administrative access and reuse.
Can the envelope sender obtain or reuse the customer’s uploaded stamp?
For a customer’s personal stamp, the sender does not receive access to the customer’s Docusign profile stamp or gain the ability to reuse it as a saved stamp in the sender’s account. The sender can, however, see the visual mark when it is applied to a document and can retain or download the completed document if they are an authorized envelope participant. As with any mark visible in a completed PDF, the image could potentially be copied from that document. A corporate stamp should therefore not be treated as confidential or as a secret authentication factor.
The Certificate of Completion and audit trail record the transaction and signing/stamping activity. They do not turn the uploaded image into a private secret or prevent the visual mark from being visible in the completed document.
Important distinction: Stamp versus electronic seal
Docusign Stamps are intended to represent a signature, approval, or organizational acknowledgment. A Stamp image should not be described as equivalent to an electronic seal. Where the customer requires a cryptographic seal for a legal entity, or evidence of origin and integrity based on a digital certificate, the customer should evaluate Docusign Electronic Seals or another appropriate regulated signing/sealing solution instead.
Recommended customer guidance
We would suggest explaining that customers should:
-
Upload only a stamp image they are authorized to use and comfortable displaying on the completed document.
-
Use their own Docusign user account and protect it with appropriate authentication controls.
-
Treat the image as reusable visual content, not as a password, private key, or other secret.
-
Confirm internally who is authorized to apply the corporate stamp.
-
Use Managed Stamps only when the organization deliberately wants administrator-controlled assignment to users or groups.
-
Obtain legal or compliance approval where the corporate mark has a formal seal, notarization, regulatory, or jurisdiction-specific meaning.
Official references
Thank you, and have a great day ahead!
Best Regards,
Luke | Docusign Community Moderator
If you find this helpful, please select “Best Answer ” so other users can see it too!