Privacy-first e-signature
E-sign with no upload
“E-sign” should not be a synonym for “upload the PDF to a vendor.” FreeSign is built so the signature provider never receives the document — only a hash and the cryptographic ceremony. That is the privacy differentiator: no upload, no account, still a real Advanced Electronic Signature-style artefact.
What “no upload” actually means
Your browser computes SHA-256 of the PDF with WebCrypto. That hash — not the file — is what the Worker sees when it binds consent, issues a per-user certificate, fetches timestamps, and returns a CMS seal. The seal is merged locally as an incremental PDF update. If FreeSign’s servers were seized tomorrow, they would not contain your contracts.
Visual stamp vs verifiable signature
Some free PDF signers place a drawn, typed or uploaded signature on the page as an image. What that produces is a picture on a page. One such tool says so on its own page: “Scissor PDF adds a visual signature, the same as signing a printout and scanning it. It does not add a certificate-based digital signature.” (pdf.scissor.studio/sign-pdf, checked 29 October 2026.) Adobe’s help makes the same distinction: an e-signature “may also appear in graphical formats, such as an image of a handwritten signature”, while a digital signature “is generated using a digital certificate” (Adobe Acrobat, Types of signatures, checked 29 October 2026).
| What you can check | Visual stamp (image placed on the page) | Verifiable signature (what FreeSign produces) |
|---|---|---|
| What is added to the PDF | An image or drawing on the page. Nothing cryptographic by itself. | A PAdES signature: a CMS (PKCS#7) signature over the document hash with the signer’s certificate. An RFC 3161 timestamp is included when a timestamp authority is configured. |
| Can a later change be detected? | Not from the stamp itself. The image says nothing about the bytes around it. | Yes. A verifier recomputes the hash of the signed revision and flags any change made to it after signing. |
| Who signed | Whatever the image shows. The file carries no verified link to a person. | A per-user certificate tied to a verified email. The signer authenticates with an email one-time code or a registered passkey. |
| When | A typed or printed date is just text on the page. | An RFC 3161 timestamp when configured. An OpenTimestamps proof may be pending or deferred; check the receipt for its status. |
| Checking it without the vendor | Nothing to verify; you just look at it. | Adobe Reader, openssl and pyHanko, or the FreeSign verifier. Adobe may show a yellow warning because the signing CA is not on Adobe’s trust list; what that means. |
FreeSign is not a Qualified Electronic Signature (QES). The left column describes the technique in general, not any one product.
What the law says
- US. The ESIGN Act defines an electronic signature as “an electronic sound, symbol, or process, attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record” (15 U.S.C. §7006(5), checked 29 October 2026). For transactions in or affecting interstate or foreign commerce, a signature may not be denied legal effect solely because it is electronic (§7001(a)), subject to §7003 exceptions including wills and family-law records. An image may express intent to sign, but its legal effect depends on the transaction and applicable law.
- EU. eIDAS Article 25(1) says an electronic signature may not be denied legal effect and admissibility as evidence solely because it is electronic or is not a qualified signature. For an advanced electronic signature, Article 26 additionally requires that it is uniquely linked to the signatory, capable of identifying the signatory, created using signature-creation data that the signatory can use under their sole control with a high level of confidence, and linked to the data so that “any subsequent change in the data is detectable” (EUR-Lex, consolidated eIDAS Regulation (EU) 910/2014, Art. 25–26, checked 29 October 2026). A bare image cannot show that last property by itself; a cryptographic signature can. FreeSign supplies verifiable PDF evidence relevant to these requirements (see the FAQ); whether a particular signing process meets Article 26 requires its own assessment. FreeSign is not a QES.
In practice: a visual stamp is often accepted for everyday paperwork, and your counterparty, contract or regulator decides what is enough. If you need to show later that the file was not changed, who signed and when, choose a signature you can verify. This is general information, not legal advice.
No account is part of the same design
Accounts create document libraries. Document libraries contradict “we never held the PDF.” FreeSign authenticates each ceremony with an email OTP or a registered passkey and binds the verified email into the certificate, then forgets the workflow the way a hash-only protocol should. There is no folder of past NDAs waiting on our side.
Proof that still stands up offline
- Verify in FreeSign’s verifier or with public tools (
openssl cms, pyHanko, Adobe Reader). - When present, RFC 3161 timestamps and OpenTimestamps proofs add independently verifiable time evidence. A deferred OpenTimestamps proof can be retrieved later.
- Evidence JSON travels inside the signed PDF’s CMS.
Related reading: Sign a PDF without uploading, Verify with openssl, post-quantum co-signature.
Who this is for
Legal and security teams who need an e-sign path for sensitive PDFs; founders signing NDAs before a data room exists; anyone who has ever hesitated to drop a contract into a SaaS because the contents were the whole point of the confidentiality clause.
FAQ
Is there really no PDF upload?
Correct. Only a hash and ceremony metadata are sent. The document bytes stay in the browser.
How is this different from “encrypted upload” products?
Encrypted upload still means the vendor stores a copy (even if locked). FreeSign never receives the copy at all.
Do I need an account for no-upload signing?
No. An email one-time code or a registered passkey authenticates the signer without an account or document vault.
What is the difference between a visual signature and a verifiable signature?
A visual signature is an image of a signature placed on the page. By itself it has no cryptographic link to the document, so a later edit cannot be detected from the file. A verifiable signature is a cryptographic signature (PAdES) over the document hash with a certificate; a configured timestamp authority adds a timestamp. A verifier can detect changes to the signed revision without the vendor. A visual signature can still count as an electronic signature in many contexts; check what your counterparty or the law requires.
Can others verify without FreeSign?
Yes. The signed PDF carries a verifiable CMS signature and embedded evidence; a configured timestamp authority adds PAdES-B-T time evidence. Public verifiers work without calling our API.