Privacy, in plain language.
Optional cloud read-aloud
When no matching installed voice is available and the server has Azure Speech configured, Read aloud asks permission to send the selected answer to Microsoft Azure for audio generation. The application keeps the returned audio in memory for playback and releases it when stopped or closed. No audio is intentionally saved by this application. Microsoft’s processing and retention terms apply. For Dari, the optional Persian (Iran) voice uses different pronunciation and is explicitly labeled before use.
What stays on your device
By default, conversation messages and extracted document text stay in the current page session and are discarded on a fresh page load. Preferences and saved glossary entries persist in browser storage. You may enable local chat history in Settings; that can retain sensitive content, including source excerpts. Do not enable it for sensitive conversations.
When information leaves your device
Every AI conversation uses the Meta API and sends your current message, bounded context from this conversation, and attached document excerpts to the configured Meta API. You must affirm permission before sending. The request sets store:false, which is not a guarantee about all provider processing or retention; Meta’s applicable terms and privacy practices still apply.
Voice
Microphone use begins only after your action and browser permission. Browser speech recognition may send audio to a browser or operating-system service. BridgeVoice does not record or save audio. The visual level meter briefly accesses microphone audio locally while listening. Read-aloud is explicit and depends on installed browser voices.
Documents
PDF, DOCX and UTF-8 TXT files are sent to the BridgeVoice server for text extraction after confirmation. The application processes them in memory and does not intentionally store them. Extracted text stays in your session unless you export, enable history, or send it to Meta. Text extraction has size and page limits. Scanned images and OCR are unsupported.
Storage and deletion
Settings lets you delete saved history or all BridgeVoice browser data. New chat clears active conversation context. Downloaded exports are outside the application’s control; delete them yourself when no longer needed. Browser profiles, backups, extensions, server infrastructure and third-party processors have their own privacy properties.
Logs and tracking
The application adds no advertising trackers or analytics collecting conversation content. Application code does not log prompts, files or API keys. Your hosting provider may keep operational access logs. Before handling sensitive data, review that provider’s configuration and terms.
Consent and limitations
Use fictional examples for demonstrations. Obtain permission from everyone whose information you process. BridgeVoice does not claim HIPAA compliance or medical/legal certification. The operator of any public deployment must provide a contact method and publish deployment-specific retention and processor information before offering the service to real users.
BridgeVoice supports human interpreters. All AI-generated translations and terminology suggestions require professional judgment and verification.