Cortex IOS Terms of Use

Document ID:CTS-LEGAL-001
Version:2.0
Status:Published
Classification:Public
Product:Cortex IOS - School Operating System
Effective Date:29th June 2026
Last Updated:16th July 2026
Review Frequency:Annual or upon material change
Owner:Aionpixel Technologies Private Limited
Applies To:Web Portal, Mobile Applications (iOS & Android), APIs and Integrated Services
Contents

1. Introduction

1.1 About Cortex IOS

Cortex IOS is a cloud-based School Operating System developed and operated by Aionpixel Technologies Private Limited ("Aionpixel", "we", "our", or "us").

Cortex IOS enables educational institutions to manage academic, administrative, financial, operational, communication, human resource, learning management, governance, reporting, and other authorised School activities through an integrated digital platform.

These Platform Terms of Service ("Terms") govern the use of Cortex IOS by authorised users accessing the platform through supported web portals, mobile applications, authorised APIs, and related services.

1.2 Purpose of these Terms

These Terms establish the conditions governing authorised access to and use of Cortex IOS.

They describe:

  • who may use Cortex IOS
  • how accounts are authorised
  • acceptable and prohibited use
  • responsibilities of Schools, users, and Aionpixel
  • platform availability
  • intellectual property
  • suspension and termination of access
  • liability limitations
  • other conditions applicable to the use of Cortex IOS

These Terms are intended to promote the secure, responsible, and authorised use of Cortex IOS.

1.3 Relationship with Other Documents

These Terms should be read together with the following Cortex IOS documents where applicable:

Product Privacy Policy;

Data Governance Statement;

Cookie & Similar Technologies Policy;

Information Security Statement;

Website Terms of Use;

Parent & Guardian Privacy Notice;

Student Privacy Notice;

School Staff Privacy Notice; and

Legal & Transparency Statement.

Each document serves a different purpose.

The Product Privacy Policy explains how information is processed.

These Terms explain the contractual conditions governing the use of Cortex IOS.

2. Acceptance of these Terms

2.1 Agreement

By accessing or using Cortex IOS, an authorised user confirms that they have been provided an opportunity to review these Terms and agree to comply with them.

Where electronic acceptance is used, Cortex IOS may record:

  • document identifier
  • document version
  • acceptance date and time
  • user identifier
  • School or tenant
  • access channel
  • technical audit information
  • other information reasonably required for compliance and audit purposes

2.2 Separate Privacy Acknowledgement

The Cortex IOS Product Privacy Policy is acknowledged separately from these Terms.

A Privacy Policy acknowledgement records that the user has been provided the opportunity to review the applicable privacy information.

Acceptance of these Terms constitutes agreement to the contractual conditions governing the use of Cortex IOS.

The two records are maintained independently within the Cortex IOS compliance framework.

2.3 Authority to Accept

By accepting these Terms, the individual confirms that they are authorised to do so.

Examples include:

  • a School administrator accepting on behalf of their own authorised account
  • a teacher accepting for their own account
  • a member of School staff accepting for their own account
  • a parent or guardian accepting for their own authorised account
  • a student accepting where appropriate for their authorised account and applicable School policies

A parent or guardian does not accept these Terms on behalf of unrelated users.

Similarly, acceptance by one member of School staff does not constitute acceptance for another staff member.

2.4 Refusal to Accept

If an individual does not agree to these Terms, they should not access or continue using Cortex IOS.

The School may determine whether alternative School processes are available for individuals who decline to use the platform.

3. Eligibility and Authorised Users

3.1 Eligible Users

Cortex IOS is intended solely for authorised users associated with a subscribing educational institution.

Depending on the School's configuration, authorised users may include:

  • School management
  • principals
  • administrators
  • teachers
  • accountants
  • human resource personnel
  • non-teaching staff
  • parents and guardians
  • students
  • other authorised users approved by the School

Access is limited to individuals who have been appropriately authorised.

3.2 School-Managed Accounts

Cortex IOS accounts are generally created, provisioned, or authorised through School-managed or authorised web-platform workflows.

The School determines:

  • who receives access
  • the role assigned to each user
  • the permissions available to that role
  • when access should be modified or removed

The Cortex IOS mobile application does not provide a public user-registration process.

Users cannot independently create Cortex IOS accounts through the mobile application.

3.3 User Credentials

Each authorised user is responsible for maintaining the confidentiality of their authentication credentials.

