|
|
|
|
|
|
by mattmillr
5148 days ago
|
|
|
Short of reading the source code for the plugin, you can't know for sure. That's why Chrome just warns you that it can access your browsing activity, that's all you can know. You have to decide whether or not you trust the plugin author with that access. Assuming (a) the plugin can access your data and (b) the plugin can communicate with some external system, there is no way* to either prohibit the plugin from sending your data to that external system or universally detect that it is doign it. * No technical way. Of course you can use contracts, TOS, & other legal methods. |
|
|