Hi Hannes, Thanks for writing! Note that the privacy policy says that bug report submission will either be manual or opt-in to automatic submission. HTTPS Everywhere doesn't implement any bug report submission, and so doesn't send any browsing data to remote servers (except through SSL Observatory, which requires specific opt-in). If we were to implement automatic bug report submission, you can be sure that it would respect the privacy policy and require specific consent.
On 11/11/2016 06:56 AM, Hannes Jakschitsch via HTTPS-Everywhere wrote: > Dear eff, first of all thanks for all your contributions. > I am looking for details on the privacy policy of the https everywhere > add-on. > The policy linked by addons.mozilla.org > > https://www.eff.org/code/privacy/policy > > There it says: > > EFF software and technology projects may give you the option to submit > bug reports to us, either manually or (if you opt-in) automatically, > such as when an error occurs. For example, if you disable HTTPS > Everywhere on a particular site, that may be indicative of bugs in the > ruleset for that site. > > That statement says when https everywhere is disabled on a site this > information will be sent to EFF. > Is there any detailed description on information collected by the add-on? > The statement said disabling https everywhere is just an example. > > Does it also submit the browsing history to remove servers as the WOT > addon did? > ( see here https://news.ycombinator.com/item?id=12918191 ) > > Thanks, Hannes > > > > > > > _______________________________________________ > HTTPS-Everywhere mailing list > [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere
_______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