Users must not:

  • share passwords
  • disclose authentication codes
  • allow another individual to use their account
  • attempt to access another person's account
  • bypass authentication mechanisms

The user is responsible for activity performed using their authorised account unless the activity results from circumstances beyond the user's reasonable control.

3.4 Accurate Information

Users should ensure that information submitted by them is accurate and kept reasonably up to date.

Where information requires correction, the user should use the available Cortex IOS process or notify the appropriate School administrator.

The School remains responsible for determining how official School records are maintained.

3.5 Suspension of Eligibility

Eligibility to use Cortex IOS may cease where:

  • the individual's relationship with the School ends
  • the School withdraws access
  • the assigned role changes
  • the account is suspended
  • access is terminated under these Terms
  • continued access is no longer authorised

Termination of access does not necessarily result in deletion of associated School records.

4. Cortex IOS Services

4.1 Nature of the Platform

Cortex IOS is a configurable Software-as-a-Service (SaaS) platform.

Different Schools may enable different modules, workflows, integrations, and features.

Accordingly, functionality available to one School or user may differ from that available to another.

The absence of a feature in a particular deployment does not imply that the feature is generally unavailable within Cortex IOS.

4.2 Supported Services

Depending on the applicable subscription and School configuration, Cortex IOS may include services such as:

  • admissions
  • student information management
  • academic administration
  • attendance
  • timetable management
  • examinations
  • assessments
  • report cards
  • learning management
  • assignments
  • communications
  • transport management
  • library management
  • fee management
  • accounting
  • human resource management
  • payroll support
  • governance workflows
  • institutional reporting
  • AI-assisted features where enabled
  • other authorised School services

Not every service is available to every School.

4.3 Role-Based Experience

The information and functionality available within Cortex IOS depend upon:

  • the user's role
  • School configuration
  • enabled modules
  • assigned permissions
  • relationship to the student where applicable
  • available platform controls

Authorised access to one module does not automatically provide access to another.

4.4 Continuous Improvement

Aionpixel may:

  • improve existing functionality
  • introduce new modules
  • retire obsolete functionality
  • enhance security
  • improve performance
  • introduce new integrations
  • update supported technologies

Where a material change affects these Terms or privacy practices, appropriate notice may be provided.

5. User Accounts

5.1 Account Provisioning

Cortex IOS user accounts are provisioned through authorised School or web-platform processes.

Depending on the user's role, account provisioning may occur following:

  • student enrolment
  • parent or guardian association
  • staff onboarding
  • administrative approval
  • authorised invitation
  • other School-managed workflows

The mobile application does not independently provision Cortex IOS user accounts.

5.2 Role Assignment

Each account is assigned one or more authorised roles.

Examples include:

  • Parent
  • Student
  • Teacher
  • School Administrator
  • Principal
  • Accountant
  • Human Resource Personnel
  • Management
  • other School-defined roles

Role assignments determine the functionality and information available to the user.

5.3 Account Security

Users are responsible for taking reasonable steps to protect their account.

Examples include:

  • maintaining password confidentiality
  • using trusted devices where possible
  • promptly reporting suspected compromise
  • signing out where appropriate
  • protecting authentication devices

Users should immediately notify the School or Aionpixel support where they reasonably believe that their account has been compromised.

5.4 Account Changes

The School may:

  • modify user roles
  • reset passwords
  • suspend accounts
  • reactivate accounts
  • change permissions
  • terminate access

Changes are performed according to School administration processes and available Cortex IOS controls.

5.5 Account Deactivation

Where a user's relationship with the School changes, the applicable account may be disabled or deactivated.

Examples include:

  • graduation
  • student withdrawal
  • transfer
  • staff resignation
  • retirement
  • change of responsibilities
  • other authorised administrative actions

Account deactivation does not automatically delete School records associated with the user.

Data retention and deletion are governed by the Cortex IOS Product Privacy Policy and Data Governance Statement.

5.6 Mobile Application Access

The Cortex IOS Android and iOS applications provide secure access for existing authorised Cortex IOS users.

The mobile applications:

  • do not create new user accounts
  • do not provide public registration
  • do not independently delete accounts
  • require successful authentication using an existing authorised account

Users who no longer have an authorised account may not continue accessing Cortex IOS through the mobile application.

6. Acceptable Use

6.1 General Principle

Cortex IOS is intended to support legitimate educational, administrative, operational, financial, communication, governance, and learning activities of subscribing educational institutions.

