Let’s Seal

Seal and verify official documents & certificates

Permits, licences, planning decisions, and official letters that anyone can verify — so a citizen, a business, or another authority can confirm a document is genuine, and forged permits and doctored official letters fail on sight. Issue one or a whole run, each carrying its own proof.

For councils, agencies, regulators, courts, and registrars.

Open the app Developer docs
What a seal proves

Four guarantees, in government & public sector

Official documents that can't be forged

A changed name, reference, or decision fails verification. The forged-permit and doctored-letter problem, closed at issue.

The issuing authority, named

Every permit and letter names the body that sealed it, chaining to a published root — a specific certificate, not a crest anyone can copy.

Fixed at the moment of issue

The issue date is timestamped on Bitcoin — decisive for deadlines, appeal windows, and which decision was in force when.

Verified by anyone, free

A citizen, a business, or another authority confirms a document at a permalink — instantly, and free, with no office to phone.

How it works

From your file to a proof anyone can check

The same pipeline every time — the seal and the timestamp travel with the file, so the proof is self-contained.

Your file
Your signed PDF
Seal
Signed over every byte · PAdES
Anchor
Bitcoin timestamp + public transparency log
Proof page
A permanent /d/… link travels with the file
Anyone verifies
Free, public, offline-capable — for anyone
The proof travels inside the file. Verification stands on the published root, the transparency log, and the Bitcoin ledger — so a court, a bank, or a counterparty can check it independently, forever.
Step by step · the web app

Seal it in the app — no setup

  1. 1

    Sign in as your authority

    Open app.letsseal.org and sign in. Your organisation gets its own certificate authority for sealing official documents.

  2. 2

    Issue or upload the document

    Enter the details or drop in the PDF. It's sealed with your certificate over the whole file, so any later edit is caught.

  3. 3

    Anchored and logged automatically

    The fingerprint is timestamped on Bitcoin and written to the public transparency log. The recipient gets a normal PDF that also verifies.

  4. 4

    Deliver with a proof link

    Every document has a permanent proof page. The recipient — or anyone relying on it — opens the link to confirm it's genuine and current.

Step by step · the CLI

Automate it from your terminal or CI

The sealbot CLI does the same thing, scriptably — one command per file, straight into your pipeline.

# Seal a run of letters or permits as they're issued
$ sealbot watch /srv/notices --mode seal --org examples
watching /srv/notices … sealing new & changed PDFs (idempotent)

# Seal a single permit under your authority
$ sealbot seal planning-permission.pdf --org examples
sealed   planning-permission.pdf
  proof  https://letsseal.org/d/7e42bc…a015

# Anyone confirms an official document — public, no account
$ sealbot verify planning-permission.pdf
✓ authentic · unaltered · sealed by Let's Seal Examples

Point a watched folder or your case system at Let's Seal and every notice, permit, and letter leaves already sealed, timestamped, and carrying a proof link — one command per document, no per-seal fee.

Full CLI & API reference
See it in action

What a proof looks like, and what you can seal

Issuer verified — controls letsseal.org
Authentic & unaltered
Document
A sealed permit or licence
Issuer
Let’s Seal Examplesletsseal.org
SHA-256
64-hex fingerprint ✓

Anchored on Bitcoin

Recorded in the public transparency log

Public and free to verify — by anyone, with standard tools.
Open the live proof

A single use case, many documents. Each of these is sealed the same way:

  • A sealed permit or licence

    Live proof

    Open the proof page the way a business or inspector would: it shows the permit is authentic, unaltered, issued by the named authority, and timestamped on Bitcoin — a forged permit can't pass.

  • A planning permission or decision notice

    Seal the decision so an applicant, objector, or conveyancer can confirm the permission is genuine and exactly as granted, appeal window and all.

  • A benefit, tax, or official letter

    Seal outbound letters in bulk, so a recipient or a third party relying on the letter can verify it's genuinely from the authority.

  • A court order or statutory notice

    Orders and notices sealed and timestamped on issue, so their authenticity and date can be proven by anyone acting on them.

Live proofs are real documents sealed under the “Let’s Seal Examples” organisation.

Common documents

What you’ll seal

  • Permits & licences
  • Planning permissions
  • Benefit & tax letters
  • Court orders
  • Official certificates
  • Statutory notices
Questions

Straight answers

Does this stop forged official documents?
A sealed document can't be edited without failing verification, and anyone can check it against the proof link. A forged permit or doctored letter simply won't verify as issued by the authority.
How does a citizen or business verify a document?
They open the proof link, or drop the PDF into the public verifier. It confirms the document is genuine, unaltered, and issued by the named authority — free, with no office to phone.
Can we issue at the scale of a whole department?
Yes. Point the CLI or a watched folder at your case system and every letter and permit leaves sealed, timestamped, and carrying a proof link — one command per document, no per-seal fee.
Will documents stay verifiable long term?
Yes. The seal and the Bitcoin anchor outlive any single vendor, so an official document sealed today stays independently verifiable for years, with standard tools.

Start sealing government & public sector documents

Free and open. Seal in the app, automate from the CLI, and hand anyone a proof they can verify themselves.

Open the app All use cases