Why Exactly The Permission List Does Not Settle This

An add-on keeps reaching out to its server — is that something to worry about?


The question arises for anyone who has opened a network monitor with extensions installed. Traffic from an empty tab looks alarming, and working out who is sending it and why is tricky at first glance. It is worth understanding how to distinguish a innocuous update from telemetry.


I added a popular extension for tabs, and everything appears to work. But the network monitor shows it pinging some third-party domain once a minute, even when the tab sits idle. The description does not mention it. Is this tracking, or am I overthinking it?


The first step is to separate yours from theirs: turn off all extensions in one go and check whether the background noise disappears. If it goes quiet, the source is one of them, and you switch each back on individually until the traffic reappears. That pins down the culprit in a couple of minutes, no guessing.


Why exactly the permission list does not settle this


Access to tabs in the manifest and passing their list outward are different things, and a single permission line cannot tell them apart. Formally the extension honestly declares access; what it does with that access isn't visible from the manifest. So watch the traffic, not the permission list.



It is easier not to guess every time and keep webmaster tools handy — ones that state plainly they collect nothing. And this tab task is quick to close with a telemetry-free swap — cookie manager for developers, behaves the same and doesn't call home.



Reviews of this sort are handy not for paranoia but for the habit: a few minutes with the network monitor after installing, and "pinging somewhere" turns into a plain picture of what goes where.