I'm sure we're all up-to-date with this, but just in case...
There is a planned further purge and enforcement of the need to have a Privacy Policy in place or to remove permissions that are un-necessary.
http://www.trustedreviews.com/news/google-plots-play-store-privacy-purge
This will bode well for legitimate Devs - the dross will be removed and therefore just our quality Apps will be left!
I'm sure they've mentioned this before - but it seems to be for real this time.
"According to security company Sophos, developers have been receiving emails warning them that their apps need to comply by March 15 this year, or will face administrative consequences, which would be pretty disastrous for any affected apps."
OR
"Of course, the alternative to complying with the policy before mid-March is removing all the aspects of your app that collect personal data. In that instance, the privacy policy requirement won't be enforced."
I had an App which used a fairly old method of accessing the device id using the Phone lib - this then meant PHONE_STATE was included in the permissions and it was flagged as such and I received an email from Google about it...
There is a planned further purge and enforcement of the need to have a Privacy Policy in place or to remove permissions that are un-necessary.
http://www.trustedreviews.com/news/google-plots-play-store-privacy-purge
This will bode well for legitimate Devs - the dross will be removed and therefore just our quality Apps will be left!
I'm sure they've mentioned this before - but it seems to be for real this time.
"According to security company Sophos, developers have been receiving emails warning them that their apps need to comply by March 15 this year, or will face administrative consequences, which would be pretty disastrous for any affected apps."
OR
"Of course, the alternative to complying with the policy before mid-March is removing all the aspects of your app that collect personal data. In that instance, the privacy policy requirement won't be enforced."
I had an App which used a fairly old method of accessing the device id using the Phone lib - this then meant PHONE_STATE was included in the permissions and it was flagged as such and I received an email from Google about it...
