What protects your data today, how each control actually works, and what is still on the roadmap. Written for the person running the review, not for the brochure.
Most security pages are written to reassure. This one is written to be checked, because that is what actually happens to it: an IT lead or a procurement officer opens it with a questionnaire beside them.
So each control below says what it does and how it is enforced, and the roadmap section says plainly what is not built yet. A gap you find here costs us a conversation. A gap you find during due diligence, after we implied otherwise, costs us the contract and costs you weeks.
If your review needs detail beyond this page, ask. We answer questionnaires directly rather than returning a brochure.
Each of these is implemented and can be demonstrated in a technical walkthrough.
Permission to open something is checked on several independent levels rather than once, so a single misconfiguration does not expose data. Access is granted per role and per action, not as one blanket setting.
Identity documents, personal contact numbers and bank details can be withheld from roles that do not need them, even on records those roles are allowed to open. Seeing a student is not the same as seeing everything about them.
One institution can never see the records of another, and within a group each campus keeps its own. Separation is applied consistently across the whole platform rather than screen by screen, and a record cannot be moved between institutions.
Records are retired rather than destroyed. A mistaken deletion during a busy admissions week is recoverable, and a deleted record keeps its history instead of vanishing from the audit.
Who created a record, who last changed it, who removed it and when. A disputed mark or fee has a history somebody can check months later, without needing a support ticket to reconstruct it.
Teachers see their assigned classes, sections and students rather than the whole institution. The default is the narrow view, widened deliberately, not the reverse.
This is the first thing a serious reviewer asks, so here is the direct answer. Your records are yours: another institution cannot see them, and within a multi-campus group each campus keeps its own data unless you deliberately share it. That separation is applied uniformly across the platform rather than implemented screen by screen, which is what makes it dependable instead of dependent on whoever built a given feature.
What it does not mean is physical separation. Institutions run on shared infrastructure with strict logical separation between them. If your policy requires dedicated infrastructure, or data held in a named country, we do not offer that today. That is on the roadmap below.
We would rather you knew that in the first conversation than at contract review. If your team needs to go deeper than this page, we will walk through it properly on a technical call under NDA.
Stated so you can plan around it rather than discover it later. Ask us for current timelines during your review.
Not available today. Institutions with a hard requirement for physically separate infrastructure should treat this as a gap rather than a detail, and raise it with us early.
We cannot currently commit to holding your data in a specific jurisdiction. If your regulator requires it, tell us early so we can be honest about fit rather than waste your evaluation.
We hold no third-party security certification today. What we offer instead is direct access to the people who built the system and written commitments in your agreement.
Date and time handling is being extended for institutions outside our core regions. Ask us where your region stands before you commit to a rollout date.
Separate from the product, and worth stating because you are reading it now.
No analytics or marketing tag loads until you allow it where consent is legally required, and every decision is recorded.
This site and the product are served over HTTPS. Certificates are managed and renewed automatically.
A demo request is used to contact you about the demo. It is not sold, and you can ask us to delete it at any point.
Send us your questionnaire and we will complete it directly. If you would rather talk to the engineers who built this, we will arrange that instead.
Contact us