A record of every transmission
Not a chat log. A radio log — who spoke, when, for how long, and what they said.
Built as a log, because that is what it is
Chat bubbles are the wrong shape for voice. Full-width rows with a hairline between them let you scan a shift, and the transport bar plays straight through what you missed.
- Sender, direction, timestamp and duration to a tenth of a second on every row
- A transcription line under each transmission
- Play through sequentially, or replay any single message
Retention is your decision, and it is visible
Off by default. When an organisation turns it on, it picks a window and a scope, and members are told in the channels it applies to.
- Configurable window, applied by a purge that runs on a schedule and audits what it removed
- Scope is channels, or channels and direct messages — the difference is stated, not implied
- Deleted media is genuinely reclaimed from disk, not just unlinked from the row
Delete means delete — or it says otherwise
Deleting a message destroys its content and leaves a tombstone carrying who deleted it and when, which is what an audit trail needs. Under a retention policy that keeps deleted content for the Vault, members are told that in the app.
- The recording itself is destroyed. What survives is the note that it was deleted, by whom, and when
- With retention off — the consumer case — deletion is true erasure
- Keeping deleted content for compliance is off by default and consent-gated
The archive your organisation can read
Message Vault decrypts in your admin's browser using an org key we never hold. It is your archive in a meaningful sense, not just an archive we let you look at.
- Your organisation gets its own key, made in your admin’s browser and never sent to us
- Every access to the Vault is written to the audit log
- Transcripts are archived with the audio, which is what makes the archive searchable
