What KML needs—and what it does not.
Kid Mission Lab is designed to use the least child information practical for the learning experience.
A parent or other authorized adult owns the family account. A child profile sits underneath that adult account.
A parent-approved nickname or first name, broad age band, preset avatar, interests, learning preferences, mission responses, progress, XP, badges and skill evidence.
A child email address, public profile photo, exact home address, precise location, school name, phone number, open biography or public contact information.
No. KML does not provide public searchable child profiles, follower counts, open comments or unrestricted child direct messaging.
No. KML does not use a child’s activity to build a behavioral advertising profile.
The family account can see its own child records. A teacher should only see a child after the family approves that classroom connection. School-scale permissions require additional role and legal review before broad adoption.
Purchases, subscription changes, account controls and external sharing belong in the adult layer, not the child experience.
The current family architecture includes an authenticated data-export workflow and an account-deletion request workflow. Production deletion timing and retention language still require final policy and legal review.
Important beta note
This page explains KML’s current product design and privacy principles. It is not a claim that Kid Mission Lab has completed every legal requirement that may apply under COPPA, FERPA, state student-privacy laws or school contracts. Qualified legal review is required before broader school-scale release.
Read the full privacy principles →