Parent-facing explanations cannot replace child-facing expression

What it is

Children's products address two audiences: guardians (responsible for policy, data, and risk) and children (who actually use the product and actually bear the consequences). Child-facing communication means the latter must directly receive information proportionate to their age — what will happen, where data goes, what can be refused — rather than only a page shown to parents. The equation "telling the parent counts as telling the child" fails: intermediary transmission attenuates, rewrites, and delays, and children hold a direct right to know what happens to them.

Why it happens

Parental mediation fails along three paths. Transmission: policies written for parents are never (and need not be) relayed as terms to children; even when relayed, they pass through the parent's comprehension and phrasing, and the load-bearing specifics (when the camera turns on, when others can see) drop out. Timing: parents read at registration, children use at every moment — the explanation must appear at the moment the camera opens or "public" is tapped; a registration-time parent page cannot help. Consent structure: in a graduated-consent system, children hold the assent role — and assent material must be comprehensible to the child; supporting a child's assent with parent-tier documents leaves the assent step idling. Fully relying on parental mediation also amplifies family inequality: parental engagement varies, protection varies with it, and outsourcing notice to families allocates the right to know by household circumstance.

Where it stops holding

Child-facing expression is not simplifying terms into easy words alone: information volume must stay within comprehension limits — one thing at a time, directly tied to the current action; the full policy still needs a parent-facing version, so the two run parallel, not as substitutes. Intensity tiers by age: graphics and voice for preschoolers, plain sentences approaching adult phrasing for teenagers. For some content (sensitive details of safety incidents) parent-first sequencing is legitimate — the child-facing step comes second, but is never skipped.

Applying it

• Explain in place at critical action moments: turning on the camera, first public posting, adding a stranger — an age-fit note on "who will now see what," rather than a bundled notice at registration.
• Build a child-language asset library: per-age-band templates (preschool graphics + voice, primary simple sentences, secondary plain sentences) for common notices, updated in sync with the adult versions.
• Design child-tier settings and consent screens separately: icon + voice + one-sentence consequence, with "what is this?" answerable within the same screen before acting.
• Verify: comprehension-test the target age band — after demonstrating the in-the-moment explanation for a key action, ask "who will see that, and what if you don't want it?"; failure on either question invalidates the expression — redo it.

Related

• Same group: P4.05.5 Consent capacity stratifies with age, not acquired in a single day · P4.05.1 Defaults must be set for the youngest plausible user
• Adjacent: O2.02 Explaining data use · T1.07 Readability and target readers
• Search terms: child-facing communication · age-appropriate disclosure · in-the-moment explanation