My extension, Flickr Fixr, is a simple extension with the solely purpose to make Flickr a better place to be. It of course runs on Flickr’s main domain (flickr.com), but also on flickr.net which hosts two flickr blogs. The extension is basically a content-script altering UI and sometimes adding information information from other pages on flickr.com or from the Flickr API at api.flickr.com (all API calls are currently “public unsigned”).
Flickr Fixr does not collect data and does not use data in any other ways than nescesarry for the extensions features and functionallity. The only purpose of the extension is to make it a better experience to be on Flickr.
Flickr Fixr does in current version not communicate any data at all outside the flickr domains (flickr.com and flickr.net). If some future new feature of Flickr Fixr will require data to be sent outside the flickr domains, It will be an opt-in (default disabled) feature, and I will make sure to state how data is used before you eventually enable it.
which is kind of the other way around than I was thinking. I guess my basis assumption was that extensions was running in a sandbox, thus it was not an interesting angle looking at transfering information found on the browser/system. But of course, depending on granted permissions, extensions does have access to some information on user, users system (OS/browser) or setup available.