The App Content Checklist to Finish Before Closed Testing
Privacy policy, ads, sign-in details, target audience, content rating: the Play Console App content declarations to complete before your closed test.
You've built the app, uploaded the bundle and you're ready to find testers. Before you share an opt-in link, open Play Console → Policy and programs → App content and clear every declaration. Your release goes through review before testers can get it, so missing declarations stall your closed test before day one.
Why do this before closed testing
Your 14-day clock only starts once testers can actually opt in and install. Every day spent fixing paperwork after you've recruited testers is a day they might lose interest. Finishing declarations first means your testers' first experience is a working install.
The checklist
Based on Google's "prepare your app for review" help page:
| ✔ | Declaration | What it needs |
|---|---|---|
| ☐ | Privacy policy | A public URL explaining how your app treats sensitive user and device data. |
| ☐ | Ads | Declare whether your app contains ads. |
| ☐ | Sign-in details | If any part of the app needs an account, membership or other access, give reviewers working access instructions. |
| ☐ | Target audience and content | Declare the age groups your app targets. |
| ☐ | Content rating | Complete the rating questionnaire so the app isn’t left “Unrated”. |
| ☐ | Permissions declarations | Needed if you request high-risk or sensitive permissions. |
| ☐ | Category-specific declarations | For example news apps, or other special categories Play Console asks about. |
Play Console shows which items are still outstanding on the App content page, so treat that page as your live checklist.
Sign-in details: the one people forget
If your app needs a login, Google asks you to "provide all required details to enable access to your app." You can add up to five sets of instructions, including notes about things like one-time passwords. Create a dedicated reviewer account that doesn't expire, and don't rely on SMS codes going to your personal phone.
Privacy policy tips
- Host it at a stable public URL. A page on your own site is ideal.
- Describe what your app actually collects, including through SDKs like analytics or ads, and why.
- Keep it consistent with your other declarations. A policy that contradicts what you declared elsewhere invites questions.
- Policies are legal documents. If you handle sensitive data, have a qualified professional review it.
Then start testing
With declarations done, set up your closed track, then list your app on TestersZone (your first listing is free) to get up to 20 testers who check in daily. If testers can't get in, use our opt-in troubleshooting guide.
How we keep this accurate
Policy facts in this guide are checked against Google's Play Console Help pages, linked inline, on the date shown above. Google can change its requirements at any time, so always confirm in your own Play Console. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start free