1. Google Play Families Policy Requirements apply as soon as any selected target age group includes children — not only when children are the primary audience. Play Console Help splits this into three cases: apps designed primarily for children under 13; apps designed for everyone, including children; and apps not designed for children. The first two must follow Families Policies (including Families Ads and Monetization). Play also reviews store-listing imagery and wording independently of your form answers; cartoon characters or "for kids" language can pull you into Families even if you left child age groups unchecked.
2. Declare the audience in Play Console under Policy → App content → Target audience and content (Start, or Manage if it already exists). Complete Ads, App access, and the privacy-policy URL first — Play Console Help requires those before Target audience and content will unlock. Pick only the age groups you actually designed for (Ages 5 and under, 6–8, 9–12, 13–15, 16–17, 18 and over). Select mixed child-plus-adult groups only if the product is truly built for all ages, not just to keep the listing visible to everyone. The Ads step then asks whether you use Google Play Families Self-Certified Ads SDK Program versions and, for mixed audiences, whether a neutral age screen is in place. Apps primarily for children, or for children plus older users, can be considered for Teacher Approved after they comply; that opt-in is not a substitute for the Families declaration.
3. Ads shown to children or users of unknown age must come only from Families Self-Certified Ads SDK versions listed in the Families Self-Certified Ads SDK Program. Children-only apps may ship those certified versions and nothing else. Mixed-audience apps may use a non-certified SDK only behind a working neutral age screen, and only for users verified as not children. Interest-based advertising and remarketing to children are prohibited. Families ad-format rules still apply: no ad walls, no interstitial at launch, rewarded or opt-in ads closeable after 5 seconds, no multiple banners on one screen, and no ads that children cannot tell apart from app content.
4. Data practices are part of Families Policy Requirements and must match COPPA (U.S. Children's Online Privacy Protection Act), GDPR, and local child-privacy law. Disclose every collection of personal or sensitive information from children — including through APIs and SDKs — in Policy → App content → Data safety and in the privacy policy. Sensitive data here includes authentication info, microphone and camera sensor data, device data, Android ID, and ad-usage data. Apps that solely target children must not transmit AAID, SIM Serial, Build Serial, BSSID, MAC, SSID, IMEI, or IMSI, and should not request the AD_ID permission when targeting API 33 or higher. Mixed-audience apps must not transmit those identifiers from children or users of unknown age. Children-only apps may not request location permission or collect, use, or transmit precise location. Collect a child's name, email, or similar personal data only with parental consent where the law requires it, and never use that data for behavioral ads.
5. Parent gates and age screens must be adult action as Families Policy defines it: a PIN, password, free-form birthdate, email verification, or similar check that does not nudge children to lie about their age. A neutral age screen asks for month, day, and year of birth with no preset of 13 and no hint that a certain age unlocks the rest of the app — the FTC age-screen guidance and Play Console Help both treat a pre-filled 13th birthday as a failed gate. For social features, require that adult action before a child can exchange personal information, show an in-app reminder about online and real-world risk before freeform sharing, and give an adult a way to disable or limit the social feature. A skippable "I am a parent" checkbox is treated as a bypassable parent gate.
6. Child Safety Standards overlap Families whenever the app has UGC, chat, or a Social / Dating category — and they apply even if you have no child users. Since the 2026-07-15 expansion (deadline 2026-08-26), Anonymous Chat and Random Chat apps are in scope alongside Social and Dating; Families Policy separately prohibits anonymous-chat apps from targeting children. Complete Policy → App content → Child Safety Standards: a working public CSAE (child sexual abuse and exploitation) standards URL that names the app or developer as on the store listing, an in-app feedback / report path users can reach without leaving the app, self-certification that you remove CSAM on actual knowledge and report confirmed CSAM to NCMEC or the regional authority, and a child-safety point of contact. The User-Generated Content policy still requires terms acceptance, in-app report and block, and ongoing moderation. Disclose social features accurately on the IARC Content Rating questionnaire in the same App content page.
7. Common Families rejections and the usual fixes: store listing looks child-directed while Target audience excludes children — either strip the kid-appealing assets or change the age groups and meet Families Policy. An uncertified ads SDK, or a certified SDK that still serves personalized / remarketing ads to children — remove it or put it behind a real neutral age screen. AAID, AD_ID, or precise location on a children-only build — drop the permission and the identifier. A non-neutral age screen (preset age, "must be 13+" copy, one-tap parent toggle) — replace it with free-form date of birth plus a hard-to-bypass adult PIN. Data safety or the privacy policy omits an SDK that talks to children — re-audit every dependency. Social or chat apps that skip Child Safety Standards, or anonymous chat that still selects child age groups — finish the form or drop children from the audience and restrict minor access if the Age-Restricted Content and Functionality policy requires it. Play Console Help treats misrepresentation in Target audience and content as grounds for removal, and a change in that section can be reviewed even before you upload a new artifact.