Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reminder: privacy policies on Extensions #236

Closed
12 tasks done
Thorin-Oakenpants opened this issue Sep 14, 2017 · 11 comments
Closed
12 tasks done

reminder: privacy policies on Extensions #236

Thorin-Oakenpants opened this issue Sep 14, 2017 · 11 comments
Assignees
Labels

Comments

@Thorin-Oakenpants
Copy link
Contributor

Thorin-Oakenpants commented Sep 14, 2017

as of current Wiki page (in future all additions require policy vetting) - checklist to find privacy policy links

Extensions

not my problem or my job

don't care also obsolete at ESR52 EOL

  • Cookie Controller
  • Live HTTP Headers - earthlng clone
  • No Redirect (Clone) - earthlng clone
  • No Resource URI Leak (Clone) - earthlng clone
  • Self-Destructing Cookies

---original post

this is a reminder for Thorin to do something about privacy policies for recommended addons - both in our wiki (I think we're good - eg gorhill, C-AD, Decentraleyes, etc - well known respected devs IMO, but we will check anyway), and those in the sticky

for example: here is an extension https://addons.mozilla.org/en-US/firefox/addon/popup_blocker/ .. 4th page of 57 compatible extensions sorted by popularity Now read the privacy policy - https://www.popup-blocker.com/privacypolicy.html How can 25K users be so naive

PS: Not that I think we need any sort of popup blocker

  1. dom.popup_allowed_events", "click dblclick" (this does it for me)
  2. overkill: breaks lots so u need to set quite a few exceptions: set uBo to use no-popups: * true (that's the icon of two pages, bottom left in your doorhanger) - it will not cover ALL popup events AFAIK. It is better to allow all and deny troublesome sites

That fixes 99.9% of them. I've yet to see one to be honest

@Thorin-Oakenpants
Copy link
Contributor Author

Thorin-Oakenpants commented Sep 15, 2017

Note sure how to do this for the Wiki, I do not want it to become too "busy". Note if you mouse over PP you get alt text Privacy Policy. Asterix is there to break the color. Does this look OK?

Edit: I know, I'll use a ✔ symbol, and we'll just put up privacy policy links for those we can find - the tick meaning it's all good re privacy. Just need to find all the links now

@Atavic
Copy link

Atavic commented Sep 15, 2017

@Atavic
Copy link

Atavic commented Sep 16, 2017

Yes, it falls back on %LOCALE%

@Atavic
Copy link

Atavic commented Sep 16, 2017

Just do that.

@Thorin-Oakenpants
Copy link
Contributor Author

these requests make me feel like a spammer :-(

@kkapsner
Copy link

Didn't feel like spam on the other side.

@Thorin-Oakenpants
Copy link
Contributor Author

Closing: have added privacy policy links where they exist, having one is up to the extension owners

@Atavic
Copy link

Atavic commented Oct 2, 2017

@rekixex Been asked here.

@Thorin-Oakenpants
Copy link
Contributor Author

in future all additions require policy vetting

It seems that Skip Redirect doesn't have a privacy policy - I may be wrong, just did a quick search.

I also said

Closing: have added privacy policy links where they exist, having one is up to the extension owners

I am no longer interested in chasing anyone up. I will check for a privacy policy when I add an item, but that's it.

@Atavic
Copy link

Atavic commented Oct 6, 2017

Skip Redirect: This extension does not collect or send data of any kind to third parties

@Atavic
Copy link

Atavic commented Jun 13, 2018

There's a bugzilla discussion about privacy labels for addons/webextensions:

“privacy”: [ “sendsUsageDataToThirdParty”, “sendsUsageDataToDeveloper”,
“sendsBrowsingData”, “sendsProfileData”, “collectsUserData” ]

Also related: pyllyukko/user.js#365

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants