Database-enforced isolation
Every row belongs to an institution, and the database itself refuses cross-institution reads — an application bug cannot leak one institution's data to another. This is covered by automated tests on every release.
APEX serves many institutions on one platform, so isolation and least-privilege access are built into the foundation rather than added later.
Every row belongs to an institution, and the database itself refuses cross-institution reads — an application bug cannot leak one institution's data to another. This is covered by automated tests on every release.
Two levels of roles — institution and department — decide what each student, faculty member, administrator and parent can see and do.
Sensitive actions such as allocations, verifications, grade changes and exports are recorded with who, when and what.
All traffic is encrypted with TLS, passwords are stored only as strong one-way hashes, and sensitive data is encrypted.
Verifiable parental consent for minors, purpose-limited access, confidential flags on sensitive mentoring issues, and support for access and correction requests.
Neither this website nor the APEX app uses third-party advertising or analytics trackers.
Read the full security overview and privacy policy. Security questionnaires and DPAs are available on request.
A 30-minute walkthrough tailored to your programmes and accreditation cycle.