Summary
The store requires a visible account deletion or account cancellation path, and the app's current UX or policy does not meet that expectation.
China Android app stores App Review issue
The store requires a visible account deletion or account cancellation path, and the app's current UX or policy does not meet that expectation.
Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.
The store requires a visible account deletion or account cancellation path, and the app's current UX or policy does not meet that expectation.
Stores increasingly expect users to find a way to cancel accounts and request deletion without excessive friction.
This issue often overlaps with privacy policy and data-retention disclosures.
A missing deletion path can block approval even if the rest of the policy pack looks complete.
Add a visible account deletion or cancellation flow in settings or account management.
Update policy sections covering deletion timelines, retention exceptions, and support channels.
Provide reviewer notes explaining where the deletion path is located and what happens after the request.
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.
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.
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.