Authorised users must use Cortex IOS responsibly, ethically, lawfully, and in accordance with:

  • these Platform Terms of Service
  • applicable School policies
  • applicable laws and regulations
  • professional responsibilities
  • educational standards
  • any additional instructions issued by the School relating to the use of Cortex IOS

6.2 Permitted Use

Authorised users may use Cortex IOS only for purposes connected with their authorised role.

Examples include:

School Management

managing School operations;

reviewing institutional reports;

monitoring authorised activities;

approving workflows;

managing governance functions; and

other authorised administrative responsibilities.

School Administrators

administering authorised School records;

managing users;

configuring authorised modules;

maintaining operational data;

generating reports; and

managing School workflows.

Teachers

recording attendance;

creating assessments;

entering marks and grades;

reviewing student progress;

communicating with authorised users;

managing learning activities; and

performing other authorised academic responsibilities.

Parents and Guardians

reviewing authorised student information;

accessing fee information;

receiving School communications;

submitting authorised information;

making payments where enabled;

communicating with the School; and

using other parent-facing services made available by the School.

Students

accessing authorised learning material;

submitting assignments;

viewing authorised academic information;

participating in authorised educational activities; and

communicating through approved School channels where enabled.

6.3 Prohibited Activities

Users must not:

  • impersonate another individual
  • share authentication credentials
  • intentionally provide false information
  • attempt to bypass security controls
  • attempt to gain unauthorised access
  • interfere with another user's access
  • introduce malicious software
  • attempt to reverse engineer Cortex IOS except where permitted by applicable law
  • misuse APIs or integrations
  • interfere with platform availability
  • harvest or scrape information without authorisation
  • copy information belonging to another School
  • misuse student information
  • use Cortex IOS for unlawful purposes
  • violate another person's privacy
  • upload malicious files
  • attempt to test platform vulnerabilities without written authorisation
  • circumvent licence restrictions
  • otherwise misuse Cortex IOS

6.4 Communications

Users must use Cortex IOS communication features responsibly.

Communications should:

  • relate to authorised School activities
  • be respectful
  • comply with School policies
  • avoid harassment
  • avoid discriminatory content
  • avoid abusive language
  • avoid unlawful content
  • respect the privacy of other users

Schools remain responsible for establishing their own communication policies.

6.5 Uploaded Content

Users should upload only information and documents that they are authorised to upload.

Users must not knowingly upload:

  • unlawful material
  • malicious software
  • copyrighted material without authority
  • confidential information unrelated to School purposes
  • offensive material
  • information intended to disrupt Cortex IOS operations

6.6 Responsible Use of AI Features

Where AI-assisted functionality is available, users remain responsible for reviewing AI-generated outputs.

AI-assisted content should not automatically be treated as:

  • final academic feedback
  • official School communication
  • disciplinary findings
  • legal advice
  • medical advice
  • financial advice
  • professional judgement

Users should review AI-assisted outputs before relying upon them.

7. School Responsibilities

7.1 General Responsibilities

Each subscribing School remains responsible for its educational, administrative, legal, and operational activities.

Use of Cortex IOS does not transfer these responsibilities to Aionpixel.

7.2 User Administration

The School is responsible for:

  • creating or approving authorised users
  • assigning user roles
  • reviewing permissions
  • removing unnecessary access
  • supervising user activity
  • maintaining organisational governance
  • ensuring that authorised users receive appropriate training where required

7.3 Information Accuracy

The School is responsible for maintaining the accuracy of information entered into Cortex IOS.

Where incorrect information is identified, the School should take reasonable steps to correct it using authorised processes.

The School is responsible for determining:

  • what information is collected
  • why information is collected
  • whether consent is required
  • applicable notices
  • applicable legal obligations
  • retention requirements
  • reporting obligations
  • lawful use of information

Aionpixel provides the technology platform through which authorised processing occurs.

7.5 Device Security

Schools should encourage authorised users to:

  • maintain updated devices
  • protect passwords
  • report suspected compromise
  • avoid sharing accounts
  • follow School information security practices

7.6 Communication Responsibility

Schools remain responsible for the content of communications sent through Cortex IOS.

Aionpixel provides communication functionality but does not generally review or approve School communications before delivery.

8. User Responsibilities

8.1 Responsible Use

