Reconcile the audience with the product
Review visual design, characters, language, gameplay, marketing and actual intended users. Keep the target-audience declaration distinct from the content rating: a low maturity rating alone does not mean the app is designed for children.
For mixed audiences, inspect how age-related choices affect the experience. A decorative age screen that does not control SDK initialization or ad requests does not establish a separate child-appropriate path.
Audit every advertising dependency
Check the current Families Self-Certified Ads SDK requirements and the versions used by each network or adapter. Approval of the main mediation SDK does not automatically cover every added adapter and configuration.
| Area | Review question |
|---|---|
| Ad SDK | Is the applicable version eligible for the intended audience? |
| Initialization | Are audience and consent settings applied before collection? |
| Ad content | Are formats, offers and maturity appropriate? |
| Identifiers | Is collection consistent with the audience rules? |
| Store presentation | Does it accurately represent the child or mixed-audience experience? |
Do not test this by clicking live ads or using real children's personal data in a development environment.
Review non-ad behavior too
Authentication, chat, analytics, external links and user-generated content can create additional responsibilities. Restrict data collection to what the product genuinely needs and explain the applicable practices accurately.
Check remote configuration and server-delivered content. A compliant initial release can become inconsistent when a new ad network or social feature is enabled remotely.
Keep evidence with the release
Retain the audience decision, SDK inventory, configuration and test results. APKLint's Families Policy Checker can structure that review, but it cannot determine a child's age, certify an SDK or guarantee store approval.
Use the current Families policy and relevant SDK data-disclosure guidance. Where child-privacy law applies, seek qualified legal advice in addition to meeting the store's product requirements.
Sources and further reading
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
