How we issue, sign, and verify credentials
This page is maintained by Legal Risk Alert to explain — in plain language — what our certifications are, how a verifier can confirm them, and what our learners and partner organizations can expect.
Every certificate is verifiable
Each certificate carries a unique code and a public verification URL of the form /verify/{code}. Anyone with the link can confirm the holder's first name, the program completed, the issue date, and current status — no sign-in required.
Machine-readable & signed
We expose each credential as a signed JSON-LD document at /api/credentials/{code}. Payloads follow the W3C Verifiable Credentials data model and carry an HMAC-SHA256 signature so a verifier can detect tampering.
Three credential tiers
Leadership Law Associate (country edition), Leadership Law Associate (international edition), and Co-Branded Partner certifications — each clearly labelled on the certificate face, in the JSON payload, and on the verification page.
Revocation is public
If a certificate is revoked — for example, for academic integrity issues — the verification page immediately shows it as Revoked and includes the date. The signed credential JSON also reflects the revoked status.
What we do not claim
This is an independent training program; it is not a regulator-issued legal credential and does not constitute a license to practice law in any jurisdiction. Learner identity is self-attested; we do not perform government-ID verification.
Report a problem
Suspect a forged certificate or a verification page that doesn't match the PDF? Email credentials@legalriskalerts.com with the code; our team responds within two business days.
Embed a verification badge
Partner sites can embed a live verification badge for any credential with a single iframe:
<iframe
src="https://law-savvy-leaders.lovable.app/api/verify/{code}/embed"
width="380" height="80" frameborder="0" loading="lazy"
title="Legal Risk Alert credential verification"></iframe>Provenance ledger
Append-only public log of certificate issuance and content version events. Each entry carries a payload hash linked to the previous entry.
Ledger is initializing — entries appear as credentials are issued.
Issuer profile (JSON-LD): /api/issuer