Inspire Early Learning

Walk into almost any modern early learning center and you will see a familiar ritual: a teacher holding a tablet, quietly tapping notes as a child stacks blocks, hums along to a morning song, or sounds out the first letter of her name.

Some of what she records is a milestone. Some of it is a mood. Some of it is a passing moment that will be compared, over time, against thousands of others—weighed by an algorithm, benchmarked against peers and stored somewhere the child will never see.

And so, a question that used to live quietly in policy papers is now sitting in every classroom: who owns a four-year-old's learning profile and assessments?

It's a question our industry has been slow to ask out loud. In K–12 and higher education, the conversation about student data is at least underway—shaped by FERPA, state privacy laws and years of high-profile breaches. But even there, the foundation is shakier than most families realize. FERPA is widely regarded as one of the most structurally outdated education laws on the books, and even its defenders concede it was built for a world that no longer exists. It was signed into law in 1974, when an “education record” meant a manila folder in a registrar's office. It’s a law built for filing cabinets.

But early childhood education occupies a quieter, less-regulated space. Our learners cannot read terms of service. They cannot opt out of a check-in sheet, an AI-assisted observation tool, or a parent app that records what they ate, how they slept and how often they cried. They simply arrive each morning, full of curiosity and leave each afternoon having generated data they will never control.

The four-year-old has no lobby.

Developmental data is uniquely sensitive. Unlike a math score or an attendance record, it describes a child's emerging self—language, regulation, social development, sensory preferences, family dynamics. It can surface a delay before a pediatrician does. It can hint at a diagnosis before a family is ready to hear it. And increasingly, it is being collected, analyzed and stored by platforms built to serve many masters at once: the center that pays for the license, the parent who wants daily updates, the vendor that wants to improve its product and the investor who wants to grow the business.

“Our job as educators, operators and technology partners, is to protect the pen.”

Each of those stakeholders has a legitimate interest. None of them is the child.

When ownership is unclear, power isn’t neutral—it defaults to the system holding the data.

As ECE leaders, we need to be honest about the tensions baked into the tools we’ve adopted—most of them quickly, and many of them without a clear answer to what happens to a child’s profile when they age out, switch centers or when the platform itself is sold. Consider the questions we rarely ask before we click “accept”:

Portability: When a family leaves our program, can they take their child’s developmental record with them in a usable format—or does it live forever inside a vendor’s dashboard?

Retention: How long is a toddler’s observational data stored, and who can access it five, ten or fifteen years from now?

Secondary use: Is anonymized child data being used to train AI models, build benchmarks, or market new products? Did the family knowingly consent to that use, or was it tucked inside a privacy policy written for adults?

Profiling: Are we quietly building early “risk scores” for three- and four-year-olds—profiles that could shape the classrooms they’re placed in, the interventions they receive, or how risk is calculated about them long before they understand what any of it means?

Deletion: If a parent asks us to erase their child’s profile, can we actually do it—across every integrated system, every backup, every partner?

These are not hypothetical concerns. They are operational realities that ECE leaders are navigating today, often without a playbook and often without the legal infrastructure our counterparts in higher education take for granted.

What stewardship should look like

The good news is that early childhood has always been a field defined by trust. Families hand us their children. The least we can do is hand back a thoughtful answer about what happens to the information we collect about them.

That starts with language. We should stop talking about “our data” and start talking about the child’s data, held in trust.

It continues with procurement. Before a center signs with a new platform, developmental data ownership, portability and deletion deserve the same rigor we apply to tuition management or payroll—not a skim of a standard contract.

And it extends to families. Parents deserve a straightforward explanation of what is collected, why, who sees it and how to get it back.

At minimum, families should be able to access, download and request deletion of their child’s full developmental record—without friction, without delay and without penalty.

Vendors have work to do here, too. The platforms that will earn long-term loyalty in ECE are the ones that treat developmental data the way a pediatrician treats a medical chart—as something that belongs to the child and the family, not to the software.

Technology in early childhood should extend the village that raises a child, not quietly privatize it. A four-year-old’s learning profile is not a marketing asset, a training set, or a proprietary benchmark. It is the earliest chapter of a person’s story.

Our job—as educators, operators and technology partners—is to protect the pen.