A little learning. Carefully handled.

This is a development privacy draft, not a claim of legal compliance. Local demo use should involve fictional profiles only.

What the demo stores

A made-up nickname, an age range, selected avatar, answers and learning results, reward history, and parent preferences. Data is saved in your browser’s local storage. It is not synced to a learning backend.

Audio and network use

Sound effects are generated on your device. Listening uses browser speech synthesis, which may use a voice provider depending on your browser. No microphone recording or pronunciation assessment is performed. Fonts and illustrations are bundled locally. Hosting services may record ordinary technical request logs.

Your choices

Parents can export the local record, delete an explorer and their progress, or reset all demo data. Anyone using this browser can access demo parent settings; these are not authenticated controls.

Accounts and competitions

If a developer configures Supabase, the parent authentication forms send parent credentials to Supabase Auth. Cloud child activation is disabled. Demo opponents and optional comparison entries are fictional. There is no open chat or public child directory.

Before production use with children

The operator must supply a legal identity and privacy contact, establish jurisdiction-specific parental consent, verify access policies and data retention/deletion, review subprocessors and hosting, and conduct legal and security review. COPPA or GDPR-K compliance is not automatic.

External notifications

External push and email delivery are disabled. In-app reminders are optional and controlled by a parent.