Adding the badge to your site

A link, not a picture — so a copied badge can't lie on somebody else's site.

Free, like everything a holder gets. Once you have a certificate, its page gives you an inline SVG snippet to paste anywhere on your own site.

Why it's a link and not an image

Anyone can right-click a saved seal and paste it on their own site — so the badge asserts nothing about your certificate at all. It's a link, and the page it points to is where the truth lives: a copied badge sends a visitor to your certificate page, showing your registered name, not theirs. There's nothing to fake, because there's nothing the image itself claims.

Nobody is tracked until somebody clicks

The snippet is self-hosted inline SVG, not an image served from our domain — so there's no request to us, and nothing about your visitors reaches us, until somebody actually clicks. An <img> pulled from our servers on every page load would quietly tell us your visitor's IP and referrer on every visit, which would be a strange thing for a company that has just promised not to process biometric data.

A stale badge can't happen

The badge doesn't carry a cached "verified" state that could outlive a revocation — a click resolves your certificate's status live, exactly like the free check does, every time.

The domain check

Your certificate knows which domains you control. So a visitor who clicks your badge can see whether it's actually placed on a site you operate — a badge copied onto somebody else's site fails that check, in public, the moment it's clicked.