Privacy
SlopMute decides what to hide inside your browser. It has no account and no way to see what you watch. This page says exactly what is stored, sent, and where.
Last updated 9 September 2026.
Everything below happens on your device, in the browser tab you already have open.
SlopMute reads the text YouTube has already put on the page: video titles, channel names, badges and labels, visible metadata and accessibility text. It matches that against rules bundled inside the extension. That matching happens in your browser. Nothing about the videos you see, search for, or watch is sent anywhere for scoring.
Your browsing history and page content are never sent to an AI service, ours or anyone else’s. There is no model call, no API key, and no inference server. The rules are plain pattern matching shipped in the extension package.
The extension has no sign-in, no profile and no licence check. Install it and it works. Filtering does not create an identity or send us your YouTube activity.
The extension uses your browser’s local extension storage: chrome.storage.localon Chromium browsers and browser.storage.local on Firefox. That storage stays on your own device. It is not synced to an account by SlopMute and it is not transmitted.
Whether SlopMute is on, which of the three categories are enabled, each category’s sensitivity and action, where filtering runs, Shorts and watch-page behaviour, and whether you have completed onboarding.
Channels you have muted and channels you have allowed, stored against the channel ID or handle YouTube exposes on the card. Videos you have permanently allowed, stored by video ID.
When you tell SlopMute it got something wrong, that choice is stored by video ID and category so the same video is not filtered again, and so a rule you corrected can be weighted slightly differently for you. It does not train a model and it is not sent anywhere.
Any custom phrases or advanced rules you create, including ones you import from a file. Exports are written to your device by your browser.
Counts only: how many videos were hidden, warnings shown, Shorts skipped, channels muted, and which built-in rules matched most often. To stop the same video being counted twice, SlopMute keeps short-lived bookkeeping records for eight days using the date, video ID, category and area. Those records hold no titles and no channel names, and delete themselves. Nothing here is analytics: there is nowhere for it to go.
The extension periodically downloads a small JSON rules document from SlopMute. It contains phrases used by the local matcher; the request does not include page text, video details, settings or an account identifier. The optional thumbnail pipeline lab, which is off by default, fetches thumbnail images directly from YouTube’s image servers. Those images are not sent to us.
You can remove all of it at any time. Reset everything in full settings clears stored data, and uninstalling the extension removes its local storage with it.
This website cannot inspect YouTube pages, extension settings, filtering history or local storage. Every build fetches the SlopMute rules document. The Chrome build also contacts SlopMute when you send feedback or use the optional discovery question; the Firefox build instead opens your own mail app for answers and sends nothing itself.
The compact feedback box sends only the words you type and the fixed label “extension quick menu”. It does not attach the page URL, video title, channel, diagnostics, settings, account details or browsing history. The note is delivered to our inbox through Resend so we can read and act on it. We use it only to respond to feedback and improve SlopMute, never for advertising or sale. You can email us to ask for a submitted note to be deleted.
After setup, you can optionally tell us how you heard about SlopMute. In Chrome, choosing a source sends that choice and a fixed onboarding label to the same inbox through Resend. Clicking “Skip this question” sends only a fixed “Skipped” tally and the onboarding label. These messages help us estimate how people discover SlopMute and how many skip the question. They contain no browsing history, settings, answer text beyond the selected source, or persistent user identifier. In Firefox, choosing a source prepares an email draft in your own mail app; you choose whether to send it, and your mail app includes your email address if you do. Skipping in Firefox sends nothing.
SlopMute’s use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.
The website uses Vercel Analytics to understand aggregate page visits and Chrome Web Store link clicks. It does not set tracking cookies, and campaign parameters such as gclid and UTM values may be attached to the aggregate store-click event. This website measurement is separate from the extension.
The Google Ads tag is disabled by default and is not downloaded until you choose “Allow measurement”. If allowed, Google may use advertising cookies and receive the page URL, campaign parameters, device and network information needed to measure visits from ads. Personalized advertising remains disabled. You can reopen Privacy choices at any time and withdraw consent. The tag runs only on this website: it cannot read YouTube pages, filtering history, extension settings or any other extension data.
SlopMute has launched, so the site no longer shows a launch form. Addresses given before launch were sent to Resend, the email provider we use, and are stored in their contact list. That was the only personal data submitted directly to SlopMute before feedback was added. It was given deliberately and is never combined with extension settings or YouTube activity.
Every email we send includes an unsubscribe link. You can also email us and we will remove you.
Email hello@slopmute.com. If anything on this page stops matching what the software does, the page is the thing that is wrong. Tell us and we will correct it.
Chrome Web Store