Your audit log is hash-chained and its
checkpoints are signed with a key that is not in our database. Sign in to inspect them,
export them, and verify them yourself.
A hash chain that lives in our
database is only as strong as our database. These checkpoints are signed with an
Ed25519 key that is not in it — so a rewritten log stops matching, and forging one
needs a key a database intruder does not have.
Get the key fingerprint from
somewhere other than this API first. A key that arrives in the same response as
the data is convenient, not independent evidence.
It is published on
kirelta.com/security, which runs on separate infrastructure.
The verifier imports no Kirelta code
— standard library plus cryptography. A result you get by
running our verifier against our data is a result you have to trust us for, so read
it (~200 lines) or reimplement it.