🔐 Privacy by design • Collect less • Explain clearly • Put adults in control
PRIVACY PRINCIPLES

Use less data.
Keep the value.

KML is being designed so children can learn without being asked for information that is not necessary for the experience.

Child profile

Current beta: nickname, avatar choice, mission responses, scores, streaks, badges and progress stored locally on the device/browser.

Not needed in child mode

No child email address, phone number, exact home address, precise location, advertising identifier or social profile is required for missions.

Learning responses

Written mission responses are used to resume progress and provide feedback. In the current beta they remain in local browser storage unless the family deliberately exports or later opts into a cloud account.

Commerce

Children do not enter payment details. Purchases, subscriptions, billing and adult contact details belong to parent/guardian accounts when secure checkout is connected.

Recommendations

KML may recommend a book or activity because it matches a mission, category or skill. That is contextual product discovery, not behavioral advertising across unrelated sites.

Reports

Parent progress reports should summarize learning activity, strengths, effort and suggested practice. Email delivery should only begin after an adult account explicitly opts into a report cadence.

Future cloud accounts

Cross-device sync will require a secure backend. The planned architecture separates child learning profiles from adult identity, billing and communication data and should provide parent controls for access, correction, download and deletion.

Beta note

This page describes the product’s privacy design principles and current beta behavior. It is not a substitute for the finalized legal privacy notice, consent flow, retention schedule and jurisdiction-specific review that should be completed before a full public launch.