Each authorised user agrees to:

  • use Cortex IOS only for authorised purposes
  • comply with School policies
  • comply with applicable laws
  • protect authentication credentials
  • maintain confidentiality
  • respect other users
  • protect personal information
  • report suspected misuse
  • cooperate with authorised security investigations where appropriate

8.2 Protection of Credentials

Users must:

  • keep passwords confidential
  • avoid sharing authentication credentials
  • avoid using another person's account
  • report suspected unauthorised access promptly
  • take reasonable steps to protect their devices

8.3 Information Submitted

Users are responsible for information they submit through authorised Cortex IOS features.

Examples include:

  • attendance entries
  • assessment information
  • assignments
  • messages
  • uploaded documents
  • leave applications
  • fee information
  • administrative records
  • other authorised submissions

Users should not knowingly submit false or misleading information.

8.4 Reporting Concerns

Users should promptly report:

  • suspected unauthorised access
  • suspected privacy incidents
  • incorrect information
  • security concerns
  • suspicious communications
  • suspected fraud
  • technical issues affecting secure operation

Reports should be made through authorised School channels or Aionpixel support where appropriate.

9. Mobile Application

9.1 Purpose

The Cortex IOS mobile applications are designed to extend authorised Cortex IOS services to existing users.

The mobile applications are not standalone consumer applications.

9.2 Existing Authorised Users

Only users with an existing authorised Cortex IOS account may sign in to the mobile application.

The mobile application does not:

  • register new users
  • create user accounts
  • enrol students
  • create parent accounts
  • independently delete Cortex IOS accounts

Account administration occurs through authorised School or web-platform workflows.

9.3 Role-Based Functionality

The mobile application provides access according to the authenticated user's authorised role.

Available functionality depends upon:

  • School configuration
  • enabled modules
  • assigned permissions
  • user role
  • tenant association
  • feature availability

9.4 Device Permissions

Certain mobile features may require permission to access:

  • camera
  • microphone
  • photographs
  • files
  • notifications
  • location

Permissions are requested only when required by the applicable feature.

Disabling a permission may prevent that feature from functioning correctly.

9.5 Mobile Security

Users should:

  • protect their mobile devices
  • use device authentication where available
  • avoid installing untrusted software
  • keep the application updated
  • promptly report loss of a device used to access Cortex IOS
  • notify the School where unauthorised access is suspected

10. Intellectual Property

10.1 Ownership

Cortex IOS, including its software, source code, architecture, user interface, databases, documentation, workflows, trademarks, logos, graphics, designs, and related intellectual property, is owned by or licensed to Aionpixel Technologies Private Limited unless otherwise stated.

These Terms do not transfer ownership of Cortex IOS intellectual property to any user or School.

10.2 Limited Right to Use

Subject to these Terms and the applicable agreement between the School and Aionpixel, authorised users are granted a limited, non-exclusive, non-transferable, revocable right to access and use Cortex IOS solely for authorised educational and administrative purposes.

No ownership rights are granted.

10.3 School Data

Information entered into Cortex IOS by or on behalf of a School remains subject to the applicable contractual arrangements between the School and Aionpixel.

Nothing in these Terms transfers ownership of School records to another customer or authorised user.

10.4 Restrictions

Except where expressly permitted by law or written agreement, users must not:

  • copy Cortex IOS software
  • modify source code
  • create derivative works
  • distribute software components
  • remove proprietary notices
  • reverse engineer the platform
  • attempt to extract source code
  • commercially exploit Cortex IOS outside authorised use
  • permit unauthorised third parties to use the platform

10.5 Feedback

Users may voluntarily provide suggestions, enhancement requests, recommendations, or other feedback relating to Cortex IOS.

Unless otherwise agreed in writing, Aionpixel may use such feedback for product improvement without creating an obligation to implement the suggestion or provide compensation.

Submission of feedback does not transfer ownership of Cortex IOS intellectual property to the user.

11. Third-Party Services

11.1 General Principle

Cortex IOS may integrate with or utilise third-party services to support authorised platform functionality.

Third-party services are selected to support the delivery, operation, security, communication, payment processing, monitoring, analytics, authentication, artificial intelligence, or other technical functions of Cortex IOS.

The availability of a particular third-party service depends upon:

  • the Cortex IOS subscription
  • School configuration
  • enabled modules
  • geographic availability
  • technical architecture
  • operational requirements

11.2 Third-Party Integrations

