>> Vendor name CraniumCafe.com >> Point of contact Michael Gorham >> Site URLs https://*.craniumcafe.com >> Does the application provide users with notice and control? https://www.craniumcafe.com/privacy-policy/ >> Have you seen and agree with the Developer Screen Sharing Submission policy? Yes >> Does the usage comply with the Developer Screen Sharing Submission Policy guidelines? Yes
the privacy statement and how info is used is not aligned with our policies - basically capturing all private info and sharing at will. will respond more later.
Priority: -- → P5
agreed ... that was a pretty boiler plate privacy statement we used. we're very eager to get our domain whitelisted. would it help to base our privacy statement off of Mozilla's example? E.g., https://www.mozilla.org/en-US/privacy/
Hi, I am resolving this bug as "won't fix", since starting Firefox 52 on April 18th the Screensharing whitelist is no longer needed to share your screen or windows. Please let us know if you find any problems! Much of this work was front-end, UX/UI changes, including support to let the UI know what streams are "scary" to share (see bug 1284910). See the meta bug 1127522 for all the work that went into this. Please read Jan-Ivar's blog post explaining the risks that users need to know about when sharing their screen or windows: https://blog.mozilla.org/webrtc/share-browser-windows-entire-screen-sites-trust/. The new UI permission dialog for screensharing links to a SUMO article with similar content to Jan-Ivar's post, but our SUMO team tailored it to a less technical user.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.