Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Google Play rejection

Families policy: apps that appeal to children, the target audience declaration and ads

Google decides whether your app is "for children" from two sources: the target audience you declare, and what the app looks like. A bright, cartoonish app declared for adults is a mismatch; an app declared for children with regular AdMob is a violation. This guide walks through both situations and what to set in your web app and in WebViewGold.

From $109 one-time per platform, or let our team do it all from $698.

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

How Google decides who your app is for

In App content → Target audience and content you select age groups. As soon as any group under 13 is included, or the app is marked as directed at children in a region with its own definition, the Families policy applies in full. But the declaration is not the only input. Reviewers also judge whether the app appeals to children: the icon and screenshots, cartoon characters, simple games, "kids" or "ABC" in the name, bright primary colors, a toddler-level UI. If the app appeals to children and you declared adults only, Google calls it a target audience mismatch and asks you to either change the declaration or change the app.

Declaring a mixed audience (children and older users) is possible, but it adds requirements of its own, such as a neutral age screen and handling each age group according to its rules. Most vibe coders are better served by a clear decision: either build a children's app and meet the policy, or build for adults and look the part.

What the Families policy requires

  • Ads

    Certified ad networks only

    Only ad SDKs from Google's self-certified families list, configured for child-directed treatment; no interest-based ads, no ads that are inappropriate for children, no ads disguised as content. The easiest compliant setup is no ads at all.

  • Data

    Minimal data, no advertising ID

    No personal information from children without verifiable parental consent, no advertising ID, no precise location. Data safety must reflect this.

  • Links

    Parental gates on the way out

    Links to websites, social networks, other apps and purchases must sit behind a gate a child cannot pass easily (a math question, a hold-to-continue, a parent PIN).

  • Login

    No social logins for children

    Google or Facebook sign-in is for adults. Use a parent account or no account at all for the child part of the app.

  • Content

    Age-appropriate throughout

    No mature content, no gambling mechanics, no user-generated content visible to children without strong moderation, and a content rating that matches.

  • Quality

    Teacher Approved is optional

    The Teacher Approved program is a badge for high-quality children's apps, reviewed by educators after you publish. It is not required to pass review, and you apply from the Families section in Play Console.

Rules by audience declaration

Adults only (13 and older)Children included
AdsAdMob as usual, with content filtersFamilies-certified SDK with child-directed settings, or no ads
Data collectionRegular Data safety declarationNo advertising ID, no precise location, parental consent for personal data
Social featuresAllowed with UGC policy complianceStrongly limited; moderation and parental involvement required
External links and purchasesNormalBehind a parental gate
Look and feelMust not primarily appeal to childrenChild-appropriate design expected
ReviewStandard reviewAdditional Families review of the app and the listing

I am very happy I bought this app! Extremely easy and great documentation. Was in contact with the customer service, they replied very quickly and very friendly. They solved my question within a day. 10/10 would recommend.

Nelis Geiger · CodeCanyon

Make a children's app compliant with WebViewGold

The native side takes five minutes; the web side is where the work is.

  1. Declare the audience truthfully

    Select the age groups the app is really for. If it is for both children and parents, consider splitting into a parent dashboard (adults) and a child mode that follows the rules below.

  2. Switch off ads and tracking in Config.java

    Set SHOW_BANNER_AD, SHOW_FULL_SCREEN_AD, ENABLE_REWARDED_ADS and USE_FACEBOOK_ADS to false, and TRACKING_EVENT to false unless you have a consent flow for parents. If you must monetize with ads, use AdMob's child-directed configuration and only the certified network.

  3. Remove the advertising ID permission

    With ads off, strip the Ad ID permission from the merged manifest as shown in the Data safety guide, then declare no advertising ID.

  4. Drop sensitive permissions

    Set requireLocation, requireCamera and requireRecordAudio to false unless the feature is essential and age-appropriate, and remove the manifest entries. Children's apps rarely justify any of them.

  5. Add parental gates in the web app

    Ask your builder for a reusable gate component in front of external links, purchases and any contact form. Decide where external links open with EXTERNAL_LINK_HANDLING_OPTIONS in Config.java (main WebView, in-app tab or system browser); whichever you choose, the gate sits in front of the link in your web app.

  6. Write a children's privacy section

    State what you collect from children (ideally nothing), how parents can review or delete it, and which laws apply (COPPA, GDPR-K). Link it from the listing and inside the app.

  7. Rate and submit

    Complete the content rating for the child content, fill in Data safety accordingly, and submit. Expect the Families review to take a little longer than a standard review.

Mistakes we see

  • A learning game for kids with the default AdMob interstitials from the template.
  • Google sign-in as the only login in an app for six-year-olds.
  • A "Share with friends" button that opens WhatsApp without a gate.
  • Analytics scripts from the web app collecting identifiers from child users.
  • Mixed audience declared without an age screen, so children see the adult version.

Frequently asked questions

My app is for parents, but the icon has a cartoon baby. Is that a problem?

It can be. Reviewers look at the overall impression. Make the icon and screenshots clearly address parents, and keep the target audience declaration at adults.

Can I use OneSignal push notifications in a children's app?

Push itself is allowed, but the data the push provider collects must comply with the Families rules and be declared. Keep notifications free of personalization and marketing to children, and check the provider's guidance for child-directed apps.

Can a children's app have in-app purchases?

Yes, behind a parental gate and clearly disclosed, using Google Play Billing (for example via RevenueCat in WebViewGold). Purchases must not be designed to pressure children.

Three ways to get your app into the stores

Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.

Do it yourself

$109 per platform, one-time

The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.

See plans on the main page

Cloud Builder

$349 per license, one-time add-on

No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.

How the Cloud Builder works Try the free demo

Full Service

$698 per platform $798

Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.

Full Service details Powered by WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Ready to ship your app?

App Store & Google Play approval guarantee – or your money back within 14 days

Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.

Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.