🛡️ Built for curiosity without turning kids into data products
TRUST & SAFETY

Kids should learn here.
Not be tracked here.

KML is being built around data minimization, parent control, age-appropriate communication and clear safety boundaries from the start.

Data minimization

Child mode asks for only what is useful to the experience. A nickname/avatar and learning progress are enough for the current beta. No need for a child email, phone number or precise location.

No behavioral ads to children

KML does not use a child’s activity to build an advertising profile. Product recommendations are tied to the mission or skill the child is using, not cross-site ad targeting.

Parent-controlled commerce

Kids can preview, wishlist and ask. Purchases, subscriptions, contact details and account controls stay in a grown-up zone.

Age-appropriate communication

Prompts use clear, supportive language without manipulative urgency, fear-based selling or pressure to spend money.

No open social feed

The current KML model has no public child profiles, open direct messaging or public comments. Future sharing features should default to closed, adult-managed spaces.

Report and review

Families and educators need a visible route to report unsafe, incorrect, inappropriate or broken content. The beta reporting queue is device-local until a secure support backend is connected.

MODERATION MODEL

What KML should moderate.

Because KML is not an open social network, moderation starts with content quality, child safety and controlled sharing.

Content safety

Review missions, books and recommendations for age fit, dangerous instructions, sexual content, bullying, hate, self-harm encouragement, exploitative commercial pressure and other child-inappropriate material.

Accuracy + quality

Flag misleading feedback, incorrect answers, broken mission logic, cultural stereotyping or material that does not match the stated age level.

Escalation

High-risk safety reports should be prioritized ahead of ordinary bugs. Adult account support and child-content review should be separated once the backend is live.

Designed to earn parent trust.

Trust is not a footer policy. It affects how KML stores progress, recommends products, asks for payment and communicates with children.

Parent View