Use less data.
Protect what families share.

A parent or guardian may provide an email address, first name and authentication information to create and secure the family account. Password authentication is handled through our authentication provider; KML does not display a parent's password to a child profile.

A child profile can use a nickname, broad age band, interests and avatar. We deliberately avoid requiring a child's email address, phone number, school, exact birth date or precise location for the mission experience.

For signed-in families, mission progress, responses needed for resume, completions, XP, streaks, badges and Whole Child evidence may be securely stored with the family account so progress can follow the child. A limited browser copy may also be used for continuity and is isolated by child profile.

KML may record product events such as starting, viewing or completing a mission so we can find broken experiences and understand whether the beta is useful. We do not treat an ordinary return visit as proof that a child returned voluntarily.

KML does not use a child's activity to build a behavioral advertising profile. Recommendations inside KML may be based on the mission, skill, age band or interests selected for the learning experience.

Children should not enter payment information. Purchases and subscriptions belong in the grown-up account. Secure live checkout is not enabled in the current private beta.

The parent or guardian owns the family account and should be able to request access, correction or deletion of family data. Final public-launch controls, retention periods and jurisdiction-specific consent flows will be completed before broad public release.

KML uses authenticated requests, database access controls and ownership checks to separate family records. We minimize child identity data because the safest unnecessary data is data we never collect.