Depending upon the services enabled by the School or Aionpixel, Cortex IOS may integrate with:

  • payment service providers
  • communication providers
  • email delivery providers
  • SMS providers
  • push notification services
  • authentication providers
  • cloud infrastructure providers
  • storage providers
  • monitoring services
  • analytics services
  • AI service providers
  • document services
  • educational systems
  • government reporting services where supported
  • other authorised technical platforms

The existence of an integration within Cortex IOS does not require every School to enable or use that integration.

11.3 Third-Party Responsibilities

Each third-party provider is responsible for the services it performs.

Aionpixel seeks to engage providers appropriate for the technical service being delivered.

Where applicable, contractual arrangements may include obligations relating to:

  • confidentiality
  • information security
  • authorised processing
  • operational resilience
  • subcontracting
  • incident notification
  • return or deletion of information

11.4 Third-Party Terms

Where a School or user directly accesses a third-party service through Cortex IOS, the terms and privacy practices of that third-party service may also apply.

Users should review those terms where appropriate.

12. Artificial Intelligence Features

12.1 Availability

Cortex IOS may include AI-assisted functionality.

The availability of AI-assisted features depends upon:

product version;

School subscription;

enabled modules;

configuration;

licensing; and

technical implementation.

Not every School or user will have access to AI-assisted functionality.

12.2 Purpose

AI-assisted functionality is intended to support authorised educational and administrative activities.

Examples may include:

  • drafting observations
  • generating narrative comments
  • assisting educational workflows
  • preparing summaries
  • assisting reporting
  • providing recommendations
  • assisting operational workflows
  • other authorised productivity features

12.3 Human Review

AI-generated content should be reviewed by an appropriately authorised user before being relied upon.

AI-assisted functionality supports human decision-making and does not replace professional educational judgement.

Teachers, administrators, School management, and other authorised personnel remain responsible for reviewing AI-generated outputs before:

  • publishing report cards
  • issuing School communications
  • recording observations
  • making disciplinary decisions
  • preparing official records
  • making significant educational or administrative decisions

12.4 Responsible Use

Users must not intentionally use AI-assisted functionality to:

  • generate unlawful content
  • create discriminatory content
  • infringe intellectual property rights
  • impersonate another individual
  • create fraudulent records
  • misuse student information
  • generate misleading official records
  • otherwise violate these Terms or applicable law

13. Availability and Support

13.1 Service Availability

Aionpixel seeks to make Cortex IOS available on a continuous basis.

However, uninterrupted availability cannot be guaranteed.

Temporary interruptions may occur because of:

  • maintenance
  • upgrades
  • security improvements
  • infrastructure issues
  • communication failures
  • Internet connectivity
  • third-party service interruptions
  • force majeure events
  • circumstances beyond Aionpixel's reasonable control

13.2 Planned Maintenance

Where reasonably practicable, planned maintenance activities may be scheduled to minimise operational disruption.

Maintenance may include:

  • security updates
  • infrastructure upgrades
  • software releases
  • database maintenance
  • performance improvements
  • operational enhancements

13.3 Support Services

Support services are provided according to the applicable agreement between Aionpixel and the School.

Support availability may depend upon:

  • subscription level
  • support agreement
  • severity of the issue
  • business hours
  • emergency situations
  • operational priorities

13.4 Feature Availability

Aionpixel may introduce, modify, improve, replace, suspend, or retire features as Cortex IOS evolves.

Such changes do not necessarily constitute a breach of these Terms where they are made in the ordinary course of product development, maintenance, security, or operational improvement.

14. Suspension and Termination

14.1 Suspension of Access

Access to Cortex IOS may be temporarily suspended where reasonably necessary to:

  • protect platform security
  • investigate suspected misuse
  • comply with legal obligations
  • respond to security incidents
  • perform emergency maintenance
  • protect customer information
  • prevent unauthorised access

14.2 School-Initiated Suspension

A School may suspend or terminate access to a user's account according to its administrative responsibilities.

Examples include:

  • graduation
  • withdrawal
  • staff separation
  • disciplinary action
  • role changes
  • administrative decisions
  • other authorised School actions

14.3 Termination for Misuse

Aionpixel may suspend or terminate access where a user:

  • materially breaches these Terms
  • intentionally compromises platform security
  • repeatedly engages in prohibited conduct
  • attempts unauthorised access
  • distributes malicious software
  • interferes with Cortex IOS operations
  • otherwise presents a significant risk to the platform or its users

