
The classroom note
A teacher opening MagicSchool for the first time can generate a lesson plan, a rubric or report-card comments at no cost; the platform's own homepage, retrieved 16 September 2026, states it offers "80+ teacher tools" built for "safe, district-aligned AI." That free layer is the entry point most teachers meet first, before any district contract exists, which changes who is actually deciding to adopt the tool: an individual teacher signing up alone, or a procurement office negotiating for a whole district.
What the evidence says
The pricing page lists three tiers as retrieved: Free, with a chatbot and quiz and writing-feedback tools; Plus, for individual teachers, at "$8.33 USD/user/mo (billed annually)" or "$12.99 USD/mo billed monthly," adding unlimited generations and student-facing tools; and Enterprise, for districts, at a custom price adding single sign-on, integrations and a named data privacy agreement. These are the vendor's own figures, not an independent audit; the homepage's cited statistics, a "28% improvement in students meeting literacy grade-level expectations" and "88% of teachers say it helps them reach every learner," are presented without the study design, sample or period a reader needs to judge them, so this note treats them as unverified vendor claims. The privacy page displays FERPA, COPPA, GDPR, SOC 2 and 1EdTech compliance badges and states MagicSchool "provides district-ready data practices, detailed documentation, and customizable Data Privacy Agreements," without detailing retention or model-training use on the page itself.
The implementation question
The free tier is the mechanism that gets a tool into a classroom before any district review happens. A single teacher can sign up, generate materials and build a habit of use without ever triggering the data privacy agreement, single sign-on or dashboard controls the Enterprise tier is built to provide. This is an editorial observation about how free tiers generally function, not a claim MagicSchool's pages make: a district that later tries to govern the tool through an Enterprise contract is negotiating around a use pattern individual teachers may already have established informally, on the free tier, without the compliance layer attached.
What holds and what fails
The pricing structure and named certifications are specific and checkable against the cited pages. What does not hold is treating the homepage's improvement statistics as evidence in the way a peer-reviewed or agency evaluation would be; MagicSchool's own pages do not publish the underlying study, so this note cannot state a sample, design or period for either figure, and neither should a school's procurement case.
- Are teachers already using the free tier before any Enterprise agreement is signed, and does that change what data protections apply to their use?
- Has the district asked MagicSchool for the underlying study behind its cited literacy and teacher-satisfaction figures?
- What does the Data Privacy Agreement say about retention and model training that the public privacy page does not?
A free tier, a paid individual tier and a custom district tier sit on the same platform with three different levels of stated data governance attached, and only the vendor's own pages, read carefully, show where those lines actually fall.
Sources & reading trail
Living homepage describing 80+ teacher tools and citing vendor statistics on literacy improvement and teacher satisfaction.
Source published: Not established · Retrieved: 16 September 2026
States the Free, Plus ($8.33-$12.99/user/month) and custom Enterprise tiers and what each adds.
Source published: Not established · Retrieved: 16 September 2026
States named compliance certifications (FERPA, COPPA, GDPR, SOC 2, 1EdTech) and references a customizable Data Privacy Agreement.
Source published: Not established · Retrieved: 16 September 2026
Departments, studies and vendor documents establish the record; the implementation reading and the boundary are School AI Atlas editorial analysis. This retrospective draft does not imply the site published on the event date.