Data integrity
Audit trail and ALCOA++
Every action lands in an immutable journal: append-only at the database level, and the application role can neither rewrite it nor disable that protection.
Immutability that is physical, not contractual
Every journal record is chained to the previous one with a cryptographic hash (a per-tenant hash chain), and the journal table is protected at the database level against updates, deletion and truncation.
Before, after and the reason
The journal keeps the value before and after, the author and the reason; changing an already saved value without a Reason for Change is impossible.
Proving the record is contemporaneous
The moment of entry is stored separately from the event time — this is what proves the record was made contemporaneously. Time is stored in UTC only, ISO 8601; the time zone is a property of presentation.
Next — in the documentation: Audit trailReason for change
We will walk you through the product on a demo study and answer your questions.
Request a demo