Mimo Privacy Policy

Effective date: 4 November 2026

Publisher: Mimo

Privacy and support contact: Contact the developer using the verified contact email shown on Mimo BETA’s Chrome Web Store listing.

This policy covers version 0.14.2 of the Mimo BETA Chrome extension distributed under the Mimo publisher name. Mimo helps you follow live audio, offers occasional additional contributions, and prepares meeting notes when you stop listening.

Information Mimo handles

• Audio you choose to record. After you start listening and grant microphone access, Mimo captures your microphone and, where Chrome permits it, audio from the selected tab. It does not record your camera, other tabs, or your entire desktop. If tab capture is unavailable, listening can continue through the microphone.
• Conversation and generated content. Mimo transcribes speech and uses transcript passages, relevant conversation context, your optional objective, and current-session feedback to prepare current understanding, additional contributions, and final meeting notes. Content may include names or other personal information spoken in the session.
• Current-tab information. Mimo reads the selected tab's title and URL to identify the source in its interface and determine whether tab audio can be captured. It does not read your full browsing history or extract page text through a content script. Conversation audio from a website can itself contain website content.
• Preferences and technical information. Mimo stores preferences such as appearance, objective, and microphone readiness in Chrome's local extension storage. Its service receives ordinary connection information, including an IP address and request headers, and temporary request/session identifiers needed to operate the service. Metadata-only failure details may be stored locally for troubleshooting. There is no advertising or third-party analytics SDK in this beta build.

Cloud processing and service providers

Speech windows are transmitted over HTTPS to Mimo's backend and forwarded to DeepInfra for speech recognition. Transcript text, your objective, relevant context, previous model output, and current-session feedback may be sent through the same backend to DeepInfra to prepare and check live understanding, contributions, and meeting notes. The full meeting transcript is processed when preparing final notes, in chunks if needed. Cloud processing is part of listening; this beta does not provide an offline transcription or AI mode.

Our backend processes request content in memory and does not create a meeting-content database or intentionally write audio, transcripts, prompts, or model answers into application logs. Proxy access logging is disabled. Server and network security/error records can include technical connection details such as IP addresses, request paths, and timestamps; they are separate from a saved meeting history.

We do not routinely have people read or listen to your meeting content. Human access is limited to what you explicitly authorize for a specific support request, what is necessary for security or abuse prevention, or what is required by law. Do not send private meeting content with an initial support request; you can describe the problem without sharing a recording.

DeepInfra's published inference policy describes temporary processing of ordinary inference content and no training on that content for the models used by this beta. Its terms allow exceptions, including legal/security needs, authorized support, and separately enabled retention features. Provider operational metadata can be retained. See DeepInfra's data-privacy documentation, privacy policy, and terms. These are provider commitments, not a guarantee that all network or operational information is immediately erased. Mimo currently uses hosted Qwen speech recognition and DeepSeek text generation through DeepInfra, rather than Google or Anthropic model endpoints.

Data is processed on Mimo's hosting infrastructure and DeepInfra's infrastructure and may be processed outside your country. This beta does not offer a user-selectable processing region. Infrastructure providers can process information as necessary to host, secure, and deliver these services. The publisher may disclose information where required by law or necessary to address fraud, security incidents, or abuse.

Retention on your device and exported files

Current-session audio, transcripts, understanding, contributions, and meeting notes are held in the extension's temporary application memory. Mimo does not create a persistent consumer meeting library or restore an unsaved session after Chrome or the extension restarts. Unsaved work can be lost if Chrome, the extension, or its recording process closes. Closing only the visible panel does not necessarily stop the background session; use Stop to end listening.

When you stop, Mimo asks you to choose a folder and prepares three files: combined audio-*.webm, transcript.txt, and mom.txt. Pending results remain in temporary memory while you save, retry, or discard them. Successfully exported files remain in your chosen folder until you delete them. Your operating system or a cloud-sync service you use for that folder may manage those files independently. The open panel may keep the current result visible until you start a new meeting or close it.

Preferences remain in Chrome storage until changed or the extension is removed. Existing development data from older unpacked builds is not automatically deleted by installing or upgrading this beta; it is not loaded as consumer meeting history. The separate developer Replay Lab is not included in the Web Store package or covered by this consumer-session description.

How information is used

Mimo uses the information above to capture and transcribe your chosen audio, prepare and display live assistance and final notes, save the files you request, apply your preferences, and diagnose or secure the service. We do not sell meeting content, use it for advertising, or use it to train models. We do not send messages or publish your notes on your behalf.

Mimo's use and transfer of information received from Chrome APIs is limited to providing or improving these user-facing features in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Your choices and requests

• Start listening only when you have permission to record and process the audio, and inform other participants as appropriate.
• Use Stop to end recording. Final transcription and meeting-note processing can continue after Stop to finish the session.
• Choose the export folder, retry an unfinished export, or discard unsaved results. Discard does not delete files already exported.
• Delete exported files through your file manager. Change microphone permission through Chrome, and uninstall Mimo to remove its extension preferences.
• A diagnostic report is downloaded only when you request it. It contains technical status/version/failure information rather than audio, transcript, meeting notes, or service credentials. Nothing is automatically sent to the publisher by this action; review any report before voluntarily sharing it.
• Contact the developer using the email shown in the contact information on Mimo BETA’s Chrome Web Store listing for privacy questions or applicable access/deletion requests. Mimo has no user account or persistent meeting library to retrieve; do not include a recording or transcript in an initial support email unless you intend to share it.

Changes

We will update this policy and its effective date when our data practices change. Material changes will be reflected in the extension and store disclosures where appropriate.