Consent first
Participants are informed and consent is recorded before capture. A visible indicator shows when recording is active.
Trust and privacy
Meeting recordings are among the most sensitive records a business holds. Here is what the product is designed to do with them, and what we will not claim.
Controls
Meeting recordings are among the most sensitive records a business holds. These are the controls the product is being built around.
Participants are informed and consent is recorded before capture. A visible indicator shows when recording is active.
The AI proposes; a person verifies. No message or downstream action happens from an unreviewed output.
Audio preparation and analysis run on a compatible device or server where the hardware can carry it.
Where local processing cannot handle a task, cloud use is disclosed and chosen by the workspace — never switched on quietly.
Processing happens on copies, so any transcript can be checked against what was actually said.
Processing steps, corrections and approvals are recorded, with the model and version noted.
Access is scoped per workspace and per role, rather than anyone with a link.
Retention is a workspace setting. Deletion removes the recording, the transcript and the derived outputs together.
We are building toward these controls and will publish validated details as they are completed. Encryption in transit and at rest, workspace isolation and audit logs are implementation requirements — not verified guarantees on this page.
What we do not claim
A trusted product says what it cannot do. This list is enforced in the copy across the site.
Recording a business meeting creates personal data. In India, the Digital Personal Data Protection Act and its rules apply, alongside contractual and sector obligations your organisation already has.
We are testing the full workflow with a small number of teams on real, consented English and Hindi meetings. Tell us how you meet and we will get back to you.