No open chat
The first public utility excludes child-to-child chat, stranger contact, direct provider messaging, and public posting.
Child safety
Safety is part of the product, not a badge.
The first public utility has a narrow boundary: finite activities, visible stopping, no open child communication, and no hidden health conclusions from play.
This page records the release standard. It is not evidence that an unreleased route, vendor, or future capability has passed review.
T1 product boundary
What does not belong in ordinary Play.
No public child profile
A child should not need a public name, photograph, follower count, location, or searchable profile to use ordinary Play.
Stopping is allowed
A child can decline, pause, or stop. Completion, streaks, celebrations, or adult prompts must not remove that choice.
Finite feedback
Feedback can be cheerful and clear without shame, harsh failure sounds, endless pressure, deceptive countdowns, or punishment for leaving.
Adult context
Caregiver-facing instructions explain the purpose, likely duration, controls, data boundary, limitations, and when a different kind of help may be appropriate.
No hidden inference
Ordinary game behavior must not be converted into a diagnosis, attention score, mood profile, personality judgment, or treatment recommendation.
Child choice
Stop, help, and another way to join.
Child-facing expectations
- A visible way to leave or stop.
- Concrete instructions that do not depend on unfamiliar icons or sound alone.
- A non-punitive response to a wrong action or a decision not to continue.
- Alternatives when sound, motion, reading, touch, or a visual mechanic creates a barrier.
- No request to share a real name, private story, diagnosis, photograph, or urgent concern inside ordinary Play.
Adult-facing expectations
- Do not use a game result as a developmental or mental-health conclusion.
- Respect a child’s decision to stop and avoid forcing completion for data or rewards.
- Use the appropriate local professional, safeguarding, medical, or emergency route when the concern is outside an everyday activity.
- Do not place sensitive child information in ordinary support or correction messages.
Verification
Safety rules still require implementation checks.
Concerns and urgent situations use different routes.
For a non-urgent concern about a page or product boundary, use the adult contact route. Do not include sensitive child information.