Privacy and meeting controls
Know what happens to your meeting data.
A desktop app still uses cloud services for transcription and AI. Here is how the documented Mufal workflow handles audio, meeting context and optional sync.
Mac and Windows. No API keys required to start. See plan limits.
Audio becomes a transcript
During transcription, audio is sent to AssemblyAI for speech-to-text processing. Running on your desktop does not mean transcription happens entirely on your device.
AI requests include relevant context
AI answers, summaries and follow-up drafts send relevant transcript text, prompts and other selected context to OpenRouter and the selected model provider. Review the Privacy Policy for the data categories and providers involved.
Cloud sync is a separate choice
Meeting data is stored on your device. Enabling cloud sync or manually syncing sends meeting data to your Mufal account. Connected Codex and Claude Code integrations can retrieve cloud-synced context you authorize them to access.
Make transcription clear to participants
Tell participants how you plan to use transcription and AI, agree on it before starting, and follow your organization's policies. A bot-free call or screen-sharing setting does not replace that conversation.
Get the documentation your team needs
Read the Privacy Policy and Data Processing Agreement before sharing sensitive meeting content. Contact [email protected] for access, export or deletion requests, or to request security and audit documentation for your review.
Questions before you start
Is Mufal fully offline?
No. Transcription and AI features use external services. Local storage and optional cloud sync are distinct from processing by AI providers.
Does bringing my own key keep all data local?
No. Your key changes the provider account used for a request. Audio and AI context still need to be processed by the selected services.
Try it on your next conversation.
Start with a short session, check the transcript, and ask your first question.