On-device transcription for board, M&A, and strategy meetings
For meetings where the answer to "should we let a third party hear this?" is "no". Keep the recording, transcript, and search on the device. No vendor meeting bot. No upload to a cloud provider. Just the browser, your microphone, and a local transcript you control.
When to keep transcription on-device
Use on-device for boardroom conversations, M&A discussions, exec strategy sessions, and anything where the default "send it to a meeting bot" workflow is the part that worries the legal team.
The technical claim is narrow on purpose: the recording and transcript live in the browser workspace on the current device. They don't leave unless you explicitly choose to export, back up, send to a BYOK provider, or switch to a cloud provider.
That's a workflow, not a compliance certificate. Whether it satisfies your policy is a call your security team makes. Keeping transcription on-device just gives them a much smaller surface to evaluate.
How it works
- Open jotty.pro on the device approved for the meeting.
- Keep transcription on-device for the recording and transcript.
- Review the transcript before generating any summary or export.
- If your policy allows it, send only selected passages to a BYOK provider.
- Keep cloud providers off for this workflow until your team has signed off on cloud transcripts.
How it compares
| Option | Where audio and transcript live | Best fit |
|---|---|---|
| Cloud meeting bots | Vendor infrastructure | Routine meetings where the vendor is already approved |
| Hardware recorders | Device, then wherever you sync the file | Teams with a physical recording workflow |
| jotty.pro on the device | Browser workspace on the current device | Sensitive meetings that need device-scoped handling |
Honest answers
Can we prove the local workflow during a security review?
Yes. Your security team can inspect the browser session directly and decide what gates to require before allowing BYOK, export, backup, or any cloud-provider action. The on-device path is small enough to reason about in one sitting.
Should every confidential meeting default to on-device?
On-device is the safer default when content is sensitive, but the bigger questions (whether to record at all, what consent the participants need, who's allowed to attend) still belong to your organization. We just narrow the technical question to "where does this content live?"
What if we need the transcript on another device later?
That's a cloud-provider or export decision, not an on-device one. Don't switch this workflow to a cloud provider until your team has reviewed the Privacy Policy, Terms, and any internal approval requirements for cloud transcripts.
If your IT team has already approved a transcription provider and the speed matters, see the cloud-provider version. Same local transcript storage, the provider does the heavy lifting.