Privacy Policy for MeetMute — Mute Control for Google Meet
Last updated: May 2026
MeetMute is a Chrome extension that provides microphone mute control for Google Meet video calls. This privacy policy explains how the extension handles your data.
- DATA COLLECTION
MeetMute does not collect, transmit, store, or share any personal data or browsing information. The extension runs entirely within your browser.
- WHAT THE EXTENSION ACCESSES
Google Meet page content: MeetMute reads the Google Meet page DOM (Document Object Model) to detect whether you are in a call, whether your microphone is muted, and to toggle mute by clicking Meet's built-in mute button programmatically.
Browser tabs: MeetMute checks which browser tabs have Google Meet open to determine if a call is active. It displays a floating mute button on other tabs so you can control your microphone without switching to the Meet tab.
Local storage: Your preferences (floating button position, animation style, notification settings, site exclusions, push-to-talk setting) are saved using Chrome's local storage API. This data is stored only on your device and never transmitted.
- WHAT THE EXTENSION DOES NOT DO
• Does not access, record, or transmit any audio or video content • Does not track browsing history or activity on any website • Does not communicate with any external server, API, or cloud service • Does not collect analytics, telemetry, crash reports, or usage data • Does not access your Google account credentials or personal information • Does not read or modify content on any page (other than rendering its own floating button UI) • Does not use cookies, fingerprinting, or any tracking mechanism
- THIRD-PARTY SERVICES
MeetMute does not integrate with, transmit data to, or receive data from any third-party service.
- PERMISSIONS JUSTIFICATION
Host permission (meet.google.com): Required to inject a content script that observes the Meet page DOM to detect call state (join, leave, mute, unmute) and toggle the microphone button.
Host permission (all URLs): Required to inject the floating mute toggle button on all browser tabs during an active call. The extension renders only its own isolated UI element (using a Shadow DOM) and does not read, modify, or interact with any page content.
Storage permission: Stores user preferences locally using Chrome's storage API.
Tabs permission: Queries browser tabs to find active Google Meet sessions and to broadcast mute state updates to the floating button on all tabs.
Notifications permission: Displays optional desktop notifications confirming mute state changes when toggled from a non-Meet tab. Users can disable this in extension settings.
Alarms permission: Internal timing for badge flash animations, service worker keep-alive during calls, and notification auto-dismiss.
Scripting permission: Injects content scripts into tabs that were open before the extension was installed, so the floating button appears without requiring a page reload.
- DATA RETENTION
All extension data is stored locally using Chrome's built-in storage APIs. Data is automatically deleted when the extension is uninstalled. No data persists outside the browser at any time.
- CHILDREN'S PRIVACY
MeetMute does not knowingly collect any information from children or any users. The extension collects no information from anyone.
- CHANGES TO THIS POLICY
Updates to this privacy policy will be posted at this URL. As MeetMute does not collect any user information, there is no mechanism to notify users directly of policy changes.
- CONTACT
For questions about this privacy policy or the MeetMute extension, please open an issue on the MeetMute GitHub repository or contact the developer.