On-device use cases - voice notes that don't leave by default
Keep recording, transcription, storage, and search on the current device. Transcripts live in the browser workspace and persist in local DuckDB. They don't leave unless you explicitly choose an export, backup, BYOK summary, or switch to a cloud provider.
This is the right default when "where does this content live?" needs an obvious answer before anything else happens — confidential meetings, regulated professional notes, personal journaling, technical conversations, or client calls.
When to keep transcription on-device
- Confidential meeting transcription: boardroom, M&A, and strategy sessions that shouldn't default to a meeting-bot vendor.
- Legal and clinical voice notes: device-scoped workflow for attorneys, clinicians, and other regulated professionals.
- Private voice journaling: raw founder brain dumps and personal reflection that stay on the device you journal on.
- BYOK AI notes for developers: on-device transcription, with hosted models reserved for specific excerpts.
- Client-call transcription for consultants: start on the device, decide per-passage what moves to BYOK, export, or a cloud provider.
If your IT or compliance team has already approved a cloud provider and you want the speed or model access that comes with it, see the cloud-provider branch. Same local DuckDB storage, the provider handles the AI.