Accounts, age limits and what a birthday changes

Parents set everything up carefully.

On one birthday, half of it changes silently.

Age limits kick in automatically. Approvals expire. Accounts switch status. The age that was set at signup quietly propagates to apps the parent has never heard of.

Almost no one knows that in advance.

This article is about that birthday.

It does not give you a single age for “how old does my child have to be”. That number is jurisdictionally bound, and the next section explains why that matters.

It gives you the mechanics: what an age limit is, what changes when the date moves, what the platform does for you and what it does to you, and what to prepare before the next birthday.

Why this matters

Three things make age the most consequential setting on a child account, and the hardest one to undo:

1. It propagates. The age set on an Apple Account, a Google Account, or a Microsoft account is shared with the App Store. It is also shared with third-party apps through Apple’s Declared Age Range API, and with game platforms that gate features by age [source: apple-declared-age-range] [source: www-biometricupdate-declared-age].

   Set it wrong on day one, and the wrong value reaches every app later — without the parent touching the setting again.

2. It triggers transitions automatically. When the child crosses the platform’s local threshold, several things change at once.

   Family Link supervision becomes opt-in rather than enforced. App Store rating tiers change. Ask to Buy may end [source: google-supervision-13] [source: apple-appstore-age-ratings].

   The platform does not ask before it does this. It notifies the parent afterwards.

3. It is jurisdictional. GDPR Article 8 lets every member state set its own age of digital consent between 13 and 16 [source: euconsent-gdpr-art8]. A single German-language page answering “how old must my child be?” is wrong for two of the three countries it will be read in. See the Country differences section below.

The rest of this article explains the mechanics and tells you what to do before the next birthday.

Prerequisites

Before you can act on this article, three things need to be in place. None of them is a setting on a device. They are all upstream of every parental control.

• You know which country you live in for this purpose. Digital age limits are jurisdictional, not linguistic. A parent who lives in Germany with a Swiss-registered Apple Account, or who moves between countries, must look up the value that applies where the account is held — not the value that applies to the language they read [source: euconsent-gdpr-art8].

• You have access to the parent-side control of every platform account the child uses. That means the Family Sharing organiser device for Apple, the Family Link parent device for Google, and the Microsoft Family Safety organiser for Microsoft.

  Without organiser access, you cannot see what the platform has stored [source: apple-region-rules] [source: google-supervision-13].

• You can open the per-country jurisdictional page for your country. Those pages are written as age-of-digital-consent-de, -at, -ch, -uk, and -us. They are the source of truth for the number that applies where you live. This article does not repeat the per-country values, by design (see ADR-0003 (docs/decisions/0003-localization-classes-and-jurisdiction-axis.md in the repository)).

If any of the three is missing, the Steps section below will tell you what you can prepare now and what you have to look up first.

How age limits work

Every major platform has a minimum age for holding a self-managed account.

Below that age, the account is a child account: created by a parent, attached to a family group, and governed by parental controls.

Above that age, the child may keep using the account, but the parent’s automatic authority over it loosens.

The mechanics are similar across Apple, Google, and Microsoft. The values are not.

This matters because it lets you separate two questions: “how does the platform behave” (universal) and “what is the threshold here” (jurisdictional).

The mechanics, universal to every platform:

• Account type is set at creation. You either create a child account (parent-owned, attached to a family group) or you do not.

  Apple documents this as a one-time decision [source: apple-region-rules].

  Google describes the supervised state as set at creation and revisable only via Family Link [source: google-supervision-13].

• Age is stored as a date. Both Apple and Google use the birthdate entered at signup as the source of truth [source: google-age-requirements] [source: apple-region-rules].

  The platform then derives current age from that date. You do not edit the age. You edit the date of birth, and the platform re-derives everything else.

• Age determines rating tier and approval flow. Apple exposes a five-tier App Store rating system (4+, 9+, 13+, 16+, 18+) and derives the ceiling from the account age [source: apple-appstore-age-ratings].

  Purchase approvals (Ask to Buy) are governed by separate rules that depend on the family configuration [source: apple.family.ask_to_buy_root].

