Audit Chain: Verifiable Cryptographic Integrity
Other catalogues store logs. Linedat stores proof — verify it with a button.
Framework / standard: ISO/IEC 38505-1 (Principle 6) · GDPR Art. 5(2) · EU AI Act Art. 12
If your audit log can be edited, it is not proof: it is a suggestion. Most catalogues store logs in mutable rows that anyone with database access can rewrite.
Linedat cryptographically chains every record — data audit, AI usage and lineage — with hashes computed by a database trigger, never by the application.
Computed by the database, not the app
The prev_hash and row_hash fields (SHA-256) are computed by a database trigger over a canonical payload. The application never writes them, so a manual UPDATE on a row breaks the chain in a detectable way. This covers audit logs, AI usage logs and lineage events, per tenant.
Self-service verification, with a permanent record
There is a verification endpoint that traverses the chain and returns a verdict ("chain intact" or "chain broken" pointing to the affected row). Each verification leaves a persistent record of who ran it, when and how long it took — operational evidence ready for a SOC 2 auditor. A broken chain is not something to repair: it is evidence of tampering.
The limits (what we do not claim)
The genesis block is reproducible (it is not signed by an external third party) and verification is linear over rows — sub-second today, not designed for billions of rows without a Merkle index. The trigger protects against manual UPDATEs, not against a database administrator with superuser privileges who alters the trigger itself.
How Linedat helps
We do not ask you to trust our audit log: we ask you to verify it — that is what the button is for. It is the differentiator that no classic catalogue has.
Related capabilities
A serious incident starts the Art. 73 clock. We start it running and block closure until notification is on record.
Temporal and Verifiable Lineage (Point-in-Time)We know what the lineage looked like on the fiscal year-end — and we can prove nobody touched it.
PII Sanitisation Before Reaching the ModelBefore a national ID or an IBAN leaves for OpenAI, it is redacted — in the critical path, not as an option.