What blockchain anchoring gets you in court
Written for legal teams and boards. No cryptography background assumed — print it, forward it, read it aloud in the boardroom. (This explains the mechanism; it is not legal advice about any particular matter.)
What actually happens when a record is “anchored”?
When your team approves an AI system, completes a risk assessment, or makes any governance decision, chainCheck computes a unique digital fingerprint of that record — change even one character of the record and the fingerprint no longer matches. That fingerprint (not the record itself) is written into a public blockchain, a ledger maintained by thousands of independent computers that no company — including us — can rewrite.
So what can we prove later?
Three things, to anyone: that this exact record existed; that it has not been altered since; and precisely when it was created. Not "trust our vendor's database" — mathematically checkable by any third party.
Why does that matter in litigation or an enforcement action?
Ordinary audit trails live in a vendor's database, where opposing counsel can argue records were altered or backdated after the fact — and you are left proving a negative. An anchored record shifts that fight: the timestamp and content-fingerprint sit on a public ledger neither you nor your vendor controls, created contemporaneously with the decision. Your evidence of "we assessed this model on March 4th" no longer depends on anyone taking your word for it.
Does the blockchain hold our confidential data?
No. Only the fingerprint goes on-chain — a string of characters that reveals nothing about the record's contents. The record itself stays in your governed workspace. Privilege and confidentiality are unaffected; the chain proves existence and integrity, not contents.
What does a regulator or court actually do to verify?
They visit a public verification page — no account, no fee — and the fingerprint of the record you produced is recomputed and compared against the one on the ledger. Match: the record is what it claims to be, from when it claims to be. Mismatch: it isn't. That check takes seconds and requires nothing from chainCheck.
What happens if chainCheck disappears?
Your anchors survive. They live on a public network independent of our company, and verification does not require our servers. Records anchored today remain provable decades from now.
The one-sentence version
Every governance decision your team makes produces a public, permanent, independently checkable proof that the decision happened, when it happened, exactly as recorded — without exposing the decision's contents to anyone.