LetsSeal

Seal and verify insurance documents

Policy documents, certificates of insurance, and claims paperwork that carry their own proof, so a broker, a bank, or a contractor can confirm a certificate is genuine in seconds, and forged cover has nowhere to hide.

For insurers, brokers, mgas, loss adjusters, and surveyors.

Open the app Developer docs
What a seal proves

Four guarantees, in insurance

A COI that can't be faked

A changed limit, name, or effective date fails verification. The forged certificate-of-insurance problem, closed.

The issuing insurer, named

Every policy and certificate names the insurer or broker that sealed it, chaining to a published root.

The moment of issue, fixed

Issue and cover dates are timestamped on the blockchain, decisive for cover periods, claims timelines, and disputes.

Verified without a phone call

A bank, a landlord, or a main contractor confirms a certificate at a permalink, instantly, and free.

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
Blockchain 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 blockchain, 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 business

    Open app.letsseal.org and sign in. Your organisation gets its own certificate authority the first time you seal.

  2. 2

    Upload the policy or certificate

    Drop in the PDF. It's sealed with your certificate (PAdES) over the whole file, so any later edit is caught.

  3. 3

    Anchored and logged automatically

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

  4. 4

    Send the proof link with the certificate

    Every document has a permanent proof page. The requesting party opens it to confirm the certificate is 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 single certificate of insurance
$ sealbot seal certificate-of-insurance.pdf --org examples
sealed   certificate-of-insurance.pdf
  proof  https://letsseal.org/d/7b1a9c…e204
  anchored to the blockchain · recorded in the transparency log

# Issue at volume: seal every policy PDF as it lands in a folder
$ sealbot watch /srv/policies --mode seal --org examples
watching /srv/policies … sealing new & changed PDFs (idempotent)

# A third party confirms a certificate, public, no account
$ sealbot verify certificate-of-insurance.pdf
✓ authentic · unaltered · sealed by Let's Seal Examples

Point a watched folder or your document pipeline at Let's Seal and every policy leaves already sealed, timestamped, and carrying a proof link, one command, no per-document 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 certificate of insurance
Issuer
Let’s Seal Examplesletsseal.org
SHA-256
64-hex fingerprint ✓

Anchored on the blockchain

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 certificate of insurance

    Live proof

    This is what a bank or contractor sees when they check a COI: genuine, unaltered, issued by the named insurer, and timestamped, no call to your team required.

  • A policy document or schedule

    Seal the policy wording and schedule so the insured, and any lender relying on it, can confirm the cover terms are exactly as issued, with nothing altered.

  • A loss-adjuster or surveyor report

    A claims report sealed the moment it's finalised: provably the version that was filed, timestamped, and attributable to the adjuster who produced it.

  • A binder or cover note

    Interim cover confirmations sealed on issue, so a broker or client can verify the binder is genuine and current before the full policy follows.

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

Common documents

What you’ll seal

  • Policy documents
  • Certificates of insurance
  • Claims paperwork
  • Loss-adjuster reports
  • Surveyor reports
  • Binders
Questions

Straight answers

Can I seal thousands of policies automatically?
Yes. Point the CLI or a watched folder at your document pipeline and every PDF leaves already sealed, timestamped, and carrying a proof link. One command per document, no per-seal fee.
How does a third party check a certificate of insurance?
They open the proof link, or drop the PDF into the public verifier. It confirms the certificate is genuine, unaltered, and issued by you, with no call to your team.
Does the recipient need special software?
No. They get a normal PDF that opens anywhere, and it also verifies against the public portal and any standard PAdES validator.
Does this prove the cover is valid?
It proves the certificate is authentic, unaltered, and was issued by you at a fixed time. Whether cover is currently in force is a matter for the policy itself, but nobody can hand over a doctored certificate and pass verification.

Start sealing insurance 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