Protecting the records behind every school day.
Attendance, student records, teacher information and parent communications deserve deliberate safeguards. Here is how we approach access, operational security and school responsibilities. We do not make an unrealistic “100% secure” guarantee; specific technical controls are reviewed for each live deployment.
Authorized school users manage academic information through their Principal Portal. E School's role is to configure, host and support the agreed service, not to sell student information or access it for unrelated purposes.
01. Our security principles
Different roles should see only the information they need. Authorized principals manage user assignments, and support access is limited to legitimate operational tasks.
Production deployments should use HTTPS and appropriate server security configuration. We verify the live deployment rather than assuming local demo settings are secure.
We establish an appropriate backup, restoration and retention arrangement as part of deployment planning. Frequency and recovery arrangements must be confirmed for each school.
We review software compatibility, apply suitable updates and investigate faults. The timing and scope of maintenance depend on the agreed service and operational needs.
02. Who should have access?
School administrators: authorized Principal Portal users can manage school data and user permissions. Teachers: use the Teacher App or Teacher Portal for teaching functions within their assigned permissions. Students and parents: access the views made available to their accounts. E School support: may need controlled access for setup and authorized troubleshooting.
The school should promptly remove accounts for departing staff, avoid shared passwords and verify that linked family accounts belong to the correct children.
03. Sensitive information and transfers
Schools should share onboarding records only through agreed channels, with the minimum information required. Please do not send passwords or large sets of student data through the public contact enquiry form. School records may be stored or transmitted using contracted infrastructure; relevant hosting regions and providers should be documented for each deployment.
04. Data changes, exports and end of service
Authorized school users can maintain their records in the system according to available features. Where export, correction, restoration or deletion requires provider assistance, the school may submit a verified request. We will explain what can be delivered, any relevant backup retention period and the steps to complete the request.
05. If something goes wrong
Users should report a suspicious login, lost device, incorrect account access or unexpected data exposure promptly. E School will work to identify and contain incidents involving the service and coordinate with the school on recovery and notification obligations where appropriate. Investigation and response arrangements should be specified in the school's written service terms.
06. Security is a shared responsibility
We are responsible for the reasonable security measures we agree to implement and maintain for the service. Schools are responsible for keeping their records accurate, controlling which staff may access them, safeguarding accounts and devices, and notifying us promptly of concerns. Absolute protection against every threat cannot be guaranteed.
Ask us about the hosting location, access permissions, backup plan and data handling terms before onboarding.
Discuss your school's requirements ↗