Play Policy Checker
Will Google PlayReject Your App?Know Before You Submit.
Upload an APK or pick your Play listing. We crawl the app, scan the build, and email you every blocker.
Crawl
Login
Permission
Account
Score
62
18 of 22 rules ran
- BlockerPrivacy link missing on the account screen
- HighNo account deletion after login
- HighTarget API one version behind
What runs
Four passes. One report.
01
You send the app
An APK, or a published Play listing. We install it on an emulator and pull the build.
02
The crawler walks it
Login, permission prompts, and account deletion. Screenshots and UI text are saved in order.
03
The build is scanned
Manifest, permissions, target API, SDKs, libraries, and the network security config.
04
The report arrives
Status, score, coverage, and every finding with the policy behind it. In your inbox.
The status
A gate, with the reason beside it.
BLOCKED
One gated failure. The score cannot lift it.
NEEDS REVIEW
A content model flagged something. A person confirms it before it counts against you.
READY
No gated failure, and no model flag still open.
The score sits next to coverage. 18 of 22 means four applicable rules did not run, and the number does not pretend they did.
Blocker
Privacy policy link, inside the app
A link that exists only on the store listing does not count. The report names the screen where it is missing.
High
A way to delete the account
If the app creates an account, Play expects a deletion path. The crawler looks for it after login.
High
Target API, current enough
One version behind the requirement fails before a reviewer opens the app. The scan reads it from the manifest.
The evidence
130+ rules. 24 are blockers.
The catalog is the Play policy set. A report only scores the rules that had evidence.
The build
- Permissions declared against permissions used
- Target API level
- SDKs and libraries
- Network security config
The crawl
- Privacy link on a real screen
- Account deletion after login
- Permission prompts
- UI text and screenshots, in order
The listing
- Title and description
- Graphics against what the app shows
- Content that has to match the rating
- Metadata that disagrees with the build
FAQ
Before you send the app
- What do you need from me?
- An APK, or the app's Play listing, and an email. We install it on an Android emulator, crawl it, scan the build, and send the report to that inbox.
- What is in the report?
- A status of BLOCKED, NEEDS REVIEW, or READY. A score. How many of the applicable rules actually ran. Each finding names the policy behind it and what to fix first.
- Does READY mean Play will approve it?
- READY means no gated failure and no model flag still open. Google Play makes the approval decision. QApilot is not affiliated with Google.