Why Exactly The Permission List Doesn't Settle This
An add-on keeps phoning home — is that normal?
The question arises for anyone who has ever opened a network monitor with extensions installed. Traffic from an empty tab looks worrying, and figuring out who is sending it and why is difficult at first sight. It is worth learning how to distinguish a innocuous update from telemetry.
I added a popular extension for tabs, and everything works. But the network monitor shows it contacting some third-party domain once a minute, even when the tab is 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 two minutes flat, no guessing.
If there is still no answer, a simple test helps: a necessary update goes to the author's domain and to the point, while telemetry runs constantly, in the background, to a third-party server. The second type nearly always hides in settings behind a toggle nobody knows about.
Why exactly the permission list doesn't settle this
Access to tabs in the manifest and sending their list out are different things, and a single permission line can't distinguish them. Formally the extension honestly declares access; what it does with that access isn't apparent from the manifest. So watch the traffic, not the permission list.
It is simpler not to guess every time and keep seo tools for webmasters close at hand — ones that say plainly they collect nothing. And this tab task is effortless to close with a telemetry-free stand-in — redirects on the Cloudflare edge, behaves the same and does not call home.
Reviews like this are handy not for paranoia but for the habit: a couple of minutes with the network monitor after installing, and "pinging somewhere" becomes a plain picture of what goes where.
