Tamper-evident audit log
Cryptographic provenance, not blockchain.
The audit log is an append-only Merkle log — the same construction used by Google Certificate Transparency (RFC 6962), AWS QLDB, and Guardtime KSI (the technology behind Estonian e-government, NHS Scotland, NATO CCDCOE, and US DoD audit infrastructure).
It is not a blockchain. There is no consensus protocol, no token, no peer-to-peer network, no on-chain data. It is industrial cryptography for integrity proofs, deployed inside your network, signed by your hardware key, written to your storage. If your regulator wishes to verify the integrity of an extraction performed three years ago, they can — without trusting us, and without leaving your building.
What we record
- — Cryptographic hash of every document ingested
- — Hash of every model output produced
- — Operator identity (signed) for every action
- — Model version, parameters, and timestamp
- — Append-only Merkle inclusion proof
What we do not record
- — Personal Data content (only hashes)
- — Document content (only hashes)
- — Anything that conflicts with right-to-erasure under DPA Sixth Principle
- — Anything outside your environment
The audit log's design specifically resolves the tension between immutability and the right to erasure. By recording only hashes and metadata, erasure of the underlying source records invalidates reverse-traceability while preserving the integrity proof — satisfying both the audit and the privacy principle.