The capture event
In controlled testing
Channel, jurisdiction, language, the exact wording that was shown or spoken, the timestamp and a hash of the subject.
Part of the Audact layer
In the platform, not a separate product · In controlled testing
What was consented to, for how long, under which entity and through which channel — captured at the moment it happened, linked to the interaction it governed, and exportable without building an extract pipeline first.
What it stores
In controlled testing
Channel, jurisdiction, language, the exact wording that was shown or spoken, the timestamp and a hash of the subject.
In controlled testing
What was consented to, for how long, under which legal entity, and for which processing purposes.
In controlled testing
Every revocation is appended and linked to the original capture, so a later change or reordering is detectable by recomputation. Replay-safe.
In controlled testing
The same subject moves country; the vault is designed to re-evaluate eligibility under the regime that now applies rather than the one that applied at capture. Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.
Why it is a store and not a log
Consent provenance is the record a compliance team needs first and can rebuild least easily. A log tells you that something was written; a store tells you what was consented to, by whom, under which wording, and what has happened to it since.
The vault exports structured records that downstream systems can read directly. That is the difference between an export and a project.
Where it sits
The Consent Vault is a component of the Evidence Vault. Consent records are linked to the per-interaction receipt, so the chain runs from the consent, through the disclosure, to what the interaction actually did, in one export rather than three.
Next step
The Consent Vault is part of the Evidence Vault rather than a product you buy on its own. Status: In controlled testing. Start with white-glove onboarding, or ask engineering for the record schema.
Control and Proof are the layer; Voice is the application on it.
The receipt a consent record is linked to. Public verifier: Not available yet.
The DPIA extract that cross-references this vault.
The API this vault is a component of.