Running AI in school without a single student account
Most AI tools want an email, an age gate and a login. Here is how a school delivers AI to four hundred students without handing any of them a consumer account, and what still needs a written policy.
The question that stops most school AI programs is not pedagogical. It is this one, usually asked by a principal about ninety seconds into the first meeting:
"So four hundred children are going to make ChatGPT accounts?"
It is the right question, and "no" is the only acceptable answer. Here is what the alternative looks like in practice.
Why personal accounts are the wrong shape for a school
Consumer AI services are built for individual adults, and the mismatch shows up in four places at once:
- Age gates and terms of service. Most major services set a minimum age, and some require verifiable parental consent below a threshold. A school that instructs a twelve-year-old to sign up is instructing them to misstate their age, or is collecting consent it has not designed for.
- Personal data. Signing up means an email address, often a phone number. That is student personal data, collected by a third party, outside your control and outside your retention policy.
- No visibility. If each student holds their own account, the school cannot see what was asked, cannot apply a content filter, and cannot answer a parent who wants to know what their child was exposed to.
- Cost and chaos. Four hundred free tiers, four hundred password resets, and a rate limit hit halfway through every lab.
What a managed gateway is, in plain terms
A managed gateway is a single institutional connection to the AI models, sitting between your students and the providers. The school — or the curriculum partner — holds the credentials. Students never see them and never create anything of their own.
In a lab exercise, the student's notebook calls the gateway. The gateway checks the request against policy, forwards it to the model, and returns the answer. From the student's side it simply works. From the school's side, four things become true that were not true before:
- No signups. No email addresses, no age declarations, no passwords, no personal data leaving the building for a consumer service.
- Filtering and limits are centrally applied, rather than depending on whatever each student's individual account happens to be set to.
- Usage is auditable. If a parent or a board asks what the tool was used for, there is a record and a person responsible for it.
- Cost is capped and predictable, because it is one account with limits rather than four hundred unmanaged ones.
This is not exotic. It is how any company gives a large team access to a paid service. Schools have simply not been offered it, because most AI-for-schools products were built as consumer products with a school logo on them.
With a managed gateway in place, how does a student use an AI model in class?
What a gateway does not solve
Plumbing is not policy. Three things still need a decision, in writing, before the first class:
What students may put into a model
The rule we teach from Grade 7 is simple enough for a twelve-year-old to remember: nothing about a real person, including yourself. No names, no photographs of classmates, no home address, no medical detail, no screenshots of family chats. Taught as a habit in the first term, not as a form signed in September.
Sensitive project topics
Projects that touch scams, medicines or mental wellbeing are the most engaging ones students choose, and the ones that most need guardrails. Ours run on scripted, facilitator-reviewed examples only — never a real private message, never a real health record — and the wellbeing project runs hands-on only where the school has named a counsellor who owns the escalation route.
Publication consent
A Build-a-thon produces photographs, video and student work that a school will quite reasonably want to share. Get written parental consent for publication separately from consent to participate, and default to not publishing when it is absent.
Five questions to put to any AI curriculum supplier: Does any student create an account with a third-party AI provider? Where does student data sit, and for how long? Who at your company is the named grievance contact for our parents? Can we see the filtering policy applied to student requests? What happens to our students' work when the contract ends?
The standard to hold suppliers to
India's Digital Personal Data Protection Act sets real expectations around children's data and verifiable parental consent. You do not need to be a lawyer to apply the spirit of it: collect the minimum, say who is responsible, and give parents a person to contact. Any supplier that cannot tell you, in one sentence each, what they collect and who is accountable for it has not thought about your students as carefully as you have.
AI Kids Lab turns the CBSE AI curriculum for Grades 7, 8 and 9 into gamified lessons designed by product engineers, inside your school's existing timetable. Try a free lesson (no sign-up), or book a 30-minute call.
Talk to us on WhatsApp

