Schools · Colleges · Universities
AI for education, privacy first.
Student records come with obligations, and staff and students need to know what is allowed. We settle both before the build. Then a CTO, an architect and engineers build AI for admissions, student services and operations that fits inside them.
What an institution needs first
Privacy and acceptable use, settled before anything ships.
Records stay protected
Each system is mapped against the obligations you already carry — FERPA, state student-privacy law, your data-sharing agreements — before it touches a student record. Vendors are held to the same terms in writing, and nothing is used to train someone else's model.
Rules people can follow
A plain-language acceptable-use policy for staff and, where you want one, for students: which tools are approved, what data may go into them, and how use is disclosed. Written with you, adopted by you.
Your data, where you decide
Built in your own cloud tenancy, not ours. Model and hosting options are chosen for where they process data and what they retain — and that choice is documented, not assumed.
No decision left to a model
Admission, placement, discipline and anything else that shapes a student's path stays with your staff. AI drafts, sorts and retrieves; a named person reviews and signs off.
Every output on the record
What was asked, which sources were used, what the system said and who approved it — logged and kept to your retention schedule, ready for a records request or a board question.
Where the team works
The offices that carry the most repetitive load.
Inquiries and applications
Answers to prospective students and families drawn from your own published requirements, checks that an application file is complete, and reply drafts your team approves before they go out.
The right answer, the right office
Questions answered from your handbook, catalog and policies, with the source shown. Anything personal or sensitive is routed to the office that owns it, and a person is always one step away.
The work behind the work
Facilities and IT request intake, staff search over internal procedures, routine reports and correspondence — integrated with the student information and ticketing systems you already run.
How it starts
Small, written down, and reversible.
Every step below ends in a document you keep, and none of them commits you to the next.
Privacy & acceptable-use review
Where AI is already in use across campus, what student data it touches, which vendors hold it, and what policy is missing. You get a written findings report and a draft policy.
One scoped build
A single workflow — admissions inquiries, a student-services assistant, an operations intake — built inside the rules from step one, with staff review on every output.
Retained CTO or embedded engineers
Ongoing ownership if you want it: architecture, vendor decisions and maintenance, handed back to your own IT team whenever you are ready.
Start with a conversation