FERPA
Education records, directory information, and who a parent or eligible student can ask to see. A tool that stores grades or attendance has to say where that record lives and who else can open it.
These are the constraints that show up in a security review. They are not a feature list.
Education records, directory information, and who a parent or eligible student can ask to see. A tool that stores grades or attendance has to say where that record lives and who else can open it.
Accounts for children under 13 need a path for verifiable parental consent. A tutoring product that looks like a consumer app still hits this when the learner is under 13.
Many states restrict selling student data or using it for advertising. Buyers ask this before they ask about live classes.
A new learning tool has to sit beside the roster and the classroom platform. Replacing both on day one is rarely the deal.
PowerSchool, Infinite Campus, and similar SIS products already hold enrollment, guardians, and attendance. The buyer expects a roster sync, not a second spreadsheet.
Canvas, Google Classroom, and the school's existing LMS already hold assignments. Teachers will not re-enter a class list.
Districts expect a tool to open from the LMS with the same identity, instead of a separate username for every student.
The person who signs is usually not the person stuck in the workaround.
Has to answer the data-processing questions and will block a tool that cannot name its subprocessors.
Needs teachers, students, and parents to see different slices of the same attendance record.
Is still running classes through chat threads and wants guardians to see progress without a phone call.
When the rules and the existing systems are clear, the education app page covers the feature set, cost, and timeline. See the education app feature set, cost, and timeline.
