Most compliance software ends the same way: an action happens, a line lands in a log, and you're asked to trust that the log is real, unaltered, and still there. Hub's compliance modules now end differently. When you record a consent, capture a payment proof, send a client notice, or collect a sign-off, the action mints a receipt — and anyone you give that receipt to can confirm it independently at verify.dekimu.com, without an account and without taking our word for anything.
Each receipt records what happened, when, and against which version of the document or policy — sealed so that any later tampering is detectable. Hand the receipt ID to a client, an auditor, or a regulator, and they open a public verification page that confirms the record existed at the claimed moment with the claimed contents. There's nothing to trust about Dekimu in that exchange. The verification is the math, and the math is open to everyone.
Every workspace now has a public trust page — a single shareable link that shows your compliance posture at a glance: which kinds of receipt you're producing, how complete your coverage is, and a way to verify each one. A freelancer pitching a nervous enterprise client can send that link instead of a paragraph of reassurance. The page is read-only, public by choice, and shows exactly what you've actually done — not a badge you bought.
"We keep records" is a sentence. A receipt a stranger can verify is evidence. The gap between those two is most of what compliance theatre has been hiding.
Publicly verifiable receipts are more work than a private audit log, and almost nobody at our tier ships them — which is exactly why we did. The whole point of a compliance floor is that it holds when someone leans on it: a dispute, a data-subject request, an audit. A record only you can see, on infrastructure only you control, is the record that fails the day you need it. So the receipts live on a separate public surface, and the proof belongs to you, not to us.