Cloud use cases - your provider, your key, transcripts still local
When you bring your own cloud provider, jotty.pro routes audio and AI calls to that provider under your own API key. We're a routing layer; the provider's terms govern what happens on their end. Transcripts persist locally in DuckDB on the device whether you use on-device transcription or a cloud provider, so the content you hold stays with you.
BYOK works both ways: a personal key for personal work, an org-provisioned key for team work. Org-provisioned keys are supported directly, so your IT can issue a shared OpenAI, Groq, Deepgram, or other supported provider key. We don't provision or hold enterprise keys.
When a cloud provider is the right call
A cloud provider fits when the provider your organization already trusts is the one handling the AI processing, and that relationship (contracts, BAAs, DPAs) governs compliance, not anything we manage.
- Confidential meeting transcription: board, M&A, and strategy meetings using a provider your security team has approved.
- Legal and clinical voice notes: regulated work backed by a BAA or DPA you sign directly with the chosen provider.
- Private voice journaling: richer self-reflection prompts under a personal key with the provider you already trust.
- BYOK AI notes for developers: provider-grade speaker diarization and fresh model versions on technical calls, under your key.
- Per-engagement consultant transcription: different provider and key per client, all routed under your control.
For workflows where no audio or AI call leaves the device, see the on-device branch instead.