Require approval for a younger child’s eligible downloads and purchases, decide which adults can respond, and run a free-app and paid-item test before handoff.
Why this decision matters
The useful part of Ask to Buy is the conversation before access. A request lets the parent check the app, business model, permissions, age fit, and why the child wants it instead of discovering it after installation.
A practical starting sequence
Verify eligibility and roles
Confirm the child is in the correct family and that the intended adult is able to approve requests.
Set the family rule
Explain which apps are likely to be approved, which require discussion, and when requests will be reviewed.
Test the complete loop
Send a request from the child device, confirm the notification, review the item, approve or decline, and verify the result.
What the child experiences
The child sees a request flow for eligible items. Updates, some re-downloads, and other transactions may behave differently, so do not describe approval as universal.
Ask to Buy does not replace checking subscriptions, in-app business models, purchase sharing, or payment methods. Availability and defaults can vary by age and region.
When to review it
Review when app requests become frequent, when the child begins using subscriptions or games with in-app purchases, and at the 12–13 transition.
Configure purchases in context
The iPhone guide connects Ask to Buy with app permissions, content choices, and the parent-child request routine.
Current official sources
Interfaces and defaults change. These first-party sources were checked for this page; verify the live device before publishing or relying on an exact menu path.
See how KidPhoneSetup verifies technical guidance