Virtual Round Table · Jul 22

View the event
Cambridge and Noesis Push to Make Human-Like AI Companions Adult-Only, With No Exemption for Schools
AI & ML

Cambridge and Noesis Push to Make Human-Like AI Companions Adult-Only, With No Exemption for Schools

A Cambridge-backed whitepaper wants human-like AI companions treated as adult-only by default, and it pointedly refuses to exempt education, reframing student-facing chatbots as a product-safety problem.

PublishedJuly 16, 2026
Read time6 min read
Share

What the framework proposes

A new whitepaper is pushing to reclassify how children encounter conversational AI. Published July 16 by the Noesis Collaborative and the Leverhulme Centre for the Future of Intelligence at the University of Cambridge, it argues that AI products designed to mimic a rich, human-like inner life should be adult-only by default. The target is a specific category: systems built to encourage emotional dependence or to form ongoing social and emotional bonds with users. The recommendation stops short of a blanket ban on AI for young people and instead sets a default restriction on the most anthropomorphic, relationship-oriented products.

The distinction is deliberate. The authors separate task-focused tools from companions that simulate feelings, memory, and continuity of relationship. Age-appropriate versions would still be permitted, gated behind privacy-preserving age assurance, so a fifteen-year-old could use a suitably constrained product. Ron Ivey, founder and chief executive of the Noesis Collaborative, co-authored the paper. The framing borrows from how societies already treat products with real developmental risk, setting a default of caution and requiring evidence before children are exposed. For a field used to shipping first and governing later, that inversion is the whole point.

No safe zone for education

The most consequential line for our readers is that the framework refuses to carve out education. Many vendors have assumed that a learning purpose sanitizes an AI companion, that a tutor persona is inherently safer than an entertainment one. The authors reject that. They warn that risks can emerge even when children initially engage a generative AI tool for legitimate study, particularly once the product is designed to build an emotional relationship. The mechanism matters more than the label on the app. A study assistant that fosters dependence carries the same concerns as a companion marketed for friendship.

This lands directly on a fast-growing edtech design pattern. Personalized AI tutors increasingly lean on warmth, encouragement, and persistent memory to drive engagement, the same properties that make a companion sticky. The paper effectively tells builders that engagement mechanics have a safety cost when the user is a child. We think this is the uncomfortable insight the sector has avoided. Retention features that look benign in a corporate learning tool take on a different character when deployed to a nine-year-old, and the framework asks vendors to design for that difference from the start.

A pharma-style audit model

On remedies, the whitepaper reaches for a regulated-industry analogy. It proposes pre-market and post-market safety audits modeled on the standards applied to pharmaceuticals and consumer goods. In practice that means a product aimed at or accessible to children would need to demonstrate safety before release and remain under monitoring afterward, rather than relying on post-hoc complaints. Age-appropriate product tiers would be allowed, provided they pass through privacy-preserving age assurance instead of the self-declared birthdays that gate most services today. It is a structural answer to a structural problem.

For anyone who builds or buys software, the operational implications are heavy. Pre-market audits imply documentation, testing protocols, and independent review that most edtech startups have never budgeted for. Post-market monitoring implies telemetry and incident response tied to child safety, a capability closer to medical devices than to typical SaaS. We are skeptical that a voluntary framework moves the market on its own. Its value is as a template that regulators can lift, and as a due-diligence checklist that cautious school districts and enterprises can start applying to any student-facing product now.

The scale that forces the question

The urgency rests on adoption data the authors put front and center. They cite that 72 percent of US teens have used AI companions, and that 24 percent of those users have shared personal information with them. On the younger end, 75 percent of European children aged nine to sixteen have used generative AI. These are not fringe behaviors. They describe a majority of young people already in regular contact with systems that were never designed around child development or data minimization, often without a parent or teacher aware of the specifics.

Those numbers reframe the debate from hypothetical to remedial. When a majority of teenagers already share personal details with systems that simulate human relationships, the question stops being whether to allow access and becomes how to constrain what already exists. That is a harder problem, and it favors the framework's default-restriction stance. We would also note that the data creates pressure in the opposite direction. Products with tens of millions of young users have every incentive to resist age gating that shrinks their base. The tension between child safety and engagement economics will define the next year of policy.

Opinion and moral development

The authors go beyond privacy and dependence to a subtler worry. Henry Shevlin, an AI ethicist at Google DeepMind and associate director at the Leverhulme Centre, pointed to influence: "Another major concern is the role these systems may play in shaping opinions and moral development." That is a claim about formation, which goes further than privacy or dependence. A companion that a child talks to daily, that remembers past conversations and responds with apparent warmth, occupies a position of influence that a search box never held. The paper treats that influence as a governance question rather than a curiosity.

We find this the most defensible part of the argument and the hardest to regulate. Measuring whether a chatbot shifts a child's values is far messier than measuring a data leak. Yet the concern maps onto real product decisions: what a model refuses to discuss, how it frames contested topics, and whose norms are encoded in its guardrails. For schools deploying AI tutors, this is a reminder that model behavior is a curricular choice by proxy. Districts that scrutinize textbooks for bias have every reason to scrutinize the assistants now answering the same students' questions.

The regulatory backdrop and buyer takeaway

The whitepaper arrives as harder law is forming. The EU AI Act's Annex III is set to classify student-monitoring AI as high-risk from August 2026, and academic bodies have already pulled back from AI-vulnerable assessment formats. A voluntary Cambridge-backed framework does not carry legal force, yet it feeds a regulatory direction that is clearly tightening around minors and education. Vendors betting that the current permissive environment will hold are reading the trend backwards. The momentum is toward audits, age assurance, and accountability for how student-facing systems behave.

For edtech buyers, the practical move is to adopt the framework's questions before regulation forces them. Ask whether a student-facing product is engineered to build emotional dependence, what data it collects from minors, whether it can prove age-appropriate design, and how its behavior is monitored after launch. Those questions cost nothing to ask and expose a great deal. The companies that can answer them will clear the bar that Ohio, the EU, and now Cambridge are all raising from different directions. The ones that cannot are building on ground that is about to move.

Tagged#news#edtech#education#learning#lms#ai-education#ai-companions#child-safety#cambridge-leverhulme#noesis-collaborative#student-safety#product-safety#eu-ai-act#ai-governance