1
Official sources
Start with current Apple, Google, Microsoft, YouTube, Roblox, and device-manufacturer documentation.
Methodology · transparency · corrections
Useful guidance must be current, clear, and honest about its limits.
KidPhoneSetup separates platform facts from recommendations, checks technical claims against current official sources, and explains where a setting cannot provide complete protection.
The publication standard
Four layers, in this order.
No technical guide is ready because an AI draft sounds plausible. It needs a source trail, human judgment, technical checking, and a clear scope.
2
Founder judgment
Translate features into a starting recommendation for a specific child, device, and setup moment.
3
Technical check
Confirm terminology, paths, defaults, limitations, version requirements, and what the child sees.
4
Real questions
Use parent and customer confusion to improve explanations, ordering, examples, and troubleshooting.
Facts and recommendations are different
A platform fact describes how a feature currently works. A KidPhoneSetup recommendation explains what we would choose for the stated situation and why. The page should make that distinction visible.
Recommended
Use when the guide proposes a clear starting choice for the stated child and situation.
Consider
Use when readiness, family needs, school rules, or tradeoffs make the decision meaningfully individual.
Verify
Use when a protection may already be enabled or may vary by account, version, country, or device.
Not recommended
Use sparingly when the guide advises against a starting configuration for the specific scenario.
What gets checked
- Current setting name and navigation path
- Whether the control is on, off, or configured by default
- Age, account, device, region, and operating-system requirements
- What the parent controls and what the child sees
- Known limits, alternate routes, and cases the control does not cover
- What breaks when a family mixes ecosystems or adds a school-managed account
- When the recommendation should be reviewed rather than left unchanged
How AI is used
AI may help organize source material, group customer questions, propose outlines, find inconsistencies, and draft plain-language alternatives. It does not certify instructions, invent firsthand experience, choose a family’s values, or approve publication.
Technical instructions are reviewed by a person against current official documentation before publication. Where a step has not been directly tested, the content should say so instead of implying otherwise.
What this guidance cannot promise
No phone setting, content filter, supervision tool, or checklist can guarantee that a child will never encounter unsuitable content, unwanted contact, spending mistakes, or attempts to work around a limit.
The purpose of configuration is to make access more deliberate, reduce preventable mistakes, clarify expectations, and create a reviewable starting point.
Updates and corrections
High-change pages should show the platform/version and the last date the relevant instructions were reviewed. Material changes are recorded on the updates and corrections page. Dates are not refreshed merely to make old content look current.
Kevin McFaul is the founder and named editorial contact. If a buyer or reader finds a broken or unclear step, email kidphonesetup@gmail.com. The affected guide, public page, screenshots, and connected emails should all be checked together.