For a year and a half this stayed on my own machine, because publishing meant paperwork. In July 2026 I did the paperwork, and it went live on the Chrome Web Store.

The part I actually care about is what it asks for. The extension requests three things: local storage, the active tab, and youtube.com. It makes zero network requests, so there is no server, no analytics, and no third party anywhere in it. Everything happens on your own machine, and it never sees a page that is not a YouTube playlist.

I wrote the privacy policy myself and then checked it line by line against the source, which is about six kilobytes of JavaScript, because a privacy policy you cannot verify against the code is only a promise. A reviewer can read the entire extension in a few minutes and confirm every claim in it.

That instinct is what I would point at rather than the feature. A tool that fixes a small annoyance should never be the reason someone takes on risk, and the way to guarantee that is to ask for less rather than to promise more.