Why Exactly The Permission List Does Not Resolve This
An add-on keeps reaching out to its server — is that expected?
The question comes up for anyone who has opened a network monitor with extensions installed. Traffic from an empty tab seems unsettling, and working out who is sending it and why is hard at first glance. It is worth understanding how to separate a harmless update from telemetry.
I set up a popular extension for tabs, and everything appears to work. But the network monitor shows it hitting some third-party domain once a minute, even when the tab stays idle. The description does not mention it. Is this tracking, or am I reading too much into it?
The first step is to separate yours from theirs: turn off all extensions at once and see whether the background noise disappears. If it goes quiet, the source is one of them, and you switch each back on in turn until the traffic reappears. That finds the culprit in two minutes flat, no guesswork.
Why exactly the permission list does not resolve this
Access to tabs in the manifest and sending their list outward are different things, and a lone permission line can't distinguish them. On paper the extension honestly declares access; what it does with that access is not visible from the manifest. So watch the traffic, not the permission list.
It is easier not to guess every time and keep desktop utilities for sites handy — ones that say plainly they gather nothing. And this tab task is painless to close with a telemetry-free replacement — DMCA complaints against domains, works the same and does not 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" becomes a plain picture of what goes where.