Pages :
Last Updated: 2025 (Current Version 2.1.0)
Brivi Voice (“the Extension”) is a Chrome extension that provides voice transcription and note-taking capabilities. This Privacy Policy explains what information we collect through the Extension, how we use and store it, and the steps we take to protect your privacy. We are committed to handling your data in compliance with Google Chrome Web Store policies and applicable privacy regulations. By using Brivi Voice, you agree to the data practices described in this policy.
We only collect data that is necessary to deliver the Extension’s functionality. The types of data collected and their purposes include:
1.1 Microphone Audio (Voice Input): With your permission, Brivi Voice can access your device’s microphone only when you actively start a recording. Audio data is used solely to convert your speech to text (speech-to-text transcription) and provide you with a transcript. We do not listen to or record audio except during your initiated recordings. Audio recordings are processed in real-time and not stored on our servers once transcribed (except temporarily in memory or local cache for processing).
1.2 Transcribed Text and Notes: The text results of your voice transcription (and any notes you save or content you manually add via the Extension) are stored so that you can review, edit, and sync them across devices. This may include any user content you choose to input or save:
1.2.1 Transcripts: The Extension pastes the transcript into the active field or note as you request. A copy of each transcript is saved to your personal History (log of past transcriptions) and/or Notes in your Brivi account so you can access it later.
1.2.2 Notes & Notebooks: If you use the note-taking features (e.g. pressing Alt+N to save a note), the Extension will save the transcribed text along with any additional content (such as page title or selected text) as a note in your account. You can organize notes into notebooks, and these notes are stored in our cloud database for synchronization across your devices.
1.2.3 Selected Text: If you use the “Add to Notes” context menu on a webpage, the Extension will capture the text you highlighted and save it as a note (along with the page source information) for your later reference. This happens only when you manually invoke the context menu option.
1.2.4 Screenshots: If you enable it, Brivi Voice can capture a screenshot of the current page when saving a note (e.g. with Alt+N) to help you remember context. The image is stored securely in your account’s cloud storage and attached to the note. Screenshot capture is optional – you can disable it in settings, in which case no screenshots will be taken.
1.3 Authentication Information: To use cloud sync and account-based features, you may create a Brivi account. During sign-up we collect your email address and a password (or handle OAuth credentials) to authenticate you. You might also provide a display name or profile image (optional) for your account. This information is used to create and secure your personal account, to sync your data (notes, transcripts, settings) across devices, and to contact you with critical account or service updates. Passwords are never stored in plaintext; they are handled securely (hashed and managed by our backend authentication service). The Extension may store an authentication token (e.g. a session access token and refresh token) in Chrome’s secure storage to keep you signed in – this token is protected and only used to communicate with our service (e.g. to fetch your notes or submit transcription requests).
1.4 Browser Tab Information: The Extension requests access to your browser tabs and active page for specific functionality. We do not monitor your browsing history; however, when you actively use Brivi Voice, we may access the current tab’s URL and title to:
1.4.1 Insert transcribed text into the correct page and field that you have focused (we need to identify the active tab and input element to paste your text).
1.4.2 Save context with your notes: when you save a voice note or use “Add to Notes,” we attach the source page’s URL or title to the note (so you know where it came from). This page info is stored as part of your note in your account.
1.4.3 Capture the visible tab for screenshots (as described above).
Aside from these cases, the “tabs” permission is not used to collect your browsing data. The Extension does not collect a list of all sites you visit or run any analytics on your browsing habits. You can also restrict Brivi Voice on specific sites (see User Control below).
1.5 Clipboard Data: The Extension may utilize your clipboard only to facilitate copy-paste actions that you trigger. For example, if you press the Alt+C shortcut to copy the last transcript and paste it, Brivi might programmatically copy text to the clipboard and immediately paste it into a field. This is done to deliver the functionality you requested. We do not read or collect arbitrary clipboard content from you; we only access the clipboard in direct response to your action (copying transcripts or notes you chose to copy). The clipboard contents (e.g., a transcript text) are not transmitted to any server – it stays on your device and is only used to insert text into your target field.
1.6 Notifications and Alerts: The Extension may send you desktop notifications (e.g., to indicate recording has started or finished, or to warn of transcription limits). These use Chrome’s notifications API. No personal data is collected from your device for notifications; they are purely to inform you of the Extension’s status (using the data it already processed, like telling you when transcription is done). You can control notification permissions via your browser settings.
1.7 Local Storage (Settings & History): Brivi Voice stores certain data locally in the extension’s Chrome storage on your device:
1.7.1 Settings: Configuration preferences (e.g. theme mode, whether to save screenshots, language settings, pause/denylist status) are kept locally so the Extension remembers your choices.
1.7.2 Transcription History Cache: A recent history of transcripts (including transcribed text, timestamp, and the source website) is maintained locally for quick access. This lets you review or retry transcriptions without always fetching from the server, and it helps support offline or context menu features (like showing “recent transcriptions” for quick paste). By design, audio recordings themselves are not permanently stored in local history – only the text and metadata. In rare cases of a transcription failure, the Extension may keep the audio data locally temporarily (marked for retry), but it clears it after a successful retry or when no longer needed to conserve space.
1.7.3 This local data never leaves your device; it exists to improve performance and usability (e.g., showing your last transcript for copying). You can clear the history at any time via the Extension’s interface (e.g., delete entries in the History tab) or by resetting the Extension.
1.8 Usage Statistics: Brivi Voice collects minimal usage data to ensure fair use and improve the service. For example, we log the length of your recordings and the number of transcriptions you perform, which is tied to your account’s usage quota. This includes data like the number of recordings in a billing cycle, total transcription minutes used, and feature utilization (e.g., how often a particular feature is used). We do not collect telemetry about your keystrokes or unrelated browsing activity – only metrics directly related to the Extension’s functions (e.g., minutes of audio transcribed). Usage data helps us provide your subscription status (if applicable), warn you of any usage limits, and plan improvements. This data may be stored in our backend logs or databases associated with your user ID.
1.9 Support Communications (Optional): If you contact us for support or feedback, we may collect the information you voluntarily provide (such as your email, and the details of your support request). This is only used to assist you and improve the service. (Note: Support requests are typically handled via our website or email, not directly through the extension UI.)
We do not knowingly collect any sensitive personal information unrelated to the Extension’s core functionality. In particular, Brivi Voice does not access your contacts, passwords, or other personal data on your device beyond what is described above. The Extension’s broad host permission (<all_urls>) is required to allow the voice recording overlay and text insertion on any webpage you choose, but we design it with “minimal mode” privacy guardrails – you can pause the extension or exclude specific sites so it doesn’t run there, and by default it only reacts when you interact with it. We never transmit page content or browsing data back to our servers except when it’s part of a feature you invoked (such as saving a note or screenshot that you requested).
We use the collected data strictly to provide, improve, and personalize the Brivi Voice service to you. Below is how we handle and protect each category of data:
2.1 Providing Core Features: All data we collect is used to enable the Extension’s features you expect. For example, your voice audio is sent to our transcription service (via secure connection) to return text results; your transcribed text and notes are stored so that you can access them through the Extension’s dashboard or web app; and your email credentials allow you to securely log into your account. We do not use your voice recordings or transcripts for advertising or profiling – only to deliver the functionality (transcribing your speech and managing your notes).
2.2 Cloud Synchronization: Brivi Voice uses a cloud backend (hosted on Supabase) to sync your data (notes, transcripts, notebooks, etc.) across devices. When you are signed in, transcripts and notes are uploaded to our secure cloud database under your account. This allows you to view and edit your content on multiple devices in real time (e.g., the Extension’s Dashboard or companion web app will reflect updates instantly via WebSocket sync). We store this data on our servers to ensure it persists between sessions and is available only to you. Each user’s data is isolated and protected by authentication and database rules – other users cannot access your notes or history.
2.3 Storage and Retention: Your account data (including notes, transcripts, and profile info) is stored in our cloud database and object storage. We retain this data as long as needed to provide the service to you, or until you request deletion. If you delete a note or transcription history item, it will be removed from our servers (after any necessary processing). We may retain minimal logs or usage records as required for legitimate business or legal purposes, but we strive not to keep personal data longer than necessary. Local data stored in the Extension (like settings or cached history) stays on your device; if you uninstall the Extension or reset its data, that local data is wiped.
2.4 Security Measures: We take data security seriously. All communication between the Extension and our servers is encrypted via HTTPS and WSS (secure WebSocket) connections, protecting your data in transit from eavesdropping. On the server side, we implement access controls and encryption to safeguard your data:
2.4.1 Our cloud database enforces row-level security, meaning each note or transcript is tagged with your user ID and our servers ensure that only you (authenticated with your token) can access your data.
2.4.2 We use authentication tokens and session management best practices to secure your account. For example, the Extension stores session tokens in Chrome's session storage (not persistent disk), and we periodically refresh them to prevent unauthorized access or expiration issues. Tokens are never exposed to websites you visit; they are confined to the Extension’s context.
2.4.3 Passwords (if you use email/password login) are processed by our authentication provider and stored hashed; the Extension never sees your raw password beyond securely transmitting it for login.
2.4.4 We maintain secure servers and rely on reputable cloud infrastructure (Supabase on AWS/GCP) to host your data. Supabase storage is used for files like note screenshots or profile photos, and access to those files is secured by token-based URLs or restricted policies.
2.4.5 We implement organizational measures such as restricted access: only authorized personnel or processes (e.g., the server functions) can read your data in the database. Internally, we redact sensitive values in logs (for instance, authentication tokens are masked in debug logs). We also regularly update dependencies and conduct security reviews to patch any vulnerabilities.
While no system can be 100% secure, we continually work to protect your information and update our security measures in line with best practices. If we become aware of a data breach that affects your personal data, we will notify you and take appropriate steps in accordance with applicable laws and Chrome Web Store policies.
2.5 Usage Data: Usage statistics (like minutes transcribed or number of notes) are used for two main purposes:
2.5.1 To enforce limits and provide account info: If there is a monthly free limit or subscription plan, we track your usage to inform you of your remaining minutes and prevent abuse. For example, we will warn you as you approach your plan’s limit and stop further transcription only if a limit is exceeded. These usage counters are associated with your account.
2.5.2 To improve the service: Aggregated usage metrics help us understand how features are used (e.g., which features are popular, average note lengths, etc.). This helps in making product decisions and improving performance. These analytics are first-party and focused on feature improvement. We do not use third-party analytics trackers in the Extension that would profile your browsing. Any analytics are performed on our side with aggregated data and are never sold or shared for advertising. Additionally, any optional diagnostic logging (for debugging) is user-controlled via a setting (default off).
2.6 Cookies: The Extension itself does not use cookies for tracking. However, if you log into Brivi via our web app or use the web-based OAuth flow, our website may set an authentication cookie. The Extension can utilize that cookie to detect your logged-in session (for example, it calls a web API to import your session token if you logged in on the website). This is solely to streamline sign-in. These cookies are only used for authentication and session continuity, not for advertising. You can clear them by logging out or via your browser’s cookie settings.
We do not sell or rent your personal information to any third parties. Data collected by Brivi Voice is used for the service’s functionality and is generally only accessible by you and Brivi (the service provider). In particular:
3.1 No Unauthorized Third-Party Sharing: We do not share your voice recordings, transcripts, notes, or any personal data with advertisers or social media companies or other unrelated third parties. Your data is your own, and our business model is subscription/feature-based, not advertising.
3.2 Service Providers: We rely on a few trusted third-party services (as processors) to operate Brivi Voice. These include:
3.2.1 Cloud Infrastructure (Supabase): Supabase is our backend-as-a-service platform, which provides the database, authentication, file storage, and server functions for Brivi Voice. All of your data that is stored or processed in the cloud resides on Supabase’s infrastructure (which is hosted on reputable cloud providers). Supabase acts as a data processor on our behalf. We have configured it with robust security rules (as described) to protect your data. Supabase does not use your data except to store and retrieve it as needed to serve Brivi Voice.
3.2.2 Speech-to-Text Engine: When the Extension sends your audio for transcription, it contacts our server (hosted on Supabase Edge Functions) which in turn uses a speech-to-text engine (which may be an integrated third-party API or our proprietary model). This means your audio data is potentially handled by that transcription service only for the purpose of generating text. We ensure any third-party STT provider (if used) is reputable and that audio is transmitted securely and not retained by them. For example, if we utilize a provider like OpenAI Whisper or Google Cloud Speech, the audio is sent over secure channels and used transiently to return a transcript. We do not allow them to use your audio for training or any purpose beyond the immediate transcription request.
3.2.3 Email/Support Tools: If you contact us or sign up for updates, we might use an email service provider to send communications. This would involve sharing your email address and any necessary info with that service purely to send the email.
3.2.4 Payment Processor: (If applicable) For managing subscriptions or payments, we use a third-party payment processor. Payment information you provide (such as credit card details) never goes through the Extension; it is handled directly by the secure payment provider. We do not store your full payment card details on our servers. We may store references to transactions or subscription status (e.g., that your account is paid through a certain date) but not sensitive payment data.
All such service providers are contractually bound to protect your data and use it only for the purposes of providing services to us (in line with this policy).
3.3 Within Brivi (Personnel): Our small team may have access to the data in our database when necessary (for example, for customer support or debugging an issue you reported). Such access is restricted to authorized personnel and only used for legitimate service purposes. We treat user data confidentially.
3.4 Legal Requirements: We may disclose information if required by law or valid legal process (such as a subpoena or court order), or if we believe in good faith that disclosure is necessary to comply with legal obligations. We would only do so after verifying the request’s lawfulness and only provide the minimum necessary data. Additionally, if needed to enforce our terms of service or protect the rights, property, or safety of Brivi or our users, we might disclose relevant data. We will notify you of any such legal disclosure if permitted.
3.5 Business Transfers: If Brivi (the service) is ever involved in a merger, acquisition, or sale of assets, user information might be transferred to the new owner as part of that deal. If that happens, we will ensure the successor honors the existing privacy commitments or notify you and get consent if required.
Apart from the above, no one outside of Brivi can access your personal data unless you explicitly share it (for example, if you export and send a note to someone, that’s under your control). The Extension’s data flows are self-contained between your device and our service.
We design Brivi Voice with user privacy in mind and provide controls so you can manage your data and experience:
4.1 Consent for Microphone Use: The first time you use Brivi’s voice recording, Chrome will prompt you to allow microphone access. You have the choice to allow or deny. If you deny, the Extension will not access your microphone and voice features will be disabled. Even after granting access, the microphone is only active when you explicitly start a recording; you can always stop a recording or revoke the permission via Chrome settings.
4.2 Opt-In Features: Features like screenshot capture on note save are optional. By default, screenshots are enabled to enhance your notes, but you can turn this off in Settings if you prefer not to capture page images. Similarly, the context menu options (adding selected text to notes) are provided for your convenience; if you don’t use them, no text is collected.
4.3 Pause or Restrict the Extension: We understand you may not want the Extension running on certain websites or during certain times. Brivi Voice offers a Privacy Pause toggle and a Site Denylist in the settings.
4.3.1 If you enable Pause, the Extension will temporarily deactivate its functionality on all sites – it will not inject the recording UI or respond to the hotkeys until you un-pause.
4.3.2 You can also add specific domains to a denylist; when you visit those sites, the Extension automatically stays inactive. This gives you control to exclude sensitive pages (e.g., your banking site or email) if you wish. In “minimal mode” on a denied site or when paused, Brivi Voice does not inject any scripts or collect any data from that page.
4.3.3 You can remove sites from the denylist or resume normal operation at any time via settings. These controls let you balance convenience with privacy as you see fit.
4.4 Viewing and Editing Your Data: You can review all your saved transcripts and notes by opening the Brivi Voice Dashboard (either via the Extension’s popup or a new tab). The Dashboard provides access to your History (all past transcriptions) and Notes. You can search your transcripts, copy or export them, and delete any items you don’t want to keep. For notes, you can edit content, move notes between notebooks, or delete notes. Any deletions or edits you make are synced to our server and permanently remove or update that data from your account (aside from any required backups, which are also protected).
4.5 Export/Import: We provide an option to export your transcription history (e.g., as a JSON file). This allows you to have your data in a portable format. You can also import such a file to restore history if needed. Note that exported files are stored on your local machine (you choose the location) and are not controlled by us, so handle them carefully. We do not automatically upload any exports.
4.6 Account Settings: In the Account section of the dashboard, you can update your profile information (such as your display name or avatar) if you provided one. You can also log out of the Extension at any time via the Logout option – this will clear your session tokens from the Extension and stop any data sync until you log in again. Logging out does not delete your data from our cloud, but it ensures the Extension no longer has access until you sign in again.
4.7 Account Deletion: You have the right to delete your account and personal data. While we hope you enjoy Brivi Voice, if you wish to delete your account, you may contact our support team to request deletion (see Contact section below). Upon verification of your identity, we will delete your account information, including your notes, transcripts, and profile data, from our servers. (We will inform you of any data we are required to retain for legal reasons, but otherwise we will permanently erase or anonymize your personal data.) Note that deleting your account is irreversible – you will lose access to your saved notes and history. Currently, account deletion is handled through support to ensure it is secure; in the future we may offer an in-app delete option for convenience. If you simply uninstall the Extension, your cloud-stored data remains on our servers tied to your account until you delete it or request deletion.
4.8 Children’s Privacy: Our service is not intended for children under 13. We do not knowingly collect personal data from anyone under 13 years old. If you are under 13, please do not use the Extension or provide any personal information. If we learn that a child under 13 has created an account or provided personal data, we will take steps to delete that information. If you are a parent or guardian and believe your child has used Brivi Voice, you can contact us to have the data removed.
4.9 Privacy Preferences: If we introduce any analytics or error-reporting that collects additional data, it will be strictly opt-in. As of now, the Extension’s only telemetry is usage counts as described, which are essential for the service. We do not provide targeted advertising, so there’s no ad personalization to opt out of. Should our practices change, we will update this policy and give you the choice where required.
Brivi Voice adheres to Google Chrome Web Store’s User Data Policy and applicable privacy laws. This means, in summary:
5.1 We only request permissions (microphone, tabs, storage, etc.) that are necessary for the Extension’s core features, and we have outlined above how each permission is used to benefit you. We do not use these permissions to capture data for unexplained purposes. For example, while we have access to “<all_urls>” for content scripting, we do not harvest your browsing content; it’s only used for the active functionalities (transcription UI and insertion). Our use of permissions is transparent and limited to the context of your interactions.
5.2 We follow the principle of data minimization. We do not collect more data than we need to provide the service. If in doubt, we prefer to keep data on your device under your control (for instance, recent transcripts in local history) rather than constantly sending everything to our servers.
5.3 We have a clear and accessible privacy policy (this document) as required, and we will update it if we make any significant changes to how we handle your data. If changes are material, we will notify users via the Extension or email so you can review the changes. We will not reduce your rights under this policy without your consent.
5.4 We respect user rights under regulations like the EU GDPR and CCPA. That includes the right to access your data, correct it, delete it, or port it. As described, you already have tools to view and modify your content. For any additional requests (e.g., a complete export or deletion of all data), you can contact us and we will assist in accordance with applicable law. We will also honor applicable opt-out rights (though we don’t sell data, so CCPA “Do Not Sell” is not applicable).
5.5 If you are located in a region with data protection laws, know that your data may be transferred to and stored in our servers which could be in the United States or other jurisdictions. We rely on services that implement appropriate safeguards for international data transfers (e.g., standard contractual clauses). By using the Extension, you acknowledge that your data may be processed in countries outside your own.
5.6 We ensure compliance with any other relevant Google policies. For example, if we integrate with any Google APIs in the future, we will adhere to Google API Services User Data Policy (though currently the Extension’s Google integration is limited to optional OAuth via Chrome Identity and we don’t access Google user data beyond authentication).
In summary, we are committed to protecting your privacy and being transparent about our practices. We regularly review our data practices to ensure we meet our obligations and your expectations of privacy.
If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us. We’re here to help and will respond to privacy inquiries promptly.
Contact Email: You can reach our support team at [email protected] (or the contact method listed on our website). Please include “Privacy” in the subject line if your inquiry is about data or privacy issues.
Support: Additionally, for general support you can use the “Support” link in our web dashboard or extension, which will direct you to our help resources or contact form.
We value your feedback and privacy. If you need to access, correct, or delete your data, or have questions about how Brivi Voice safeguards your information, do not hesitate to contact us. We will work with you to address any issues in accordance with this policy and applicable law.
By using the Brivi Voice Chrome Extension, you acknowledge that you have read and agree to this Privacy Policy. Thank you for trusting Brivi Voice with your voice notes and transcription needs – we are dedicated to keeping that trust.
Email: [email protected]
Website: https://brivi.app