Apps aimed at children face the strictest rules on Google Play. The Families policy and related requirements impose extensive obligations on apps that target or appeal to kids, and getting them wrong is one of the fastest ways to have an app rejected or an account penalized. On top of these rules, a kids app published from a new personal account must also complete a closed test with at least 12 testers opted in for 14 continuous days before production access. This guide covers Families policy testing and the category-specific compliance you must get right during your window.
The closed-testing process is identical to any app, but kids apps carry the heaviest compliance burden of any category. Using your testing window to validate both functionality and rigorous Families-policy compliance is essential, because the consequences of mistakes here are severe.
The requirement applies to kids apps
There is no exemption for children's apps. The closed-testing requirement is tied to your developer account type, so a kids app on a new personal account must complete a closed test with 12+ testers for 14 continuous days before production access. See the closed testing guide. Because Families-policy compliance is demanding, plan for it to run in parallel with your testing window and start early.
Standard advice applies: recruit committed, device-diverse testers, keep your count above 12, and prepare your listing in parallel. But for kids apps, the compliance work is the harder and more consequential half of launch preparation.
The Families policy and its requirements
Google's Families policy governs apps that target children or a mixed audience including children, and it is extensive. It covers content appropriateness, data collection restrictions, advertising rules, correct target-audience declarations, and participation in the Designed for Families program where applicable. Kids apps must strictly limit data collection, use only certified ads SDKs, avoid inappropriate content, and meet privacy requirements that go well beyond those for general apps. Review Google's Families policy requirements in full.
Correctly declaring your target audience in the Play Console is a critical first step, because it determines which rules apply. Misdeclaring your audience — claiming an app is not for children when it clearly appeals to them — is a serious violation. Use your testing window to confirm your declarations are accurate and that every Families-policy requirement relevant to your app is satisfied. See COPPA and kids apps.
Data collection and advertising
Kids apps face strict limits on data collection and advertising. You must minimize data collection from children, avoid collecting personal information except as narrowly permitted, use only Google-certified ads SDKs configured for child-directed treatment, and avoid behavioral advertising to children. These rules exist to protect kids, and Google enforces them firmly. Any third-party SDK in your app must be compatible with Families requirements, so audit your dependencies carefully. See ad policy testing and analytics SDK testing.
| Kids app requirement | What to verify |
|---|---|
| Data minimization | Collect only what's narrowly permitted |
| Certified ads SDKs | Only Families-compatible, correctly configured |
| No behavioral ads to kids | Ads must be non-personalized |
| Content appropriateness | Everything suitable for the age group |
| Third-party SDKs | All must be Families-compatible |
Use your testing window to audit every SDK and data flow against these rules. This is where kids apps most often fail review.
Content and age-appropriateness
All content in a kids app must be appropriate for the target age group, including any user-generated content, external links, and ads. Google reviews children's apps carefully for anything unsuitable, and even indirectly accessible inappropriate content — through an ad, a link, or a web view — can cause rejection. Ensure there are no pathways from your app to content that would be inappropriate for children, and that any interactive or social features are safe and moderated. Consult the Play developer policy center.
During testing, have testers explore every corner of your app, including links, ads, and any external content, to confirm nothing inappropriate is reachable. Pay particular attention to any web views or outbound links, which are common escape hatches to non-compliant content. Getting content safety right is both a policy requirement and an ethical obligation for apps used by children, and your testing window is the time to verify it exhaustively.
Setting up your closed-testing track
Once your signed release build is ready, create a closed-testing track in the Play Console and upload it, add testers by email or Google Group, and share the opt-in link each tester must use before installing. Correct configuration matters because the 14-day clock counts only opted-in testers, and a misconfigured track is a common reason developers realize late that their timer never started. Install from the listing on a real device and confirm the app behaves correctly before inviting your group. See how to create a closed testing track.
Give testers clear onboarding instructions covering the opt-in flow and what to check, and ask them to probe content safety, ads, and any links. Every failed opt-in is a tester who does not count toward your 12, so smooth guidance maximizes active testers from day one and gives you thorough coverage of the compliance-critical areas that matter most for a kids app.
Recruiting and managing the window
You need 12+ committed, device-diverse testers for 14 continuous days. Recruit a buffer above 12 to absorb attrition, keep testers engaged with clear instructions and quick responses, and direct them to test content safety, ads behavior, and data flows in addition to functionality. Monitor your active count in the Play Console and recruit replacements early if it slips toward the minimum.
If assembling a reliable, device-diverse group is your bottleneck, a service that supplies verified real testers solves it quickly. You can submit your app to get started, and read where to find real testers and how to keep testers engaged.
From closed testing to production
When your 14 continuous days with 12+ testers complete, request production access in the Play Console. For a kids app, ensure your target-audience declaration, Families-policy requirements, ads configuration, data declarations, and content are all fully compliant before you submit, since kids apps face intensive review. Preparing everything in parallel during the window lets you submit immediately rather than losing more time. See what happens after 14 days.
Why real-device testing matters for kids apps
Children's apps are used on a huge range of hardware, from hand-me-down budget phones to tablets shared across a family, and real-device testing across that range matters both for quality and for compliance. Performance on low-end devices, correct behavior of parental gates and controls, and the actual rendering of your content and any ads all vary across hardware, and the compliance-critical question of what content and ads are reachable can look different on different devices. Testing on one clean development device tells you little about the varied, often older hardware that children actually use.
This is why the closed-testing requirement, built on real opt-in testers, is genuinely useful for kids apps. Real testers exploring your app on diverse devices surface both functional problems and, crucially, any pathways to inappropriate content or non-compliant ad behavior that only appear in real use. The window is your structured chance to verify that your app is safe, appropriate, and functional across the market before children ever open it, which is both a policy obligation and an ethical one.
Common reasons kids apps get rejected
Kids apps face the highest rejection rate of any category because the Families policy is strict and closely enforced. The most common causes are misdeclaring the target audience, using non-certified or misconfigured ads SDKs, collecting more data than permitted, including third-party SDKs that are not Families-compatible, and having reachable content — through ads, links, or web views — that is not age-appropriate. Each of these is a serious violation, and any one can block your launch or endanger your account.
Use your window to audit exhaustively against these pitfalls: confirm your audience declaration is accurate, verify every ads and analytics SDK is Families-compatible and correctly configured, minimize data collection, and probe every path in your app for inappropriate content. This is the most compliance-intensive audit of any category, and doing it thoroughly before you request production access is what prevents the painful, repeated rejections that kids apps so often suffer. See app not eligible for production access and COPPA and kids apps.
Turning tester feedback into fixes
The value of your closed test scales with how well you capture and act on feedback. Give testers a frictionless way to report problems and ask specific questions, including compliance-focused ones: could you reach any content that seemed inappropriate, did any ad look like a personalized or behavioral ad, did the parental gate work, did anything confuse a child user? Concrete prompts produce the actionable reports that catch both functional bugs and the policy risks that matter most for a kids app.
Then close the loop: when you ship a build addressing reported issues, tell testers what changed and ask them to reconfirm on their device. This validates fixes across diverse hardware and keeps testers engaged. A kids app that enters production having already closed off every inappropriate-content path and confirmed compliant ad behavior launches with far less risk of the enforcement that plagues this category. See ad policy testing.
A realistic timeline for your launch
Plan backward from the 14-day minimum, and add generous margin for kids apps given the compliance burden. Expect several days up front to finalize your build, complete your extensive Families-policy preparation, recruit and onboard testers, and confirm opt-ins before your continuous window begins; the 14 days then run while you fix issues; and review, which is intensive for kids apps, takes additional days and sometimes multiple rounds. Budgeting four weeks or more end to end is realistic and prudent.
Developers who hit their dates front-load recruitment and the compliance audit so nothing blocks them when the window closes. If tester recruitment is your uncertain variable, resolving it early through your network or a service supplying verified real testers is the highest-leverage step for keeping your launch on schedule. See getting 12 testers without friends or family.
Use internal testing before your closed test
The Play Console's internal testing track is faster than the closed track and ideal for a first pass, and for a kids app it is especially useful for shaking out compliance issues privately. Push your build to a small trusted group, confirm ads render as non-personalized, verify no inappropriate content is reachable, and check that data collection is minimal — all before your counted 14-day window begins. Catching Families-policy problems here, rather than during your closed test or at review, protects both your timeline and your account.
A practical rhythm is to validate each release candidate on the internal track, confirm compliance and basic functionality on a couple of real devices, then promote it to the closed track where your counted testers live. This keeps the closed track stable and your compliance audit thorough. Treating internal testing as your staging step and closed testing as the requirement is a simple discipline that materially reduces the risk of a rejection for a category where rejections are common. See internal vs closed testing.
Key takeaways
- Kids apps must meet the 12-tester, 14-day requirement plus the demanding Families policy.
- Declare your target audience accurately — it determines which rules apply.
- Minimize data collection and use only certified, non-behavioral ads.
- Audit every third-party SDK for Families compatibility.
- Ensure all reachable content is age-appropriate, including links and ads.
Frequently asked questions
Do kids apps need closed testing?
Yes. On a new personal account, the 12-tester, 14-day requirement applies, in addition to the Families policy.
What is the Families policy?
Google's set of rules for apps targeting children, covering content, data, ads, declarations, and privacy — far stricter than general rules.
Can I show ads in a kids app?
Only through Google-certified, Families-compatible ads SDKs configured for non-personalized ads. Behavioral advertising to children is prohibited.
Why does my SDK matter for a kids app?
Every third-party SDK must comply with Families requirements. A non-compliant SDK can cause rejection, so audit all dependencies.
How do I find testers for a kids app?
Use your network, communities, or a service, and direct them to test content safety and compliance in addition to functionality.
Why do kids apps get rejected so often?
Because the Families policy is strict and closely enforced. Common causes are misdeclared audience, non-compliant ads or SDKs, excess data collection, and reachable inappropriate content.
Do I need certified ads SDKs for a kids app?
Yes. You must use only Google-certified, Families-compatible ads SDKs configured for non-personalized ads, and every third-party SDK must comply.
How long should I budget for a kids app launch?
Budget four weeks or more. The extensive Families-policy preparation and intensive, sometimes multi-round review add time beyond the 14-day window.