Share & Sign
Sent Versions — Prove Exactly What You Shared
Every deck you send and every document you sign is sealed with a tamper-proof fingerprint — so a recipient can verify they're seeing exactly what was shared, unchanged, and your unsent edits stay private.
A recipient of a signed document sees the exact version you sent — your later edits stay private drafts until you publish a new version, so a contract can never quietly change after it's signed.
Every send, share, and live presentation is sealed with a SHA-256 fingerprint — the same one an e-signature freezes against, so a signed version and its signature are one unbroken chain.
On a shared deck link, a trust badge shows the recipient the exact version they're seeing — “Version 3” with its fingerprint — while your unpublished edits stay private drafts until you publish. No more “which version did they actually see?”
What you send is sealed
Prove to a recipient they're seeing exactly what you shared — unchanged.
A PDF in an inbox proves nothing — nobody can show which version was actually sent. A cloud link is worse: it can quietly change underneath. In Decks, every deck you send and every document you sign is sealed the moment it goes out with a tamper-proof SHA-256 fingerprint. The recipient sees the exact version sent — and your later edits stay private drafts until you send a new one.
It's the same fingerprint an e-signature freezes against, so a signed version and its signature are one unbroken chain. Every send, share, live presentation, and signature leaves an immutable record — and drafts are never visible to anyone.
One document, three truths
The owner raised the fee after sending. The recipient never sees it.
Master Services Agreement
Fees: $18,000 payable Net-15.
The owner raised the fee and shortened the terms — but hasn't re-sent. Only the owner sees this.
Master Services Agreement
Fees: $12,000 payable Net-30.
Exactly the body that was sent. The owner's later edit is invisible here.
The owner's draft hashes to be388ecd4a16… — a different fingerprint, provably not what was sent.
The owner raised the fee after sending — but the recipient still sees the sealed first version. The draft never leaks, and the fingerprint proves it.
Sealed on every channel
The link always shows what you've published. Every send leaves a seal.
The share link is permanent — but the recipient always sees the version you've published, not your live drafts. Every crossing still cuts an immutable version into a record that can't be erased: email, copy-link, WhatsApp, live present, and signature.
On a shared deck link
A recipient trust badge — “Sent as Version N”, honestly.
The recipient always sees a calm badge naming the published version and its fingerprint. Privately, you're flagged when you have unpublished draft edits — the recipient never sees drift.
One hash, two proofs
A signed version and its signature — the same fingerprint.
One rule makes the fingerprint: the signer signs the sealed version they saw, so the signature's hash equals the version's, exactly. The signature stays permanently valid for the sealed version it signed; a later edit simply creates a new draft the signature doesn't cover — presenting an edited document as the signed one is immediately detectable by the hash mismatch.
A record that can't be erased
Every version sent — the recipient can browse every sealed version.
When more than one version was sent, the badge opens to the full history — each with its number, trigger, date, and fingerprint. Drafts are never listed; only sealed sends.
Per-version insights
Which version your audience actually saw.
View analytics break down by the sealed version each viewer saw — so you know whether your update landed, or the audience is still on an older one.
Step by step
From send to a version you can verify — in four moves.
You send, share, or present
Email a deck, copy the link, share to WhatsApp, go live to present, or send a document for signature.
The version is sealed at that instant
Decks captures the body verbatim and fingerprints it with SHA-256 — atomically with the send, so a send can never exist without its sealed version.
The recipient sees what was sent
Both documents and decks show the recipient the sealed version you published, never your private draft — with a badge naming the version and its fingerprint.
Anyone can verify
The recipient eyeballs the fingerprint against your copy, browses every sent version, and you see which version the audience saw. Delete the deck and its sealed versions go with it.
Where teams use it
When “which version did we see?” stops being a question.
“That's not what we agreed”
Open the exact version the client saw, fingerprint and all — no more word against word.
Re-price without worry
Your edits stay private drafts, and every version the buyer saw stays sealed on the record.
Protected from both sides
Every proposal and deliverable you send is sealed — and under White-Label, the record ships under your brand.
Why it matters
An attachment proves nothing. A sealed version proves everything.
A file in an inbox can't show which version was sent, and a cloud link changes underneath you. A sealed version ends both: an immutable record of exactly what you shared, with a fingerprint anyone can verify — the same fingerprint your signature stands on.