In October 2018, we announced updates to our Permissions policy that will limit which apps are allowed to request Call Log and SMS permissions. This is the third and final reminder to let you know that this policy may impact one or more of your apps.
Starting January 9, 2019, only an app that has been selected as a user’s default app for making calls or text messages, or whose core functionality is approved for one of the exception use cases, will be able to access Call Log or SMS permissions.
Below, we’ve included next steps you should take, along with a sample of apps from your catalog which may not meet the requirements for permission requests.
Action required
Read through the Permissions policy and the Play Console Help Center article (which describes intended uses, exceptions, invalid uses, and alternative options for use of Call Log or SMS permissions) to determine which of the following options apply to your affected app(s):
Option 1) If your app does not require access to Call Log or SMS permissions: Remove the specified permissions from your app’s manifest, or migrate to an alternative implementation by January 9, 2019. If you require additional time to make these changes, you can submit a Permissions Declaration Form; eligible apps may be granted an extension until March 9, 2019.
Option 2) If your app is a default handler, or you believe your app qualifies for an exception: Submit a request using the Permissions Declaration Formby January 9, 2019. We are currently reviewing submissions and will respond to your request. Note: You do not need to make changes to your app in order to be eligible to submit a request.
Please note that the extension mentioned above is applicable only to currently published apps. If you wish to publish a new version of your app, it must be compliant with our Permissions policy. Make sure that your app is otherwise compliant with other Developer Program Policies to prevent your app from being removed.
We appreciate your willingness to partner with us as we make these improvements to better protect users.
Affected apps
Affected apps and permissions are listed below, up to 20; if you have additional apps, please ensure that they are also compliant with the Permissions policy.
