App Store 5.1.4 rejection: Children's privacy

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps intended for children or able to collect or share a minor's personal information.

A parental gate doesn’t automatically provide consent to collect a child’s information. Apple’s 5.1.4 covers children’s data, while 1.3 adds Kids Category requirements. We’d review both the audience and the actual data flows.

5.1.4(a): collection and a useful experience

Review the applicable children’s privacy laws with qualified advice. Requests for birthdate and parental contact information are limited to compliance purposes under this clause. The app should still provide useful functionality or entertainment regardless of age.

Apps primarily for children generally shouldn’t include third-party analytics or advertising. Inspect SDK traffic even if the app doesn’t ask for a name.

5.1.4(b): limited exceptions and disclosures

Any analytics or advertising exception must meet the conditions in 1.3. Covered apps need a privacy policy and compliance with children’s privacy laws. Apple distinguishes a parental gate from parental consent for data collection.

Keep claims such as “For Kids” consistent with the Kids Category rules. Check names, descriptions, and screenshots, not only the age-rating form.

Verify the child’s route

Use fictional age-group accounts to test collection, access, ads, and parental interactions. Explain the controls and any documented exception to Apple. Keep real children’s data out of your review evidence.

Messages this guide can help with

App Store 5.1.4 rejection; app store 5.1.4 denial; Guideline 5.1.4; Children's privacy; 5.1.4(a); 5.1.4(b)

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review