• Age propagates to apps that ask. Apple’s Declared Age Range API lets an app, with consent, ask the operating system for the user’s age range rather than asking the user directly [source: apple-declared-age-range].

  This is the mechanism through which a wrong birthdate can quietly affect a service the parent has never touched.

The values are not universal — see Country differences.

What changes on a birthday

A birthday is the moment the platform re-derives state.

The parent typically experiences this as a notification and a behaviour change.

The most common transitions:

• Family Link supervision becomes opt-in for the child. Google notifies the family when the child reaches the applicable age in their country.

  The child can then choose to continue under supervision or leave it [source: google-supervision-13].

  The reported rule that stopping supervision requires parent approval until 18 was surfaced in Google’s help material but was not directly verified for this article [claim: google-supervision-13].

• App Store rating ceiling rises. A child turning 13 on an Apple Account gains access to the 13+ tier; turning 16 gains 16+; turning 18 gains 18+ [source: apple-appstore-age-ratings]. The platform does not need a setting change. The new ceiling applies automatically.

• Purchase approval may end. On Apple, Ask to Buy rules are part of the family configuration, not the age.

  The platform documents them in the same flow. They are commonly understood as “the thing that stops when the child grows up”.

  The actual rule is set per family, not per age [source: apple-region-rules].

• In-app age gates may trigger. Some services — most visibly Roblox, which uses facial age estimation globally — re-bin users into a new bracket on the next login [source: roblox-age-estimation].

  Other services ask for an ID re-check rather than a birthday.

• Data minimization may kick in. Roblox’s published behaviour, [claim], is to remove email and phone information when an estimate places a user below 13.

  The opposite transition (gaining those fields when reclassified above 13) is part of the same flow [source: roblox-age-estimation].

  This is a documented product behaviour, not independently audited.

• UK services re-test. Under the Online Safety regime, services that rely on age assurance are expected to refresh it.

  Ofcom’s 2026 report documents a 23-fold increase in completed age checks across 32 UK services between July and December 2025 [source: ofcom-age-assurance-2026].

  Self-declaration alone is not treated as effective age assurance in this regime [source: ofcom-age-assurance-2026].

The single most important fact about a birthday in this context: the change is platform-driven, not parent-driven. The parent is informed, not consulted.

Country differences

This section is jurisdictionally bound. The numbers below are examples, not a substitute for the per-country article. Language is not jurisdiction. ADR-0003 (docs/decisions/0003-localization-classes-and-jurisdiction-axis.md) makes the language/jurisdiction distinction a structural property of the wiki, not a wording choice.

The minimum age to hold a self-managed account differs by country. The differences are legal, not product-driven.

GDPR Article 8 sets the age of digital consent at 16 by default across the European Economic Area. It lets each member state lower it, “provided that such lower age is not below 13 years” [source: euconsent-gdpr-art8].

Every European exception you encounter in a platform’s help page is a member state exercising that option.

One concrete illustration, fetched directly from Google’s own help page in August 2026 [source: google-age-requirements]:

For a Google Account:

• Germany — 16.
• Austria — 14.
• Switzerland — unlisted in Google’s country table, therefore the default 13.

Same company. Same platform. Same question. Three different answers, because the legal answer differs.

The same pattern appears in Apple’s country table — under-16 in Germany, under-14 in Austria, under-13 in Switzerland for the child-account threshold [source: apple-region-rules].

The apple/google country lists do not match in every detail.

Denmark and Serbia appear on Google’s list but not Apple’s. Liechtenstein and Kosovo appear on Apple’s but not Google’s [source: google-age-requirements] [source: apple-region-rules].

This is unresolved in the located evidence.

A wiki page answering “what is the legal age in country X” should not pretend the disagreement does not exist.

Where to look up the value that applies to your country.

The wiki publishes per-country pages that are not translations of this article. They are jurisdictional pages, each carrying localization: jurisdictional per ADR-0003 and therefore not auto-translated:

• age-of-digital-consent-de — Germany.
• age-of-digital-consent-at — Austria.
• age-of-digital-consent-ch — Switzerland.
• age-of-digital-consent-uk — United Kingdom.
• age-of-digital-consent-us — United States.

