One mark. Everywhere. Always verifiable.
Every Let's Seal document carries the same mark, stamped into the PDF, on its proof page, and in the embeddable widget. Consistency is what makes it recognisable; the rule that it always links to a live verdict is what keeps it honest.
The verified seal
A blue verified-badge with a check, “sealed & verified” in one glyph. Deliberately blue, because Adobe’s paid AATL seal owns the green tick and we’re the free, open alternative.
#2563ebA live verify badge, in one line
The widget renders in a shadow DOM (no clash with your styles) and calls the public, keyless verify API. It always shows a live verdict, never a static image.
Shows “authentic & unaltered”, issuer, and a link to the full proof.
<!-- Verify badge for one document --> <div data-letsseal-verify data-hash="<sha256>"></div> <script src="https://app.letsseal.org/embed.js" async></script>
Lets a visitor verify any file, right on your page.
<!-- Drop-a-PDF checker --> <div data-letsseal-verify></div> <script src="https://app.letsseal.org/embed.js" async></script>
Keep it recognisable, keep it honest
- Always make the badge open the live verdict. Clicking or scanning lands on the real proof.
- Keep the mark in Trust Blue (#2563eb); use it at a legible size with clear space around it.
- Pair it with the document's fingerprint or a /d/<hash> link, so anyone can check the file itself.
- Say what's true: “Sealed & unaltered”, “Issued by <name>”, “Verify at letsseal.org”.
- Don't present the badge as proof on its own. A copied image is not a seal. Verify the file.
- Don't recolour, redraw, or add effects to the mark, or pair it with a different tick.
- Don't imply notarisation or that identity was verified. A seal proves integrity + time, not who.
- Don't use it as static decoration with no link to a live, checkable proof.
The badge is a front door, not the proof. That’s the whole design: it invites a check, and the check is what carries the weight. See the root of trust