Page:Note-by-Chair-and-selected-documents-ordered-from-Six4Three.pdf/11

 but rather build their own ecosystem at the expense of our users, other developers and, or course, us. That is something that we will not allow.’

4. Android

From email dated 4 February 2015

Michael LeBeau – ‘He guys, as you know all the growth team is planning on shipping a permissions update on Android at the end of this month. They are going to include the ‘read call log’ permission, which will trigger the Android permissions dialog on update, requiring users to accept the update. They will then provide an in-app opt in NUX for a feature that lets you continuously upload your SMS and call log history to Facebook to be used for improving things like PYMK, coefficient calculation, feed ranking etc. This is a pretty highrisk thing to do from a PR perspective but it appears that the growth team will charge ahead and do it.’

Yul Kwon – ‘The Growth team is now exploring a path where we only request Read Call Log permission, and hold off on requesting any other permissions for now.

‘Based on their initial testing, it seems this would allow us to upgrade users without subjecting them to an Android permissions dialog at all.

‘It would still be a breaking change, so users would have to click to upgrade, but no permissions dialog screen.’

Email from Matt Scutari, Manager Privacy and Public Policy, Facebook

15 November 2013

‘Matt has been working with the privacy PM, PMM and Legal to understand privacy risks associated with several Android permissions that will go out in the next release, including permissions associated with reading call logs and SMS’

‘Matt is providing policy feedback on a Mark Z request that Product explore the possibility of making the Only Me audience setting unsticky. The goal of this change would be to help users avoid inadvertently posting to the Only Me audience. We are encouraging Product to