1. Platform Scope and School Ownership

The platform is operated for schools and their authorized users. School records inside the app are managed within a school-specific context, and access is limited according to user role, school assignment, class assignment, and linked-student relationships.

• Only approved schools can be onboarded into the platform.
• Personal self-registration for unrelated individual use is not supported.
• Each school is responsible for the accuracy of the data it enters or approves.
• Users may only access data that matches their role and authorized school scope.

2. Acceptable Use and Account Responsibility

• Keep your username, password, and device secure.
• Do not share credentials, impersonate another user, or try to bypass permissions.
• Do not upload harmful files, misleading records, offensive content, or unauthorized exports.
• Use result, attendance, and profile tools carefully because actions may affect official school records.
• You are responsible for activity performed through your account unless you report unauthorized access promptly.

3. Data We Handle

The app may store and process information required to run school workflows, including:

• Identity data such as names, usernames, linked roles, school IDs, student IDs, and profile images where enabled.
• Academic data such as scores, grades, report comments, published results, ranking context, and historical records.
• Attendance and behaviour data such as days open, days present, assessment traits, and class notes.
• Operational data such as timetables, disputes, issue reports, imports, and workflow approvals.
• Security and audit data such as login events, password changes, activity history, and controlled admin actions.

4. Privacy, Access Control and Student Protection

• Access is role-based. Teachers should see only assigned subject or class scope, and parents should see only linked-child information.
• Published results, report views, and verification flows are designed for authorized academic use, not open public disclosure.
• Audit logs and system traces may be used to investigate abuse, errors, or unauthorized changes.
• Users must not copy, forward, screenshot, or distribute school records except where the school has authorized that use.
• Student information should be treated as sensitive, especially where it relates to minors.

5. Security and Retention

• The platform may use backups, audit logs, validation checks, and other reliability controls to protect records.
• Data may remain in the system as long as needed for active school operations, audit needs, support, backup recovery, or legal compliance.
• Deletion requests may be delayed or limited where records are required for legal, security, dispute, or academic-history reasons.
• Some technical metadata may be retained to confirm what changed, when it changed, and who initiated the action.

6. Data Rights and Correction Requests

The app includes a controlled Privacy Request workflow for export, correction, deletion, and related data-rights actions. Requests are reviewed before sensitive changes are applied.

• Use the in-app request form for export, deletion, correction, or contact-detail updates.
• School admins review requests in their school context before final action where applicable.
• Super admin resolution may be required for final approval, rejection, or application of controlled changes.
• Requests may be rejected when identity cannot be verified, the request is incomplete, or the action would compromise record integrity or legal obligations.

7. School Responsibilities

• Maintain accurate student, parent, teacher, and school information.
• Assign user roles carefully and remove access when staff or relationships change.
• Use published results, imports, corrections, and bulk tools responsibly.
• Review disputes, privacy requests, and unusual account activity in a timely way.
• Provide any extra school-specific privacy notice required by local law or policy.

8. Policy Updates and Acceptance

By checking the Terms and Privacy box at login, you confirm that you have read and accepted this notice. Acceptance may be recorded against your account and may be requested again after significant policy or feature updates.

We may revise this page to reflect new workflows, security controls, or compliance changes. The latest version published in the app replaces earlier general versions of this notice.

9. Help, Support and Contact Path

• For login, account, or school-record questions, contact your school administrator first.
• For product issues, suspicious behavior, or technical concerns, use the in-app Report Issue page.
• For privacy, export, correction, or deletion requests, use the in-app Privacy Request form.