Google Play Developer Policies: Maintain a Product-Level Compliance Register
A useful Google Play policy process ties each requirement to a real app feature and an accountable owner. A long copied checklist becomes unreliable when.
Google Play & compliance
Google Play Policy Checker
Check your app against common Google Play Developer Program policies before you submit for review.
Google Play Policy Checker is part of APKLint, an online toolkit for inspecting Android APK files. Check your app against common Google Play Developer Program policies before you submit for review. Work through the checklist on this page — there is nothing to upload; it is a guided review.
- Request only needed permissionsEvery permission maps to a visible feature; remove anything unused.
- Sensitive/restricted permissions justifiedSMS, Call Log, Accessibility, All-files, and location have an approved, disclosed use.
- Data Safety form accurateIt reflects what your code AND your SDKs collect, share, and how it's secured.
- Privacy policy linkedA valid, reachable privacy-policy URL is set in the listing and in-app where required.
- Account deletion pathIf you offer accounts, provide in-app and web data/account deletion.
- Content rating correctComplete the IARC questionnaire honestly; rating matches actual content.
- Ads complyAds are family-safe where needed, not deceptive, and don't mimic system UI.
- Metadata is honestTitle, icon, screenshots, and description match real functionality; no keyword spam.
- No impersonationYou don't copy another brand's name, icon, or assets.
- Target API OKMeets Google Play's current target-API requirement for your release track and form factor — verify the current threshold in Play Console.
- Background locationBackground location use is justified, disclosed, and approved if required.
- Financial/health/sensitive rulesIf applicable, you meet the extra policies for those categories.
- Foreground services declaredEach foreground service has a valid type and user-facing justification.
- Testing & functionalityNo crashes, broken links, or placeholder content at review time.
Free reference. No upload and no account needed — just open it and work through each point.
About Google Play Policy Checker
Check your app against common Google Play Developer Program policies before you submit for review.
Google Play Policy Checker is part of APKLint’s google play & compliance toolkit — Prep your listing, policies, and release for the store. It’s free to use and needs no account.
It’s a free reference — there’s nothing to upload and no account needed.
When to use Google Play Policy Checker
- Best for
- Checking your app against common Google Play Developer Program policies before you submit.
- Not the right tool for
- Not the full policy text and not an automated checker.
- What you get back
- A walkthrough of frequently-hit developer policy areas to self-assess.
- How it differs from related APKLint tools
- It is the general policy companion; the Families tool is the kids-specific subset and the Rejection tool is outcome-focused.
- Limitations
- A static reference, last reviewed 22 September 2026; verify current policy in Play Console.
How to use Google Play Policy Checker
- Open the checklist — Everything you need to review is laid out in plain language.
- Work through each item — Check your app against every point on the list.
- Fix what's flagged — Update your manifest, build, or listing where needed.
- Re-verify before release — Run through it once more before you publish.
Native code: 64-bit and 16 KB page-size support
If your app — or any SDK it bundles — ships native code (.so libraries), Google Play adds two requirements on top of the target-API rule. 64-bit support: every supported native architecture must comply with Google Play's 64-bit requirements — for example, provide an arm64-v8a library when you ship the corresponding ARM native code (you don't need to add ABIs you don't already build for). 16 KB memory page-size support: apps targeting Android 15 (API 35) and higher must support 16 KB page sizes on 64-bit devices, which means rebuilding the affected libraries 16 KB-aligned. Apps written purely in Java/Kotlin qualify by default. From February 1, 2027, updates that don't support 16 KB page sizes can't be released.
Form-factor deadlines are earlier: Android TV has required 64-bit + 16 KB since August 1, 2026, and Wear OS requires them from September 15, 2026 — these apply even though those form factors can still target a lower API level, so don't assume an API 34 TV app is exempt. Check the Play Console compatibility warnings and confirm the current deadlines before your next release.
Why use APKLint
Always free
Every tool is free with no login and no paywall. Reasonable file and input limits keep the free service stable.
No on-page ad banners
A clean, focused interface with no third-party ad banners cluttering your results.
Privacy-first
No upload and no account needed.
How it runs
No analysis engine — this is a browser-only checklist.
No sign-up
Start immediately — no account, login, or email required.
Works anywhere
Runs in any modern browser, on desktop or mobile.
Frequently asked questions
What does Google Play Policy Checker do?
Check your app against common Google Play Developer Program policies before you submit for review.
Is it free to use?
Yes. Every tool on APKLint is completely free, with no sign-up and no account.
Do I need to upload anything?
No. This is a free reference checklist you work through in your browser — there's nothing to upload and no file is analyzed.
Does it cover the latest Google Play requirements?
This is a static reference guide, last reviewed 22 September 2026. Android and Google Play requirements change over time, so verify time-sensitive policy details in the Play Console before publishing.
Related tools
All product names, logos, and trademarks are property of their respective owners. APKLint is an independent toolset and is not affiliated with, endorsed by, or sponsored by Google, Android, or any other party.