As someone who hangs out in /r/selfhosting a fair amount, I get what you mean. But I also see it used frequently in the vernacular to distinguish between a managed/hosted web service (which may simply be a web "application" as far as the user is concerned), and software you can run on your own machine. To extend your analogy, running Word locally is in some sense "selfhosted" as opposed to using Word Online in a browser. (Though I'd argue that this isn't a great example because of how much the Word desktop app increasingly uses cloud services in order to work.)
IMO, selfhosting here was descriptive in that the Chrome extension is storing all data and generating all recommendations locally, without the use of a managed service that would presumably be storing all of my history in someone's cloud instance. (I'm sure you're a great person, OP, but I wouldn't want to give you my entire browser history.)
Yes, it's shipped in the Chrome web store, so OP could theoretically ship different code than what's showing in the open-source repo, but you actually _can_ selfhost even "further" by building the extension yourself (even if installing unsigned extensions in Chrome is harder than ever, I think it's still possible, and certainly Edge still allows it via Developer Mode).