Privacy practices for school examination data.

The app stores account details, school profiles, member roles, academic structures, learner records, guardian links, examination setup, marks, audit records, and published results needed to operate school examinations.

Data is used to authenticate users, separate school tenants, authorize school and platform actions, run examination workflows, calculate results, and provide learner or guardian portal access.

Each school is responsible for entering accurate learner, guardian, staff, and examination data and for assigning appropriate roles to its members.

Access is based on authenticated accounts, active school membership, platform roles, and server-side permission checks. School domains resolve to the matching tenant before protected data is loaded.

Audit and academic records may be retained for accountability, reporting, dispute resolution, and operational recovery according to the deployment operator's retention policy.

Support may ask for school name, account email, tenant or domain details, error messages, and workflow context to diagnose issues without requesting passwords.