Permission requests should make sense to users. You may only request permissions that are necessary to implement current features or services in your app that are promoted in your Play Store listing. You may not use permissions that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. Personal or sensitive data accessed through permissions may never be sold.
Request permissions to access data in context (via
incremental auth), so that users understand why your app is requesting
the permission. Use the data only for purposes that the user has
consented to. If you later wish to use the data for other purposes, you
must ask users and make sure they affirmatively agree to the additional
uses.
Apps lacking default SMS, Phone, or
Assistant handler capability may not declare use of the above
permissions in the manifest. This includes placeholder text in the
manifest. Additionally, apps must be actively registered as the default
SMS, Phone, or Assistant handler before prompting users to accept any of
the above permissions and must immediately stop using the permission
when they’re no longer the default handler. The permitted uses and
exceptions are available on this Help Center page.
pps may not access data protected by location permissions (e.g., ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_BACKGROUND_LOCATION) after it is no longer necessary to deliver current features or services in your app.
| Call Log permission group (e.g. READ_CALL_LOG, WRITE_CALL_LOG, PROCESS_OUTGOING_CALLS) | It must be actively registered as the default Phone or Assistant handler on the device. |
| SMS permission group (e.g. READ_SMS, SEND_SMS, WRITE_SMS, RECEIVE_SMS, RECEIVE_WAP_PUSH, RECEIVE_MMS) | It must be actively registered as the default SMS or Assistant handler on the device. |
Comments
Post a Comment