Short answer
Put every link out of the app and every purchase behind a parental gate. Remove third-party analytics and advertising SDKs unless they meet Apple’s limited exceptions, such as analytics that collect no IDFA or identifiable information about the child. Add a privacy policy. If the app is not really for kids, leave the Kids Category and take “for kids” wording out of the metadata.
Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
What 1.3 and 5.1.4 reject, and the fix
01
Links or purchases without a parental gate
“These apps must not include links out of the app, purchasing opportunities, or other distractions to kids unless reserved for a designated area behind a parental gate.” Apple, Guideline 1.3
A web link, a social button, a store link or an in-app purchase that a child can reach directly breaks 1.3. Put each one behind a parental gate. Apple’s own page on parental gates explains what it expects.
02
Third-party analytics or ads SDKs
“Apps in the Kids Category should not include third-party analytics or third-party advertising.” Apple, Guideline 1.3
Check the build for analytics, ad network and attribution SDKs, including ones a plugin pulled in. Remove them, or keep only analytics that send nothing that could identify the child or the device.
03
Personal data without a privacy policy
“the parental gate requirement for the Kid’s Category is generally not the same as securing parental consent to collect personal data under these privacy statutes.” Apple, Guideline 5.1.4
Collecting a name, email, photos, chat or location from a child needs a privacy policy and compliance with children’s privacy laws such as COPPA. A parental gate is not the same as parental consent to collect that data.
04
The app left the Kids Category but still looks like it
“it will need to continue to meet these guidelines in subsequent updates, even if you decide to deselect the category.” Apple, Guideline 1.3
Also check: Apple says that once customers expect the app to follow the Kids Category requirements, it must keep meeting them in later updates even if you deselect the category. An app outside the category also can’t use terms in its name, subtitle, icon, screenshots or description that imply the main audience is children (5.1.4, 2.3.8).
Checked against the vendor’s docs on : Apple: App Review Guidelines, 1.3 Kids Category; Apple: App Review Guidelines, 5.1.4 Kids; Apple: App Review (replying and appeals).
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
Resubmit before Apple’s holiday slowdown
Pay for the Diagnosis and send the rejection and access to the app by (US Eastern). The Diagnosis is back by . Pay for the Fix that day and it arrives as a pull request by , in time to build and resubmit before .
In past years Apple said reviews may take longer around the holidays: December 20 to 26 in 2024 (opens in a new tab), December 22 to 27 in 2023 (opens in a new tab), December 23 to 27 in 2022 (opens in a new tab). Apple hasn’t posted its 2026 dates yet (checked ). Approval stays Apple’s decision.
“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
Related: App Store Guideline 2.3.8 metadata · App Store Guideline 5.1.1 · App Store Guideline 3.2.2 · App Store Guideline 3.1.1