It would require collecting this data in the first place. Since it's not related to the primary functionality of the extension, it would require me to declare it in the privacy policy and extension stores. Probably needs additional access permissions as well. It's much easier to just not collect anything at all.

If it was up-front and clear in scope and intent, I would have much fewer problems with it. But, I don't think I've ever some across software that clearly and explicit listed the scope of what will be tracked (and how), clearly stated that it was intended to be sold, and gathered clear and explicit consent from the user.

It will inevitably turn out later, when the data has already leaked, that due to an unfortunate oversight or bug or misconfiguration it wasn't truly anonymized after all.