Those pages are the source of truth for the number that applies where you live. This article deliberately does not repeat them. The table changes more often than this article is reviewed, and a wrong in-line value is worse than a missing link.

For US state-level enforcement of age assurance (Utah from 2026-05-06, Louisiana from 2026-07-01), the relevant page is us-state-age-verification-laws, not a general age article [source: www-biometricupdate-declared-age] [source: apple-dev-age-requirements].

Steps — prepare before the next birthday

A birthday triggers a state transition. The parent learns about it after the fact. The work that avoids surprise is work done before the date.

Numbered checklist:

1. Verify the birthdate on every platform account. Open the Apple Account (under Family in Settings), the Google Account (in Family Link), and the Microsoft Account (in the Family Safety app). Confirm the date of birth matches the actual date of birth.

   A wrong date set on day one propagates to every age-gated app later [source: apple-declared-age-range] [source: google-age-requirements].

2. Record the platform’s local threshold for your country. Look it up in age-of-digital-consent-de, -at, -ch, -uk, or -us, depending on where you live. Mark the date of the next crossing in a calendar reminder (six weeks ahead is a working lead time).

3. Decide, before the date, what you want to do. For each platform:

   • Will supervision continue, or end?
   • Should the rating ceiling rise, or stay where it is?
   • Should purchase approval stay on, or be removed?
   • Are there apps (Roblox, Discord, Snapchat, others) where the age bracket controls who can contact the child?

   The platform will not ask you these questions on the day [source: google-supervision-13]. The default is the new state, not the old one.

4. Talk to the child, not just to the platform. The age-transition conversation is also the conversation about digital autonomy. See Talking about it below.

5. Note the family-group notification date. Google notifies parent and child when the child reaches the applicable age [source: google-supervision-13]. Apple sends an equivalent Family Sharing notification. The notification is informational, not a request for permission — the transition happens anyway.

6. Plan for the UK age-assurance re-check, if relevant. Under the UK Online Safety regime, services relying on age assurance are expected to refresh it, not rely on the original signup age [source: ofcom-age-assurance-2026]. Expect a prompt for ID or another method, on a service-by-service basis.

7. For Roblox or similar platforms using facial age estimation: expect the child to be re-binned on next login. This happens regardless of what the birthday suggests.

   The estimate, not the stated birthday, controls the bracket [source: roblox-age-estimation].

   Independent evidence does not establish the accuracy of these brackets at the relevant legal thresholds (13, 16) for the production system used [source: ageassurance-aatt-age-estimation-2025].

8. Document the choices. Write down the decisions you made: continuation of supervision, rating ceiling, approval flow, family-group role. The next platform update or device replacement is more likely than the next birthday. A written record shortens the next conversation.

What no setting can hold back

Age limits are platform mechanics. They do not replace judgement.

The list below is what an age signal does not accomplish, even when it is set correctly for the country and the platform has done everything else right.

• It does not stop a child from using an older sibling’s account. Apple and Google identify the account, not the person holding the device.

  The signal is per-account, not per-face [source: apple-region-rules].

• It does not stop a child from creating a new account with a wrong birthdate. A 12-year-old who can read can also type a different year.

  Self-declared age is not treated as effective age assurance under the UK regime [source: ofcom-age-assurance-2026].

• It does not guarantee a rights-boundary decision is correct. Independent evidence on facial age estimation shows that threshold-conditioned false-positive and false-negative rates immediately around 13 and 16 are substantial [source: ageassurance-aatt-age-estimation-2025].

  An MAE figure such as “1.4 years” describes an average error [source: roblox-age-estimation] [claim: roblox-age-estimation]. It does not describe the probability that a specific child is on the correct side of the boundary.

• It does not propagate back from the app to the operating system. A Declared Age Range signal travels from the OS to the app, not the other way [source: apple-declared-age-range].

  An app that learns the child is older (for example, through a payment flow) cannot update the OS record.

• It does not equal parental authority. Where a country’s age of majority is 18, supervision may technically continue past the digital-consent threshold.

  But supervision does not substitute for the conversation a parent is responsible for having.

  The platform does not know the family context.

