AppReviewFix
Guideline library
Google Play — Kids & Families

Families Program — Designed for Families program compliance

Official source: Google Play Developer Program PoliciesTopic overview: Children’s apps
What this guideline means

Beyond the ads-SDK certification, apps directed at children face broader restrictions: no behavioral advertising to kids, tighter limits on data collection, age-appropriate content only, and permissions requests scoped to what's strictly necessary.

Why apps actually get flagged

A common cause is a kids' app requesting a permission (like precise location or contacts) that isn't essential to its core function, which draws extra scrutiny under the Families program's stricter permission bar.

A real example

"Your app is designated for children but requests a permission or collects data not essential to its core functionality, in violation of the Designed for Families program requirements."

The short version, in more detail

The Designed for Families programme sets broader rules for apps directed at children than the ad-SDK requirement alone. Behavioural advertising to children is not allowed, data collection is tightly limited, content must suit the age group and permission requests must be strictly necessary. A request for something like precise location or contacts that the core function does not need draws extra attention.

Why this rule exists

Children's apps are held to a higher standard because the audience is vulnerable and laws in many countries protect children's data. The programme gives families a set of apps that follow stricter rules, which is also a commercial advantage for developers who qualify. The limits on permissions and data reflect the principle that an app for children should ask for as little as possible.

What this guideline covers

  • Content suitable for the declared age group.
  • Limits on data collection and permissions.
  • Advertising and monetisation in children's apps.
  • Interactions that expose children to others.

What usually triggers this rejection

  • Requesting precise location or contacts without a core need.
  • Behavioural advertising in a children's app.
  • Content not appropriate for the age group.
  • Social features that let children contact strangers.
  • Collecting personal data that the app does not need.

How reviewers evaluate it

  • Reviewers check permissions against the app's function.
  • They test ads, content and sharing features.
  • They consider the audience declared in Play Console.
  • Children's apps get more scrutiny than most.

Common misunderstandings

  • Declaring a mixed audience does not remove all children's requirements.
  • An app does not have to be built for children to be covered if it appeals to them.
  • Permission requests are reviewed more strictly in this programme.

Common questions

Is joining the programme mandatory?

Apps directed at children must comply with its rules, whether or not they seek the badge.

What counts as directed at children?

Apps whose content and audience target children, as judged by factors such as design and marketing.

Are in-app purchases allowed?

With restrictions suited to the audience.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
1.3 — Kids Category5.1.4 — KidsFamilies Ads SDK — Families Self-Certified Ads SDK ProgramChild Endangerment — Child endangerment and CSAE policyFunctionality — Functionality, content and user experience
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.