How to Set Up a Child's First iPhone Properly

Published August 24, 2026 · Last reviewed September 2, 2026

Why the account has to come first

The common mistake is handing over a phone signed into an adult Apple Account — often a spare one, or a parent’s — and adding restrictions afterwards. It half-works. You lose Ask to Buy, you lose age-appropriate defaults, purchases go to the wrong place, and every limit becomes something you bolted on rather than something the account came with. Fixing it later means migrating an account, which is considerably more disruptive than getting it right on day one.

A child account created in Family Sharing gives you: purchase approval, screen-time reporting to your device, location sharing within the family, and Screen Time controls you manage remotely. None of that is available otherwise.

The setup sequence

1. On your iPhone, open Settings, tap your name, tap Family, and add a child.
2. Create the child’s Apple Account with their real date of birth — this drives age-appropriate defaults and cannot be casually changed later.
3. Turn on Ask to Buy so any download or purchase, including free apps, needs your approval.
4. Set up the child’s iPhone and sign in with that account.
5. Set a Screen Time passcode that is different from the device passcode the child knows.
6. Configure Content & Privacy Restrictions and Downtime before handing the phone over.

The first-day settings that matter

Action

Set a Screen Time passcode that the child does not know and that differs from the device passcode.

Why it helps

This is the single most important step. If the two match, a child who can unlock the phone can remove every limit in under a minute.

Verification

Ask the child to open Screen Time; it should demand a passcode they cannot provide.

Action

Turn on Ask to Buy for the child, and check it appears on your device the first time they try to download something.

Why it helps

It converts every install into a short conversation, which is more useful than any blocklist because it teaches judgement rather than enforcing a list.

Verification

A request notification arrives on the parent's phone.

Action

Turn off Allow Apps to Request to Track and review app permissions before handing the phone over.

Why it helps

A child cannot meaningfully consent to cross-app tracking, and the defaults are worth setting once rather than reacting to prompts later.

Verification

The Tracking list under Privacy & Security is empty.

Action

Set up Find My and family location sharing openly, with the child present.

Why it helps

Location sharing configured together is durable; discovered covertly it gets defeated and damages trust.

Verification

Both of you can see each other in Find My.

Action

Turn on Communication Safety and explain what it does before the child needs it.

Why it helps

It blurs nudity in photos on the device and offers help, without sending images anywhere. Explaining it first means it is a safety net rather than a surprise.

Verification

The setting shows as on under Screen Time.

What to agree out loud

The technical setup is the easy half. The part that determines whether it survives is a short, explicit agreement, ideally written down:

• Where the phone sleeps — a charging spot outside the bedroom removes the single biggest source of late-night conflict.
• What happens if something upsetting arrives — that they can tell you, and that they will not lose the phone for it. A child who fears confiscation will not report a problem.
• When the rules get reviewed — a stated date, such as every birthday. Limits with a review date are accepted far more readily than limits presented as permanent.

What changes as they get older

A child account carries age-based defaults that relax automatically at certain ages, and control transfers fully when they reach the age of majority in your region. Plan for that rather than being surprised by it: the goal of a first phone is a teenager who can manage their own, not a fifteen-year-old still on nine-year-old settings who has learned to route around them.

How it works

Family Sharing creates a parent-child relationship between Apple Accounts, and that relationship — not the device — is what carries the controls. Because the link lives at the account level, Screen Time limits and purchase approvals follow the child across every device signed into that account, and a parent can adjust them remotely from their own phone without handling the child's.

The date of birth matters more than it appears. It determines the default content ratings applied to the App Store, media, and web content, and it governs which protections are on by default and when they relax. It also has legal weight: children's privacy regulations in many regions constrain what data may be collected from an account known to belong to a child, so an honest date of birth genuinely changes how the account is treated.

The Screen Time passcode is deliberately a separate credential from the device passcode, and everything else depends on that separation. The device passcode has to be known to the child; the Screen Time passcode authorises changing the limits. Setting them to the same value collapses two different authorities into one and silently disables the whole system — which is why it is the most common reason parental controls quietly stop working.

Worked example

A ten-year-old receiving a hand-me-down iPhone. The parent's first instinct is to erase it, sign in with the family Apple Account already on the household iPad, and add restrictions.

That approach is abandoned for a specific reason: purchases would be attributed to the parent's account, Ask to Buy would not exist, and the App Store would apply adult content defaults regardless of any restrictions added afterwards.

Instead, the parent spends four minutes creating a child Apple Account in Family Sharing with the real date of birth, and turns on Ask to Buy. The phone is erased and set up with that account. A Screen Time passcode is set — deliberately different from the 6-digit device passcode the child will use — and Downtime is configured for 20:30 to 07:00 with Messages and Phone in Always Allowed.

Total setup time: about 25 minutes. The verification happens the same evening, when the child tries to install a game and a request appears on the parent's phone rather than the app simply installing. Six months later, a comparison with a friend's household is instructive: there, the child account was skipped, and the child disabled all Screen Time limits in the first week because the Screen Time passcode was the same as the device passcode.