Trust · Data practices
Know what is recorded, derived and kept separate.
Assure separates immutable event evidence from derived inventory, maps, controls and workpapers. A correction creates review history; it does not silently rewrite the original evidence.
01 / Trust · Data practices
Recorded evidence
Typed event envelopes can include source, actor, action, timestamps, provenance and cryptographic commitments. Payload bytes are not required for hash-only sources.
02 / Trust · Data practices
Derived review state
Inventory, relationships, process maps, gaps and advisory results are versioned interpretations. Unknown context remains unknown until evidence or a reviewer establishes it.
03 / Trust · Data practices
Retention and deletion are not one number yet.
Default and configurable periods, backups, legal holds, payload deletion and the treatment of append-only evidence remain unresolved legal and operational configuration. No fixed public retention promise is made here.
04 / Trust · Data practices
Deployment modes stay statused.
The current public deployment is hosted. Private deployment, customer-managed keys, confidential computing and regional-residency options are not represented as generally available until implemented and verified.
05 / Trust · Data practices
Evidence can be checked without proving every meaning.
Version history, event chains, signed checkpoints and offline verification help detect later alteration. They do not prove that a source event was accurate or that a model interpretation is correct.