MusicMute privacy policy

Operator and contact

MusicMute is operated by MusicMute. This policy covers the Android and iOS apps, the web app, MusicMute Local for Mac, its Chrome extension, and the MusicMute services they use. Features and data handling differ slightly by client.

MusicMute removes background music from audio to produce voice-only results.

For privacy, support, access, correction, or deletion questions, email hatemragapdev@gmail.com or use the support page. Do not send passwords, authentication tokens, browser cookies, private audio, or protected download URLs. Support may ask you to verify ownership before acting on an account request.

Information MusicMute handles

• Account and authentication information: Firebase user ID, profile name, email when available, verification state, linked sign-in providers, and the credentials or session records needed for sign-in. The Mac app stores its sign-in credentials in macOS Keychain; they are not sent to the Chrome extension.
• Audio and user content: audio you select or upload, prepared audio, voice-only results, filenames, duration, size, processing history, source URLs and identifiers you submit, and source metadata.
• Device and service information: where supported, a MusicMute installation identifier, Firebase installation and messaging identifiers, push token, device model, operating system, app version and build, request metadata, and security/session records.
• Diagnostics: bounded crash, error, performance, and processing diagnostics needed to operate, secure, and troubleshoot the service. Chrome extension and Mac app diagnostic reports remain on your device unless you choose to share an exported report; other clients and the backend may send privacy-filtered diagnostics to Sentry when enabled.

When a client prepares a selected local video for processing, it uploads prepared audio rather than the original video file.

Why the information is used

MusicMute uses this information to authenticate your account, enforce account and usage policy, prepare and process audio, deliver your private results, maintain your history, send processing notifications you request, support playback and export, prevent abuse, diagnose failures, provide support, and complete account deletion.

MusicMute does not sell personal information, transfer it to data brokers, use it for advertising, or use it to determine creditworthiness or for lending. Your data is used only for the disclosed features and for necessary service, security, and legal purposes.

Imports from links

When you submit a public link in the mobile or web app, MusicMute retrieves an audio-only stream for the item you selected and processes it. The mobile app does not fetch media from the link provider itself. Originals and voice-only results from supported public links enter private permanent shared storage and can be reused by other authorized accounts or scoped guests. Local file uploads and their results remain private to the owning account.

Import only material you own or are permitted to process. Confirming your rights is a statement by you; MusicMute does not verify ownership or grant permission to process third-party material.

Chrome extension and Mac companion

The Chrome extension plays a voice-only track synchronized with a supported YouTube watch video through the required MusicMute Mac app, and follows the processing choice saved in that app. MusicMute is independent of YouTube and Google. It processes only the selected audio and does not download the video file. With local processing selected, the Mac app obtains the selected audio online when needed, runs separation on your Mac, and keeps originals, vocals, processing metadata, and preferences in its managed storage on your device. Playback uses native messaging and a temporary protected loopback connection on the same Mac. Automatic local preparation is enabled by default for eligible playing videos; you can turn it off or set a shorter duration limit.

Chrome playback and preferences: on these watch pages, the selected canonical URL and video identifier, duration, playback position and speed, volume, mute state, and player/advertisement state. The extension uses these to add controls, prepare the selected audio through the Mac app, and synchronize vocals. Playback and language preferences and bounded diagnostics are stored in the current Chrome profile.

The Chrome extension does not read general browsing history, browser cookies, your Google password, or GPS location. It does not request browser geolocation permission. It does not log typed text or general keyboard activity. Its access is limited to these supported watch pages and is used only for the selected playback feature; it does not monitor unrelated browsing. MusicMute does not collect health, financial/payment, or personal-communication data for this feature.

Account credentials and guest capabilities are handled by the Mac app and are not sent to the Chrome extension.

To obtain audio locally, the Mac app acts as a logged-out guest of the source platform and does not import your Chrome account, profile, or browser cookies. The source platform and its media servers receive these requests, and may return anonymous session data for that request. The source platform may refuse access; MusicMute does not bypass login requirements.

With local processing selected, no MusicMute account is required. When MusicMute's optional shared service is available, video metadata may be sent before playback to reserve shared saving. After vocals start playing in Chrome, the native publisher can upload original audio, vocals, and associated video metadata in the background, even while signed out. Native Mac preparation of audio from the same supported watch-page feature can release its prepared pair for saving when preparation completes, without waiting for Chrome playback. Pending saves can resume when the app or helper starts again. There is no separate per-video opt-in control for shared saving. Signing out does not disable it. If the optional shared service is unavailable, local preparation can continue without shared saving.

Accepted shared originals and vocals from this feature have no automatic expiry and can be reused by other authorized accounts or scoped guests. They survive local cache clearing, job deletion, or account/guest deletion. Personal audio or video files processed in the Mac app use the account-private saving path and do not enter this shared catalog.

Mac account and cloud processing

Signing in to the Mac app connects it to your MusicMute account and Library.

When MusicMute cloud processing is selected in the Mac app, manually starting a video sends its canonical watch URL to MusicMute using that saved choice, without a per-video confirmation in Chrome. MusicMute then retrieves the audio, removes its background music, and delivers the voice-only result to your Mac for playback. Cloud processing uses your account's processing allowance. Automatic preparation never submits new cloud processing.

Android app: permissions, backup, and analytics

• Android cloud backup is disabled for the app so local session data is not copied into Android backup.
• The Android app uses Internet access, notifications, foreground media playback, and wake lock for its core video and background-playback features.
• The app does not request camera, microphone, contacts, location, calendar, SMS, call log, photos, or broad device file access.
• MusicMute does not use mobile analytics for advertising and does not include an ads SDK.

Service providers and data recipients

