"Just get it e-signed" has become the default answer to anything involving a document. But an e-signature and a hash seal answer two different questions, and mixing them up leads to paying for the wrong tool, or trusting the wrong one.
Two questions, not one
- Who agreed to this? That's what a signature answers. It ties a person to a document.
- Is this exactly the document that was issued? That's what a hash seal answers. It ties a document to its exact content at a point in time.
Plenty of documents need only the second: a quote you send, an invoice, a report, meeting minutes, a deliverable. Nobody needs to "sign" them. What matters is that what arrives is exactly what left.
What an e-signature gives you
- Identity of the signer (how strong depends on the type: simple, advanced or qualified, in EU terms).
- Intent: the person agreed to the content.
- Usually an audit trail kept by the signing platform.
The cost: accounts for the signer, a workflow, often a per-envelope or per-seat price. Great for contracts. Overkill for "here is my quote".
What a hash seal gives you
A SHA-256 fingerprint of the file, registered with a date. Change one character and the fingerprint no longer matches.
- Integrity: anyone can check the file hasn't changed since sealing.
- No accounts needed to verify: the recipient opens a link or drops the file.
- Privacy: the fingerprint reveals nothing about the content.
What it does not give you: proof of who wrote the document, or that anyone agreed to it.
A quick way to choose
| You need to prove... | Use |
|---|---|
| Someone agreed to terms | E-signature |
| The document wasn't altered after you sent it | Hash seal |
| Both | Sign it, and seal the signed copy |
Where TRAMPTO fits
TRAMPTO is the hash-seal side. You seal a PDF in your browser (the file is never uploaded) and share a public verification link. The recipient checks it in seconds, for free, with no account.
It's not a signature and doesn't try to be. Where the law requires a qualified e-signature or seal, use one. For the many everyday documents where the real risk is a quiet edit, a seal is the lighter, cheaper tool.
What do you use?
Do you e-sign everything by default, or only contracts? Where has a plain "this is the exact file" check been enough for you?
Top comments (0)