For Districts — KeepChatSafe

Rollout

Four stages, each with an exit ramp

Stage 1 · Review

Security & policy review

Your CTO, CISO, privacy officer, and counsel get the security review packet under NDA — architecture, data flows, DPA draft, control-to-evidence mappings. No commitment, no pilot pressure.

Stage 2 · Configure

Wellbeing criteria & identity

Your student-services team defines content thresholds and escalation routes in the Policy Studio; IT connects your existing sign-on — Google Workspace, Microsoft 365, Clever, or ClassLink. Every configuration decision is recorded as your school's attested policy.

Stage 3 · Pilot

Contained cohort pilot

One or two schools, defined grade bands, opted-in teachers. Weekly reporting on safety events, usage, and escalations — the evidence your board will ask for, gathered from day one.

Stage 4 · Scale

District-wide, on your calendar

Expansion timed to your semesters and PD days, with family communication templates aligned to your annual-notification process.

Teacher guiding students using devices in class

🏛️

The Founding District Program

A limited cohort for the 2026–27 school year. Founding districts co-design the wellbeing criteria library, get direct input on the rollout sequence, and lock founding-partner pricing. In return, we ask for honest feedback and a hard look at our claims — the kind of scrutiny that makes the product better for every district after you.

Ask about the founding cohort →

Procurement, without the friction

What we bring to your process

📄

Contract-ready paperwork

DPA drafted to AB 1584's required clauses, security questionnaire responses, insurance documentation, and a subprocessor list — delivered before you ask.

💰

A price in the first meeting

Per-student annual pricing with a district minimum, finalized with founding districts. You'll get a number in the first conversation, not after a pilot.

🤝

Straight answers on maturity

We're a young product from an enterprise AI-governance team, entering K-12 deliberately. What's shipped, what's roadmap, and what's not planned — labeled as such, in writing.

CTO & CISO FAQ

The questions we expect you to ask

Which AI models do students actually talk to?

Frontier models from providers whose terms permit serving minors with safeguards — reached only through our governance gateway, never directly. Providers whose developer terms prohibit under-18 end users are excluded by the routing layer itself. The current provider list, and each provider's minor-serving terms, are in the security review packet.

What happens when a student writes something concerning?

The conversation is not frozen — silencing a student mid-disclosure is the most dangerous possible response. The student receives a supportive, age-appropriate reply, and your designated staff receives an alert with context, following the escalation routes your district configures in the Policy Studio.

Can students bypass it and use consumer chatbots anyway?

On personal devices and cellular networks — yes, and no vendor can honestly tell you otherwise. KeepChatSafe governs what your district offers and pairs with your existing device and network controls. Our job is to make the sanctioned tool good enough that students use it.

Where does student data live, and who can see it?

In your district's isolated tenant under database-enforced row-level security. Conversation access is role-based and every access is logged. Retention follows your records policy. We don't sell student data, serve ads, profile students, or train models on their conversations.

How does this fit with our web filter and classroom management tools?

It completes them. Your CIPA filter governs destinations; your classroom tools govern attention; KeepChatSafe governs the AI conversation itself — the layer the other two were never designed to see. We integrate alongside, not instead.

What about students under 13?

Out of scope today, deliberately. Under-13 deployments carry COPPA consent duties and stricter provider data-retention requirements — a different product with different controls. We'd rather scope it honestly with your counsel than blur the line.

Is this available today?

We're enrolling a limited founding-district cohort for the 2026–27 school year. That's the honest status. Book a briefing and we'll show you the platform and the roadmap side by side — labeled which is which.

Who is behind KeepChatSafe?

An enterprise AI-governance team whose platform governs corporate AI use — policy enforcement, data-loss prevention, and audit for organizations with regulators to answer to. KeepChatSafe applies that same architecture to the highest-stakes users there are.

Adoption designed the way districts actually work