• It does not survive a forgotten password and a re-created account. Apple documents account recovery, and a fresh account begins the age derivation again [source: apple-region-rules].

The single sentence version: the age on an account is a signal that the platform uses to apply defaults. It is not a verdict on the child. It is not a replacement for the parent.

Talking about it

A birthday is the moment when “I set this up” becomes “what do we keep”.

Three small habits make the conversation land without becoming a control story:

• Tell the child what is about to change, and why. The platform will notify them anyway [source: google-supervision-13]. If you describe the transition first, the notification confirms rather than surprises.

• Frame the decision as a joint one, where it is. Continuing Family Link supervision past the local threshold is the child’s choice in Google’s documented behaviour, and the child’s cooperation makes it work [source: google-supervision-13]. Pretending the child has no say is both wrong and unsustainable.

• Name what stays and what goes. The rating ceiling may rise. The family group stays. Purchase approval may be lifted, or kept. The screen-time passcode, where it exists, is independent of birthday and continues until the parent removes it.

The editorial stance of this wiki is that parental controls are a layer, not a verdict, and that the birthday is the natural moment to revisit the configuration together with the child rather than around them.

Sources

• apple-region-rules — Apple Support, “Region-specific rules for managing an Apple Account”. Country thresholds for Apple Accounts [source: apple-region-rules].

• apple-appstore-age-ratings — Apple Developer, “Age ratings values and definitions”. The five-tier App Store rating system [source: apple-appstore-age-ratings].

• apple-dev-age-requirements — Apple Developer News, “Age requirements for apps in Brazil, Australia, Singapore, Utah, Louisiana”. State-level enforcement of age assurance on the App Store [source: apple-dev-age-requirements].

• apple-age-range-legal — Apple legal framing of the Declared Age Range signal [source: apple-age-range-legal].

• apple-age-range-support — Apple Support, “Share your age range with apps”. Parent and child controls for the age-range signal [source: apple-age-range-support].

• apple-declared-age-range — Apple Developer Documentation, “Declared Age Range”. The API and consent model through which a child’s age range is shared with apps [source: apple-declared-age-range].

• google-age-requirements — Google Account Help, “Age requirements on Google Accounts”. The primary source for the per-country minimum-age table [source: google-age-requirements].

• google-supervision-13 — Google Families Help, “How Google Accounts work when children turn 13”. Birthday transitions and the supervision-continuation rule [source: google-supervision-13].

• google-supervision-setup — Google Families Help, “Set up supervision to continue using your Google Account”. The continuation-of-supervision flow [source: google-supervision-setup].

• euconsent-gdpr-art8 — GDPR Article 8, the legal basis for the per-country variation in age of digital consent [source: euconsent-gdpr-art8].

• ofcom-age-assurance-2026 — Ofcom, “Use of Age Assurance Report 2026”. UK statutory evidence on the volume and type of age checks performed on children [source: ofcom-age-assurance-2026].

• roblox-age-estimation — Roblox, “Facial Age Estimation for Safer Chat”. The vendor’s own description of the global facial age estimation system and its age brackets [claim: roblox-age-estimation].

• www-biometricupdate-declared-age — BiometricUpdate (2026), “Apple updates Declared Age Range API for age assurance laws”. Secondary reporting on the rollout schedule of the API and the state-level enforcement dates [source: www-biometricupdate-declared-age].

• ageassurance-aatt-age-estimation-2025 — Australian Age Assurance Technology Trial, Part D — Age Estimation. Independent threshold evidence on facial age estimation immediately around 13+ and 16+ [source: ageassurance-aatt-age-estimation-2025].

[source: apple-region-rules] [source: apple-appstore-age-ratings] [source: apple-dev-age-requirements] [source: apple-age-range-legal] [source: apple-age-range-support] [source: apple-declared-age-range] [source: google-age-requirements] [source: google-supervision-13] [source: google-supervision-setup] [source: euconsent-gdpr-art8] [source: ofcom-age-assurance-2026] [source: roblox-age-estimation] [source: www-biometricupdate-declared-age] [source: ageassurance-aatt-age-estimation-2025]