Where appropriate, Aionpixel may notify the relevant School.

14.4 Effect of Termination

Termination of access:

  • ends the user's authority to access Cortex IOS
  • does not transfer ownership of School records
  • does not automatically delete School information
  • does not affect accrued legal rights or obligations
  • does not terminate contractual obligations that are intended to survive termination

Data handling following termination is governed by the Product Privacy Policy, Data Governance Statement, and applicable agreements.

15. Disclaimers

15.1 Educational Platform

Cortex IOS is a technology platform that supports educational institutions.

Cortex IOS does not independently determine:

  • admission decisions
  • student grades
  • academic outcomes
  • disciplinary decisions
  • School policies
  • educational curriculum
  • examination results
  • scholarship decisions
  • employment decisions

These matters remain the responsibility of the School and its authorised personnel.

15.2 Information Accuracy

Cortex IOS processes information provided by authorised users.

Aionpixel does not independently verify every item of information entered into the platform.

Schools remain responsible for reviewing and maintaining the accuracy of official School records.

15.3 Professional Judgement

Nothing within Cortex IOS should be interpreted as replacing:

  • educational judgement
  • legal advice
  • accounting advice
  • medical advice
  • psychological assessment
  • safeguarding responsibilities
  • professional decision-making

16. Limitation of Liability

16.1 Scope

To the maximum extent permitted by applicable law, Aionpixel's liability shall be limited in accordance with the applicable agreement governing the provision of Cortex IOS.

Nothing in these Terms excludes liability where exclusion is not permitted by applicable law.

16.2 Platform Operation

Aionpixel is not responsible for losses arising solely from:

  • incorrect information entered by authorised users
  • misuse of authorised accounts
  • failure to protect credentials
  • School administrative decisions
  • Internet connectivity issues outside Aionpixel's control
  • third-party infrastructure failures
  • force majeure events
  • unauthorised use resulting from a user's failure to maintain reasonable security

16.3 School Responsibilities

The School remains responsible for:

  • educational decisions
  • academic records
  • statutory reporting
  • School governance
  • student welfare
  • employment decisions
  • financial administration
  • compliance with applicable educational obligations

17. Governing Law

These Terms shall be governed by the laws applicable to the agreement between Aionpixel Technologies Private Limited and the subscribing School.

Where no separate contractual provision specifies otherwise, these Terms shall be governed by the laws of the Republic of India.

The courts having competent jurisdiction shall have jurisdiction over disputes arising under these Terms, subject to any contractual dispute resolution mechanism agreed between Aionpixel and the School.

18. Changes to these Terms

Aionpixel may update these Terms from time to time.

Updates may reflect:

  • new Cortex IOS functionality
  • legal developments
  • security improvements
  • operational changes
  • technology changes
  • new services
  • improvements to these Terms

Where a material change is introduced, authorised users may be required to review and accept the updated version before continuing to use Cortex IOS.

Minor editorial or non-material updates may not require renewed acceptance.

19. Contact Information

Questions regarding these Terms may be directed to:

General Support:

support@cortexios.com

Website:

https://www.cortexios.com

Trust, Privacy & Security Centre:

https://www.cortexios.com/trust

Annexure A - Examples of Acceptable and Unacceptable Use

Acceptable Use Unacceptable Use
Recording attendance Attempting to access another School's information
Entering assessment marks Sharing passwords
Viewing authorised student records Circumventing security controls
Paying School fees Uploading malicious software
Sending authorised School communications Using Cortex IOS for unlawful purposes
Accessing learning material Creating fraudulent School records
Uploading authorised documents Misusing AI-generated content without review

Annexure B - User Role Responsibilities

User Role Primary Responsibilities
School Management Governance, oversight and authorised approvals
Administrator User administration, configuration and operations
Teacher Teaching, attendance, assessments and communication
Accountant Fee administration and authorised financial operations
HR Personnel Staff administration and HR workflows
Parent / Guardian Reviewing authorised student information and School interaction
Student Accessing authorised educational services
Support Personnel Providing authorised technical assistance

Annexure C - Version History

Version Date Description
1.0 29th June 2026 Initial Platform Terms of Service
2.0 16th July 2026 Comprehensive revision aligning with Cortex IOS Privacy Policy, Data Governance Statement, web and mobile application architecture, AI-assisted functionality, role-based access model, and Trust Centre documentation.
Back to top