• Firebase/Google: handles sign-in, account identity, authentication security, and, where enabled, installation identifiers and push notifications. These services receive the account or device information needed for those functions and network metadata.
• MongoDB and Cloudflare R2: MusicMute's database infrastructure uses MongoDB to retain account, session, processing, and usage records. Cloudflare R2 stores private input audio, voice-only results, and shared media; authorized temporary grants allow media transfer. Database and storage infrastructure process these records and files to provide the requested service.
• Hosting and network providers: run MusicMute's API, database, queue, and processing infrastructure and deliver service traffic. They process the records, media, and request or security metadata needed to host, deliver, and protect these services. Cloudflare also provides network delivery and protection.
• Sentry: where enabled for clients other than the Chrome extension and Mac app, and for the backend, receives privacy-filtered crash and reliability diagnostics to diagnose failures. Those reports exclude audio, credentials, and private media URLs. Chrome extension and Mac companion diagnostic reports remain local unless you choose to share an exported report.
• Source and acquisition services: the source platform and its media servers described in the Chrome extension and Mac companion section receive local audio-acquisition requests. MusicMute's private audio-acquisition providers receive submitted public source links and the request metadata needed to return audio for cloud imports. These services are used to acquire the selected public audio, not personal local file uploads.
• Companion downloads: Cloudflare R2's public release bucket delivers current Mac app and native runtime assets. GitHub and its download infrastructure deliver the model from its approved upstream GitHub release and may deliver runtime assets for older app versions. Download services receive request metadata to deliver these files. The public release bucket and GitHub download endpoints are not destinations for user audio or diagnostic reports; private media storage is separate.

Service providers process information for the functions described above. User-directed exports may be shared with an app or provider you select, and support receives information you choose to send. MusicMute may disclose information when necessary for security investigations or to comply with law.

Security and transfer

Service and media transfers use HTTPS or secure WebSockets, as applicable. Your media is stored privately and transferred through short-lived, access-controlled links. Access is authorized through account-scoped records, and storage is not public. Do not share credentials or signed transfer URLs. Native messaging and protected loopback playback stay on the same Mac. No system can guarantee absolute security.

Browser executable code is bundled with the Chrome extension. The Mac app separately downloads checksum-verified native runtime components and model data, installs them outside the extension, and runs the native tools in the companion rather than in Chrome. Each downloaded component ZIP is removed after its successful installation stage. Ordinary app replacement preserves the installed runtime, model, and app data.

Local diagnostics and your controls

The Chrome extension and Mac app keep diagnostic reports on your device, without automatic upload, telemetry, or analytics. Exporting diagnostics creates a local report, and you choose whether to share it. Reports omit audio, credentials, browser cookies, and private media URLs. Separately, MusicMute's online services retain operational and security records for the requests they receive.

You can turn automatic preparation on or off, set a duration limit, switch between vocals and original sound, or stop playback. Use "Stop playback and clear local cache" in the extension's local tools to clear its managed local results. This does not delete a shared result or cancel an already released background save. The local cache is subject to a managed size budget. Items in your account Library are managed separately and can be deleted by you.

Removing the Chrome extension removes its Chrome settings; it does not uninstall the Mac app or delete its files, cloud Library, or accepted shared public-link results. Contact support for privacy questions or requests about data the available controls do not remove.

Retention, local copies, and deletion

Your privately uploaded media, results, and account history remain until you delete the relevant item or your account, subject to processing cleanup and the deletion lifecycle below. Shared public-link media follows the separate permanent retention described above. Deleting an item or account removes its owned records and access; privately uploaded media is removed through the cleanup process, while accepted shared media remains private and accessible through authorized account-scoped records or scoped guest capabilities.

Signing out does not delete your cloud account or Library, accepted shared media, or retained account-owned local media. On Android, signing out clears the temporary listening-tools cache, including temporary passage exports; other retained media and history remain separated by account. Account deletion clears account-owned private copies when the app receives an accepted deletion response. Original selected files and copies you have exported remain under your or the receiving provider's control.

An accepted account-deletion request blocks access immediately and starts an exact 15-day recovery period. Permanent cleanup starts after that deadline.

Account data and privately uploaded local media remain inaccessible during the 15-day recovery period so the owner can request recovery. Permanent cleanup then removes the account profile, privately uploaded input and result audio, processing history, and account-linked device and push records. Audio imported from supported public links and its processed results are stored once in permanent shared storage and remain after job or account deletion; deletion removes the account's records and access to them. Shared storage remains private; MusicMute controls access through authorized account records or scoped guest capabilities. A pseudonymous security replay fence remains for 24 hours. Files selected from another provider and copies exported by the user remain under that user or provider's control. Access-restricted operational logs and backup copies may remain until their normal service lifecycle expires and are not used to restore the deleted account, except when preservation is required for security, fraud prevention, or law.

Account access ends as soon as a deletion request is accepted. MusicMute keeps the account in a 15-day recovery period. Permanent active-system cleanup starts automatically when that period ends and is retried until it completes.

Use the account deletion page to request deletion outside the app or review the in-app process. The page explains the data removed, the exact recovery period, and any limited retention.

Chrome Web Store Limited Use

MusicMute Local's use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used and transferred only for the disclosed voice playback, processing, and account Library features, and for the policy's permitted service purposes.

User data is not used or transferred for personalized, retargeted, or interest-based advertising; it is not sold or transferred to data brokers and is not used for creditworthiness or lending. Human access to user data is limited to the policy's permitted situations, such as your affirmative agreement to specific support access, security investigations, compliance with law, or permitted internal use of aggregated and anonymized data.

Policy changes

Material changes will be published at this same URL with a new last-updated date. This notice describes current data handling; it does not itself obtain consent for new or unrelated uses. Where a change requires additional notice or affirmative consent under applicable law or store policy, MusicMute must provide that notice and obtain that consent before the new use.