← Parent pilotSafety & privacy

Controlled family launch

The Parent Pilot Guide

Begin with the founder household, verify the complete loop, then invite three to five families who understand the commitment: consistent adult supervision, honest evidence, and feedback that improves the system.

1

Adult previews

The parent reads the sample week and agrees that the public Site is an adult-facing curriculum preview.

2

Parent consents

Before a learner profile exists, the parent reviews data, safety, offline, and deletion choices.

3

Alias is created

Use a nickname such as Wolf 01—never the child’s full name, school email, diagnosis, or address.

4

Device is paired

A one-time six-digit code connects one family device to the parent-controlled learner space.

5

Domains are placed

Reading, spelling, writing, math, science, regulation, and movement each begin at their own prerequisite.

6

The week runs

The learner encounters, models, names, twists, and teaches back while the parent keeps evidence.

7

The parent reviews

Print or export attendance, artifacts, mastery status, and the next recommended node.

Invite families who

Fit the pilot

  • Will supervise young learners
  • Can test on an iPad or tablet
  • Will use aliases and protect private data
  • Will complete at least one full sample week
  • Will report confusion, breakage, and wins directly

Do not collect yet

Keep the perimeter clean

  • Child emails or passwords
  • Full legal names
  • Medical or disability records
  • District credentials
  • Payment information
  • Public rankings or social profiles

Current pilot sequence

Share this parent link now. The organizer then issues learner-app access only after the parent consent, alias, and device-pairing flow is ready for that family.

Open the sample week