The school chooses access.
Your institution decides which approved systems, records, and staff roles each agent can use.
Privacy and security for student information
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.
Nostra
Leonardo
Maya
Sherlock
Athena
MarcusStudent information first
School-controlled access
No public chatbot
Human approval
The non-negotiable
The Crew is useful only if the school remains in control of the information, the permissions, and every decision.
Your institution decides which approved systems, records, and staff roles each agent can use.
Processing uses enterprise contractual terms that prohibit your content from being used for model training.
The Crew prepares and returns work. A responsible person approves anything important before it moves.
Useful because access is limited
The crew does not get a blank check to roam through your school. Your institution chooses the sources, permissions, and people involved.

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

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

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

Commitments, responsible people, deadlines, and completion status.

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

Approved calendars, walkthrough plans, coaching time, and staff priorities.
One request, from question to approval
A staff member uses the approved chat app to ask a question or request prepared work.
The on-site system retrieves only the school sources and permissions connected to that request.
The request is processed under contractual zero-training terms, not through a public consumer chatbot.
The crew returns an answer or draft. Nothing important is sent, filed, or published without human approval.
The question every principal asks
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
The school information their existing role and permissions allow.
Holds approved mail, files, records, and the permissions that govern the crew.
Logged setup and maintenance access. Student or staff content is not visible by default.
Nothing. They are not part of the system.
Processes requests under contractual terms that prohibit storing your content for model training.
For your IT lead
No slide deck required. Your IT lead can confirm the architecture, contract, and controls in one technical review.
One on-site machineSchool-controlled infrastructure on the school's network.
No consumer AI toolsOnly an enterprise provider under zero-training terms.
Approved staff accessOne chat app governed by existing roles and permissions.
Logged supportMaintenance access is limited and auditable.
Human controlImportant actions require a person to approve them.
Private by design. Useful by permission.
We will show both of you exactly how the crew works.
Book a 20-minute demo