

That GitHub discussion seems to confirm it. The developers shutting down their extension immediately afterwards too just reeks of suspicious activity.
The version number for the extension in my browser (1.8.8) doesn’t match the latest release that’s visible on this otherwise public repository (1.8.0)
So presumably at some point “someone” “somewhere” modified or added some files to the source code of this extension out of public view… and then “somehow” got a hold of this dev account password or whatever which was subsequently used to surreptitiously push it to the chrome webstore…
This is genuinely disturbing.
A developer was planning on sneaking data collection into a product through a sketchy terms of service. That on its own should keep the app out of any marketplace.
The subsequent claim that the developer simply forgot to include this in the TOS doesn’t get any extra sympathy from me. Funny the apology only appeared after the developer got caught with their pants down, isn’t it?