Users
Protect access
Keep credentials private and use only authorized features.
These terms explain the responsibilities of users, schools, platform administrators, and deployment operators when managing accounts, academic data, examinations, and service operations.
Terms at a glance
The main areas covered by this agreement
Responsible access
Use verified accounts and respect assigned roles.
Accurate school data
Schools remain accountable for records entered by their members.
Safe operations
Production services and recovery actions require authorized oversight.
Agreement structure
Responsibilities are separated across individual accounts, school tenants, platform administration, and the infrastructure used to run the service.
Users
Protect access
Keep credentials private and use only authorized features.
Schools
Maintain accuracy
Review members, roles, academic records, and published results.
Operators
Run safely
Manage infrastructure, recovery, backups, and administrative actions.
Use the platform for legitimate school administration, examination management, learner record keeping, and result publication. Do not use it to enter false records, impersonate users, or bypass role restrictions.
Users are responsible for keeping credentials private, verifying account email addresses, and signing out of shared devices. School owners are responsible for inviting the right staff and reviewing role assignments.
Schools are responsible for the accuracy of academic years, enrollments, marks, learner details, guardian links, and published results entered by their members.
Platform super admins may approve school applications, suspend or reactivate tenants, manage platform roles, and review audit records for operational safety.
Production use depends on configured database, email, upload, DNS, and SSL services. Operators should monitor backups, delivery, storage, domains, and audit records.
Emergency recovery may require approved administrative scripts, such as first-owner bootstrap or database index setup. These should be used only by authorized operators.
Administrative scripts, platform-level actions, role changes, data publication, and recovery procedures should only be performed by people with the appropriate authority and operational context.