No fake offline promise
If you need every voice workflow to run fully offline, Peanut is not making that claim today.
Trust and controls
A voice app should be clear about where your words go.
Peanut does not claim to be fully offline. It is a cloud-provider based desktop voice workspace with local app history, explicit provider settings, bring-your-own key options, and clear permission requirements.
Cloud providers
Audio and text may be sent to configured providers for transcription, speech, translation, and AI cleanup.
Local app data
Settings, snippets, history, and workflow data can live on your device for app continuity.
Provider choice
Use shared access after sign-in or bring your own keys where supported.
Know the provider path
Peanut exposes supported provider choices for speech-to-text and text-to-speech, including OpenAI and ElevenLabs options.
Bring your own keys
Use your own provider account where supported when direct billing, account ownership, or operational separation matters.
What happens in common workflows
Workflow
What Peanut may process
Control
Dictation
Recorded audio and generated text
Provider settings, BYOK where supported, local history controls
Read-aloud
Selected text and generated audio
TTS provider, voice, speed, and provider key settings
Translate Lab
Selected or spoken text plus translated output
Target language, shortcuts, and provider settings
Snippets and history
Saved text, triggers, recent sessions, and metadata
Stored locally for workflow continuity
Privacy should be specific.
Marketing pages can summarize the model, but the legal policy is the source for current privacy terms and contact details.