Trust

Verify your audit trail yourself

You don't have to take our word that nobody changed your approval history. Every line of a Glime audit trail carries the hash of the line before it, so altering or removing any line breaks every link after it. Drop in your workspace export (Settings → Your data → Export) and this page recomputes every link — in your browser, on your machine.

Nothing leaves this page. Its security policy forbids it from connecting anywhere at all, and your browser enforces that — disconnect from the internet and it works the same. Prefer a terminal? node scripts/verify-audit.mjs export.json in the open repository does the same arithmetic.

Your export file (.json) Optional: an anchor you were sent earlier (seq:hash, from a monthly governance email)

What this proves, and what it doesn't

• It proves the file's audit rows form an unbroken chain: none altered, none removed from the middle, none reordered — and, with an anchor, that the history up to that anchor is still the history you were sent.
• It doesn't prove the log is complete going forward from its last row, or that the vendor couldn't have rebuilt the whole chain before you ever saw it. That's why the chain's head goes out to you every month: keep it, and a later rewrite has to disagree with it. Tamper-evident, not tamper-proof.