Privacy and security for student information

STUDENT DATA.
PROTECTED AT THE CORE.

Before an AI agent saves one minute, the system must protect the student and staff information entrusted to your school. Your institution controls access, public chatbots are never used, and every important action stays with a person.

School controlledSTUDENT
INFORMATION
Protected core
Agent NostraNostra
Agent LeonardoLeonardo
Agent MayaMaya
Agent SherlockSherlock
Agent AthenaAthena
Agent MarcusMarcus

Student information first

School-controlled access

No public chatbot

Human approval

The non-negotiable

Student information is never the price of automation.

The Crew is useful only if the school remains in control of the information, the permissions, and every decision.

01

The school chooses access.

Your institution decides which approved systems, records, and staff roles each agent can use.

02

Your data does not train AI.

Processing uses enterprise contractual terms that prohibit your content from being used for model training.

03

People keep authority.

The Crew prepares and returns work. A responsible person approves anything important before it moves.

Useful because access is limited

Each agent sees only the work it needs.

The crew does not get a blank check to roam through your school. Your institution chooses the sources, permissions, and people involved.

Agent Nostra
Agent Nostra

Calendar and deadlines

Approved calendars, district requests, coverage needs, and due dates.

Agent Leonardo
Agent Leonardo

Meetings and commitments

Approved agendas, notes, decisions, owners, and follow-up dates.

Agent Maya
Agent Maya

Community communication

The context needed to draft messages that a person reviews before sending.

Agent Sherlock
Agent Sherlock

Open promises

Commitments, responsible people, deadlines, and completion status.

Agent Athena
Agent Athena

Approved school records

The files, email, and decisions your institution permits her to connect.

Agent Marcus
Agent Marcus

Leadership priorities

Approved calendars, walkthrough plans, coaching time, and staff priorities.

One request, from question to approval

What actually happens to your data.

01

You ask the crew.

A staff member uses the approved chat app to ask a question or request prepared work.

02

Your machine gathers context.

The on-site system retrieves only the school sources and permissions connected to that request.

03

Enterprise AI processes it.

The request is processed under contractual zero-training terms, not through a public consumer chatbot.

04

A person decides.

The crew returns an answer or draft. Nothing important is sent, filed, or published without human approval.

The question every principal asks

"My district banned AI chatbots. Doesn't that include this?"

No public chatbot ever sees your school data.

Consumer chatbot bans are aimed at tools where staff may paste sensitive information into a public service. Agents of Schools uses a school-controlled system and enterprise AI terms that prohibit model training on your content.

Your IT lead can review the setup, permissions, and contract before the crew touches school work.

Access, plainly stated

Who sees what.

WhoWhat they can see
You and approved staff

The school information their existing role and permissions allow.

Your on-site machine

Holds approved mail, files, records, and the permissions that govern the crew.

Agents of Schools support

Logged setup and maintenance access. Student or staff content is not visible by default.

Public consumer chatbots

Nothing. They are not part of the system.

Enterprise AI provider

Processes requests under contractual terms that prohibit storing your content for model training.

For your IT lead

Five things to verify.

No slide deck required. Your IT lead can confirm the architecture, contract, and controls in one technical review.

01

One on-site machineSchool-controlled infrastructure on the school's network.

02

No consumer AI toolsOnly an enterprise provider under zero-training terms.

03

Approved staff accessOne chat app governed by existing roles and permissions.

04

Logged supportMaintenance access is limited and auditable.

05

Human controlImportant actions require a person to approve them.

Private by design. Useful by permission.

Bring your IT lead.

We will show both of you exactly how the crew works.

Book a 20-minute demo