Google Play enforcement process and actions policy: fixes and checks

Read the action named in the notice before submitting anything. Rejection, removal, suspension, and account restriction have different consequences and different routes to resolution.

Rejection

The submitted app or update isn’t published. For a rejected update, the previously published version normally remains available. Fix all identified violations before resubmitting; the rejection itself doesn’t count against account standing.

Removal

The app and prior versions are unavailable for download. A compliant update can restore the listing after approval. Billing features may be unavailable while the app is removed. Repeated removals can lead to suspension.

Suspension

A suspension removes the app and counts as a strike against the developer account. You can’t continue using the suspended APK or bundle. Follow the notice’s appeal instructions if you believe the finding is wrong; don’t treat suspension as an ordinary rejected update.

Limited visibility and limited regions

Limited visibility restricts discovery while leaving the listing accessible by direct link. Limited regions restrict where users can find and download the app. Previously installed users can continue using a region-limited app but no longer receive updates under the policy’s described action. Read the notice for the affected scope.

Restricted or terminated account

A restricted account removes the catalog but still allows Play Console access to provide information and correct issues. Apps can be republished after the violations are resolved.

Termination removes the catalog and affects related accounts. Creating another account to bypass termination is prohibited and can result in that account being terminated too.

How to respond or appeal

Match each finding to a concrete fix or evidence that the decision is mistaken. Include the app identifier, affected version, reviewer steps, and relevant screenshots. Use the appeal route in the notice for disputed enforcement.

Check shared code and other apps for the same issue: a notice may not list every violation. Avoid repeatedly submitting unchanged builds. For a practical response checklist, use our Google Play rejection guide.