Guideline 5.1.4
Guideline 5.1.4 - Privacy: Using 'For Kids' Without Being in Kids Category
Our Take
Apple is rejecting your app because it uses 'for kids' or similar child-directed language in its metadata (name, subtitle, description, keywords, screenshots) without being published in the Kids category on the App Store. Under guideline 5.1.4, apps that market themselves to children must be placed in the Kids category, which triggers additional privacy requirements under COPPA and Apple's own children's privacy policies. This rejection is a metadata issue, not necessarily a code issue. Apple considers any of these triggers: 'for kids,' 'for children,' 'kid-friendly,' 'child-safe,' 'ages 3-8,' or similar language in your app name, subtitle, description, promotional text, or keywords. If you use this language, Apple requires your app to be in the Kids category. The catch is that being in the Kids category comes with strict requirements: no third-party analytics, no third-party advertising (except certified COPPA-compliant networks), no links out of the app, no account creation for children, and parental gates for any external links or purchases. If your app can't meet those requirements, the fix is to remove the child-directed language from your metadata, not to move to the Kids category.
Resolution Guide
**Decide: Kids category or not** — If your app genuinely targets children, move it to the Kids category and ensure full COPPA compliance. If it targets a general audience, remove child-directed language.
**Option A: Move to Kids category** — In App Store Connect, change the primary category to an appropriate Kids subcategory. Then ensure: (a) no third-party analytics except Apple's, (b) no third-party advertising except COPPA-certified networks, (c) parental gates on external links and purchases, (d) no account creation for children, (e) no collection of personal information from children.
**Option B: Remove child-directed language** — Remove 'for kids,' 'for children,' 'child-friendly,' age ranges, and similar terms from your app name, subtitle, description, keywords, and screenshot text. Reframe for a general audience.
**Audit screenshots and preview videos** — Check that promotional assets don't contain child-directed messaging that contradicts your chosen path.
**Update the age rating** — Ensure the age rating in App Store Connect is consistent with your target audience.
Prevention
Example Rejection Email
Before & After
App name: 'MathBlast - Fun Learning for Kids'; Category: Education; includes Google AdMob and Firebase Analytics
Option A: App moved to Kids category, AdMob replaced with Apple Search Ads, Firebase Analytics removed, parental gates added. OR Option B: App renamed to 'MathBlast - Fun Learning Games', child-directed language removed from all metadata, remains in Education category
What changed: You must either fully commit to the Kids category with all its restrictions, or remove all child-directed marketing language.
Community Solutions · 0
Sign in to share your solution.
More Guideline 5 (Legal) rejections
- Guideline 5 - Legal: Remove Watermark Feature
- Guideline 5.1.1 - Data Collection and Storage: Incomplete Privacy Manifest
- Guideline 5.1.1 - Data Collection and Storage: Missing Purpose Strings
- Guideline 5.1.1 - Data Collection and Storage: Privacy Manifest Missing
- Guideline 5.1.1 - Data Collection and Storage: Privacy Nutrition Label Mismatch
- Guideline 5.1.1 - Data Collection and Storage: Privacy Policy