Google Play App Review issue

Google Play SMS and call log rejected

Google rejected the app because SMS or call log access is restricted and the declared use case or disclosure package is not sufficient.

google play sms call log rejectedsms permission rejected google playcall log permission rejected play

Fix Google Play review issues before the next submission

Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.

Run compliance check Generate policy Reject Fix AI Assistant Book demo / Start free Generate terms

Summary

Google rejected the app because SMS or call log access is restricted and the declared use case or disclosure package is not sufficient.

What this means

SMS and call log permissions are tightly restricted and usually allowed only for narrow core-function cases.

Google expects strong justification, clear user benefit, and accurate store and in-app disclosure.

Many teams are better off removing the permission than trying to defend a borderline use case.

Common causes

The app requests SMS or call log access for convenience rather than a clearly permitted core function.
Policy and disclosure text are vague about how message or call data is accessed and retained.
The relevant declaration form is incomplete or inconsistent with the app flow.

Step-by-step fix

Step 1
Reassess whether SMS or call log access is truly required for the shipped feature set.
Step 2
If required, rewrite disclosures and policy sections to explain the exact permitted use case and user control.
Step 3
If not required, remove the permission and clean up every related reference in forms and policy copy.

What to update

Manifest permissions
Restricted-permission declaration
Privacy Policy
Prominent disclosure UI

How LogicSpring helps

Use LogicSpring to coordinate the removal or justification workflow across manifest, policy, and submission forms.
Precheck helps catch references that teams often forget after removing restricted permissions.
This shortens the loop when a hotfix release needs to go out quickly.

Run compliance check Generate policy Reject Fix AI Assistant Book demo / Start free Generate terms

FAQ

Can I resubmit to Google Play without changing the binary?

Only for pure listing or form corrections. If the shipped build still requests the wrong permission, bundles the wrong SDK, or behaves inconsistently, resubmitting the same build is risky.

What evidence should I prepare before resubmitting?

Prepare the updated public policy URL, the exact store fields you changed, screenshots for permission or disclosure flows where relevant, and a short reviewer note explaining what changed and why it now matches the app.

Should the privacy policy, store form, and in-app disclosure all match?

Yes. Review teams compare these surfaces together. If one says you collect or disclose something and another says you do not, the mismatch itself often becomes the next rejection.