Requests for permission and APIs that access sensitive information should make sense to users. You may only request permissions and APIs that access sensitive information that are necessary to implement critical current features or services in your app that are promoted in your Google Play listing. You may not use permissions or APIs that access sensitive information that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. Personal or sensitive data accessed through permissions or APIs that access sensitive information may never be sold nor shared for a purpose facilitating sale.
Request permissions and APIs that access sensitive information to access data in context (via incremental requests), 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.
2 Are you asking help to write down the Policy? if yes then
Here’s a clear policy declaration you can use/adapt for your SMS/Call Log related extension or app,
Our app requests access to SMS and/or Call Log permissions strictly for implementing core features that are clearly described in our Play Store listing.
Purpose of Use,
These permissions are required only for [ insert your real feature here, e.g. “allowing users to send messages directly from the app to their contacts” or “displaying call history within the app for user convenience”].
We do not use them for any unrelated or undisclosed purposes.
User Consent,
Permissions are requested in context, at the time they are needed, so that users clearly understand why the app is asking for access.
Data Handling,
Data obtained via SMS/Call Log permissions is used only within the app to provide the stated features.
We do not sell, share, or transfer this data for advertising or resale.
Data is not stored or processed beyond what is necessary to enable the feature.
Future Uses,
If at any point we wish to use this data for additional purposes, users will be asked for explicit, informed consent before any new usage.
This wording shows Google that your app complies with the Sensitive Permissions Policy,
You declare why you need the permissions.
You limit them only to features shown in your Play Store listing.
You explain how you handle user data.
If your answer is not in option 2 then ask a clear question
Your app has been rejected and wasn’t published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.
### Issue found: Requested permissions do not match core functionality of the app
You declared that your permission use case is the core functionality of your app. However, after review, we found that your app does not match the declared use case(s). Learn more about permitted uses and exceptions.
Please either make changes to your app so that it meets the requirements of the declared core functionality or select a use case that matches your app’s functionality.
Your store listing information does not match the core functionality for your declared use case.
Default SMS handler (and any other core functionality usage while default handler)Default Phone handler (and any other core functionality usage while default handler)
Requests for permission and APIs that access sensitive information should make sense to users. You may only request permissions and APIs that access sensitive information that are necessary to implement critical current features or services in your app that are promoted in your Google Play listing. You may not use permissions or APIs that access sensitive information that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. Personal or sensitive data accessed through permissions or APIs that access sensitive information may never be sold nor shared for a purpose facilitating sale.
Request permissions and APIs that access sensitive information to access data in context (via incremental requests), 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.