Current school data
School name, teacher accounts, class names and join codes, memberships, assignments, submitted work, progress and feedback are processed. The current model has no separate school-administrator tenancy dashboard.
Access boundary
Teachers are scoped to classes they own and students in those classes. A school administrator role exists but requires further tenancy design before production use across a school.
Instructions and contracts
A school DPA must define instructions, confidentiality, security, subprocessors, transfers, rights assistance, breach handling, deletion or return, audit information and termination. The repository checklist is not an executed contract.
Removal and termination
Removing class membership does not delete an independent account. School export, class archiving, teacher transfer and contract-end deletion require business rules and legal review before school procurement.
Safeguarding
Schools remain responsible for their safeguarding procedures. CodeQuest provides a report route and restricted case workflow but does not promise continuous monitoring.