ElizaChat: Institutional Authorization Is Not Student Consent
Evidence-Based Responsibility Reconstruction℠ Case Study
ElizaChat markets its platform to school districts as continuous AI mental-health support for students, including evenings, weekends, and holidays when counselors are unavailable. The company says students who need immediate help are automatically escalated to human counselors.
Utah authorized ElizaChat to test that promise in participating school districts. Schools decide whether to provide the system. ElizaChat decides when a student’s behavior qualifies for human intervention. The company’s terms allow a school to accept the service on behalf of parents.
However, the student does not design the system, approve the intervention threshold, select the underlying AI, authorize the Utah pilot, or negotiate the terms governing what happens after harm.
Yet the student bears the consequences.
This case applies Evidence-Based Responsibility Reconstruction℠ to the public record surrounding ElizaChat: the state agreement authorizing the pilot, ElizaChat’s school-facing claims, its Terms of Service, and its Privacy Policy. No individual injury is needed to see the structure. The governing documents already establish where authority sits, and who is the victim if harm occurs.
ElizaChat Decides When a Student is Connected to a Human
The Agreement Gives ElizaChat the Threshold
Section XVI(A) states:
“Users who demonstrate high risk behavior, as determined by Participant,” must be connected promptly with ElizaChat’s clinical team, emergency contacts, and a licensed psychologist or therapist.
The words “as determined by Participant” control the safeguard.
ElizaChat is not simply operating the communication system. It decides whether a student has crossed the threshold that brings outside human expertise and judgment into the interaction.
| If ElizaChat classifies the student as high risk | If ElizaChat does not classify the student as high risk |
|---|---|
| The escalation process activates. | The escalation process does not activate. |
| Clinical personnel and emergency contacts may be notified. | A counselor, parent, school official, or emergency contact may never be notified. |
| The system creates an escalation record. | The missed student may leave no escalation record at all. |
The existence of a human escalation process does not establish that students who need intervention will receive it. It establishes only that ElizaChat has a process.
The System Decides Whether Its Own Safeguard Begins
What the Agreement Identifies
Schedule B identifies an NLU system that filters inputs and outputs and a training loop involving a clinical advisory board. That is more methodological information than a bare claim that safeguards exist.
It is not validation.
What the Public Record Does Not Show
The public record provides no demonstrated accuracy rate, false-negative rate, independent study, or evidence showing how the system performs when students express danger indirectly, ambiguously, sarcastically, or in language the system was not trained to recognize.
The central control therefore depends on the system correctly recognizing the condition that is supposed to trigger supervision.
Disclosure Is Not The Same as Student Consent
What the Agreement Requires Students to Acknowledge
Section VI(G) requires ElizaChat to disclose that:
- The application uses generative AI.
- The system is undergoing testing and may not function as intended.
- Student data will be used in specified ways.
A user must acknowledge receiving those disclosures before accessing the application.
That is a click-through acknowledgement. It is not evidence that the student meaningfully chose the institutional arrangement.
What the Student Never Decided
By the time the student sees the disclosure, Utah has authorized the pilot, the school has chosen to provide the system, ElizaChat has established the operating conditions, and the adults involved have determined that the student will encounter the technology.
| What the student can acknowledge | What the student did not control |
|---|---|
| That the application uses generative AI | Whether the school adopted it |
| That the system is being tested | Whether students should be the test population |
| That the system may not work as intended | Which failures were considered acceptable |
| How the company says data will be used | Which model, threshold, monitoring process, and escalation design govern the interaction |
Disclosure is not choice. Acknowledging that an AI system may fail is not the same as authorizing its use in a school mental-health setting. Clicking a box does not transfer the institutional decision to the student.
ElizaChat’s Terms of Service also allow a school or district to accept the terms on behalf of students’ parents and provide consent for collecting student information. The terms assign parents responsibility for their minor children’s conduct whether or not the parent authorized that conduct.
The structure converts authorization by Utah, the school, and ElizaChat into purported consent by the person with the least control over the arrangement.
Institutional authorization is converted into purported student consent, while the consequences are transferred to the student.
A Harm-Reporting Duty Still Depends on ElizaChat Recognizing the Harm
Utah Created a Broader 24-Hour Reporting Duty
The agreement does not limit all reporting to whether ElizaChat crossed into the licensed practice of mental-health therapy.
Section VI(I)(3) separately requires ElizaChat to notify the Office within 24 hours of incidents that result in harm to a user’s health, safety, or financial well-being.
That broader duty matters. A student or parent also retains the right to bring a claim against ElizaChat. Schedule A(F) makes clear that Utah’s enforcement relief does not eliminate claims by individual users or their parents or guardians.
The agreement therefore does not erase every remedy after harm.
ElizaChat Still Controls the First Classification
When ElizaChat Recognizes Harm
The reporting obligation begins only when the event is recognized as harm.
When ElizaChat Does Not Recognize Harm
If ElizaChat fails to classify a student as high risk, no escalation may occur. If the company does not learn of a later injury, does not connect it to the interaction, or does not classify the event as reportable harm, the 24-hour notice does not generate.
| What the agreement requires | What issues remain unresolved |
|---|---|
| ElizaChat must report known harm within 24 hours. | How harm that ElizaChat failed to detect becomes known to Utah. |
| Utah may inspect records after a complaint or suspected incident. | How Utah discovers students who were never escalated and never complained. |
| ElizaChat must address identified failures and attempt to prevent recurrence. | Who independently determines whether the failure was identified completely. |
| Students and parents retain the right to seek a remedy. | Whether they possess the records needed to prove what happened. |
The error in the earlier framing would be to say a broader reporting duty does not exist. It does.
The actual failure is more important: the duty still depends on the same company-controlled recognition process that governs escalation.
A Separate Licensing Incident Is Not the Same as Student Harm
Schedule A also defines an incident around whether ElizaChat enters the licensed practice of mental-health therapy. When the Office or Division determines that the application crossed that professional boundary, ElizaChat receives time to correct the problem and must address resulting harm.
That process protects a licensing boundary. The 24-hour provision addresses broader harm. Neither provision establishes an independent mechanism for discovering an injured student whom ElizaChat never identified as high risk.
A missed escalation might later be called a classification error, an inaccurate output, a monitoring failure, or unexpected AI behavior. Each label could describe part of the event.
None would establish who owned the decisions that produced it.
Responsibility Moves Away From the Student’s Decision-Makers
Authority and Consequences Are Distributed Differently
| Actor | Authority or control | Position after harm |
|---|---|---|
| Utah | Authorized the pilot, reviewed the rollout, and could approve expansion | Disclaims endorsement and receives protection from claims arising from ElizaChat’s operation |
| School district | Chose whether to provide the system and could accept terms on behalf of parents | Did not design the AI or control its internal classifications |
| ElizaChat | Designed and operated the system, controlled the intervention threshold, and held the operating evidence | Its terms attempt to limit responsibility for AI outputs and resulting losses |
| Parent or guardian | May receive notice or be represented by the school’s acceptance | May not have directly authorized the arrangement and lacks control over the system |
| Student | Supplies the sensitive information and experiences the system’s decision | Bears the consequences despite controlling none of the institutional conditions |
Authority remains institutional. Risk does not.
Utah’s Relief Is Narrower Than a Complete Immunity
Utah’s agreement says the pilot is not a state endorsement or approval of ElizaChat’s technology. ElizaChat must protect the Office and the Division of Professional Licensing from claims, losses, and expenses arising from the work.
But Schedule A(F) preserves claims brought by students and their parents or guardians against ElizaChat. Utah’s regulatory relief concerns enforcement of the licensed-therapy boundary; it does not immunize ElizaChat from individual claims.
That precision strengthens the responsibility finding. Utah authorized the operating conditions. ElizaChat retained responsibility for the system. Students retained a possible remedy. None of those facts establishes that an injured family would possess enough evidence to reconstruct the failure.
ElizaChat’s Terms Narrow the Practical Path
ElizaChat’s terms describe the company as a technology platform rather than a healthcare provider. They say the service is not appropriate for emergencies, warn that AI outputs may be inaccurate, and place reliance on those outputs at the user’s risk.
The terms attempt to limit responsibility for AI inputs and outputs, exclude categories of damages, cap total responsibility under the terms, require individual arbitration, and prohibit class and representative proceedings.
The right to bring a claim is therefore not the same as a clear path to proving a claim.
ElizaChat Controls the Evidence Needed to Explain What Happened
The Company Holds the Interaction Record
ElizaChat collects account information, conversations, device information, usage activity, emergency-contact information, and system interactions. Its Privacy Policy says relevant conversation context may be shared with school officials, parents, law enforcement, or other authorities when the company determines reporting is necessary.
The company also controls the operating evidence:
- What the student entered.
- What the AI returned.
- How the conversation was classified.
- Whether a safety threshold activated.
- Whether an alert was generated.
- Who received the alert.
- Whether a clinician became involved.
- What ElizaChat reported to Utah.
- Which excerpts were selected as examples of successful or unsuccessful behavior.
The Evidence Rules Do Not Establish Independent Possession
Utah’s Access Begins After Visibility
Utah may request records after a complaint or an action reasonably likely to qualify as an incident. That access begins after the potential failure becomes visible to Utah. The agreement does not give Utah an independent mechanism for discovering students whom ElizaChat failed to identify.
The Retention Rule Is Not Clear
The public documents also provide different descriptions of what evidence survives. ElizaChat’s Terms of Service say some user content and health information may remain after account termination or deletion. Its Privacy Policy says account deletion permanently erases associated data except for information previously disclosed through mandated reporting.
Those statements do not establish a reliable preservation rule for an investigation after harm.
Private Disputes Can Conceal Patterns
Individual arbitration can fragment the evidence further. A student’s dispute may remain private and separated from similar claims. That makes it harder for families, schools, researchers, or the public to identify a pattern that ElizaChat can see across its records.
ElizaChat’s explanation would be evidence. Utah’s review would be evidence. A school’s account would be evidence. None should be accepted as the responsibility finding.
What the Public Record Establishes—and What Remains Unresolved
| What the public record establishes | What remains unresolved |
|---|---|
| Utah authorized the pilot and controlled phased expansion. | Which individual approved expansion at each phase and what evidence supported that decision. |
| Participating school districts determined whether students would receive access. | Which school officials accepted the deployment conditions and what parents were told. |
| Dave Barney signed the agreement for ElizaChat. | Who designed, validated, and approved the high-risk threshold. |
| ElizaChat controlled the threshold that determines when a student reaches a human. | The threshold’s false-negative rate and performance across different forms of student expression. |
| The agreement identifies an NLU filter and clinical-advisory-board training loop. | The model, model version, configuration, external services, validation record, and independent testing. |
| ElizaChat created and held the operating record. | Whether an outside investigator could recover the complete record after harm. |
| Students and parents retained the right to bring claims against ElizaChat. | Whether they could obtain enough evidence to prove the responsibility chain. |
| ElizaChat had a 24-hour duty to report harm. | How Utah would discover harm that ElizaChat failed to recognize or report. |
| Utah, ElizaChat, and schools all exercised institutional authority before deployment. | Who formally accepted the remaining risk to students. |
These are not peripheral questions. They are the connections required to establish who controlled the conditions under which the AI acted.
Where those connections cannot be recovered, responsibility remains unresolved by design.
Responsibility Reconstruction Finding
ElizaChat presents human escalation as the safeguard protecting students. But ElizaChat controls the threshold that decides whether the safeguard begins.
Utah authorized the pilot, approved the structure, and retained oversight authority. It did not accept responsibility for operating the technology.
Schools chose whether to introduce the system and could accept terms on behalf of parents. They did not design the AI or control its internal risk decisions.
ElizaChat operated the system, controlled the intervention threshold, and held the evidence. Its terms nevertheless attempted to narrow its responsibility for inaccurate outputs and resulting harm.
Students controlled none of those institutional decisions.
The structure does not produce a clear accountable owner after harm. It produces a sequence of institutions pointing to the next actor, a technical label describing the failure, and a student left with the consequences.
Naming the event a missed escalation or classification error would explain the mechanism of failure. It would not establish who authorized the threshold, who validated it, who permitted deployment, or who accepted the risk to students. Naming the error is not owning responsibility.
Evidence-Based Responsibility Reconstruction℠ is necessary because the agreement, the terms, the privacy policy, and the company’s incident report would each show only part of the responsibility chain. The process must reconstruct how authority, control, consent, evidence, and risk were distributed across Utah, ElizaChat, the school, the parents, and the student.
The final finding is not that no one participated.
It is that the institutions with authority retained control, while the student who did not authorize or meaningfully consent to the system was left to absorb its failure.