Skip to main content
Can I set a retention policy on Vexa recordings and transcripts? Today: No. Erasing a completed meeting takes its captured-signal tapes with it, but there is no retention policy surface and no audit line over it. Sponsorable: yes — The policy surface, the API and the audit line.
Decide how long recordings and transcripts live, and prove what was deleted.

​
What it does

  • Retention rules over recordings and transcripts.
  • Deletion exposed as an API, not a manual operation.
  • An audit line recording what was deleted and when.

​
What exists today

Erasing a completed meeting takes its captured-signal tapes with it, but there is no retention policy surface and no audit line over it.

​
What this adds

The policy surface, the API and the audit line.

​
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

No. Erasing a completed meeting takes its captured-signal tapes with it, but there is no retention policy surface and no audit line over it.
The policy surface, the API and the audit line.
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.