Strip names, account numbers and identifiers before the transcript is stored.
What it does
- Detects named entities and identifiers in the transcript.
- Removes them before storage, not after the fact.
- Runs inside your own infrastructure.
What exists today
Transcripts are stored as captured.What this adds
A redaction pass ahead of storage, so the stored artifact never carries the identifiers.How sponsorship works
You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so “done” means done on your meetings. Your name goes on the release note. Sponsorship buys the order of the queue — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.Two doors
Sponsor this
Fifteen minutes. Bring the constraint you are under.
Watch this
One email when it ships. The mail is already written — send it as it is.
Questions
Can Vexa strip names and account numbers out of a transcript before storing it?
Can Vexa strip names and account numbers out of a transcript before storing it?
No. Transcripts are stored as captured.
What would sponsoring this add?
What would sponsoring this add?
A redaction pass ahead of storage, so the stored artifact never carries the identifiers.
Where does it run?
Where does it run?
On your own infrastructure. Vexa is Apache-2.0 and self-hosted — the audio and the transcript stay inside it.
Ships upstream Apache-2.0 when sponsored.