Data boundary
Tenant scoped
School records remain attached to the correct workspace.
Understand what information the platform handles, how school data is separated, and how access is controlled during normal operation.
Privacy principle
Tenant-scoped data and role-limited access.
We process only the information required for safe examination operations and keep tenant data separated.
Privacy framework
The platform processes the information required to run school examination workflows while separating tenant data, controlling access, and maintaining accountability for sensitive actions.
Data boundary
Tenant scoped
School records remain attached to the correct workspace.
Access model
Role controlled
Permissions are validated before protected data is returned.
Accountability
Audit aware
Sensitive actions can be retained for operational review.
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.
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.
Deployment operators should define retention periods, backup practices, support procedures, and access-review policies that match their legal and operational requirements.