Trust and transparency
Understand what you’re signing.
How access, signing records, and document verification work in OpenSeal.
Keep private links private
A signing link lets its holder act as the invited signer. A tracking link grants access to the associated document. Anyone you share these links with may be able to use that access. Signers do not need an account, so confirm the request and sender before signing.
A record of what happened
OpenSeal records events such as sending, opening, consent, and signing. The completion certificate includes recorded timestamps and signing details. These records support review; email access alone does not independently verify a person’s identity.
Check the completed PDF
The completed PDF receives a digital seal. Verification can check that seal and whether the file has changed since sealing. It does not establish that the contents are correct, prove the signer’s identity, or replace notarization. Keep the original downloaded PDF for verification.
Storage and deletion
Document downloads require authorized account access or the document’s private link. Free completed files are stored for 7 days; Pro storage is 365 days. Download before the date shown for your document. Self-hosted operators control their own infrastructure and configuration.
Your choices
Review the PDF and electronic signing disclosure before consenting. You can decline a request or contact its sender about corrections, paper copies, and other ways to sign. Optional browser drafts contain sensitive information and should not be saved on shared devices.
Get help or report a suspicious request
If you don’t recognize a signing request, don’t sign. Verify it with the sender using contact details you already trust. Keep private signing links, tracking links, verification codes, and document contents out of public reports.