Children's records.
Act like it.
An institution platform holds the most sensitive data a family ever hands over. What follows is how this one treats it — stated as checkable mechanisms, not badges. Where a certification is absent, you will not find it implied.
The mechanisms
Isolation is enforced
below the application.
Tenant isolation
- Row-level security at the database — a query without a tenant returns nothing, not everything
- Every institution at its own origin, with per-origin sign-in
- Product data separated by soft references — no cross-product joins to leak through
Identity & sessions
- A phone or email change requires proof of the old identity, not just a form
- Changing a credential revokes every session that predates it
- Staff impersonation is read-only, logged, and visible — never a back door
Data minimisation
- Aadhaar numbers are never stored — a test enforces it in the build
- Statutory identity fields are policy-driven: collect what your rules require
- Free-text from the public internet is stored as text, rendered as text
Where isolation lives
DPDP, honestly
The Act asks who holds what, and why. We can answer.
The Digital Personal Data Protection Act turns every vendor an institution uses into a question the institution must answer: what does this company hold about our families, on what basis, and what happens to it when we leave? Most schools cannot answer it for six vendors at once. Consolidation is itself a DPDP posture — fewer processors, fewer agreements, fewer places a record can be forgotten — and the platform’s design carries the rest: data lives in the tenant, credentials and messaging identities belong to the institution, and the exit is a full export in machine-readable formats, on demand, with no fee.
What we do not claim matters as much. There is no ISO badge on this page because we have not completed that audit; when we have, the certificate will appear with its date, in the same checkable style as everything else on this site. A vendor that will not say what it lacks is telling you how it will behave when something goes wrong. Security questionnaires from your IT team are welcome — they get the real answers, including the uncomfortable ones.
Send the questionnaire
your IT head keeps ready.
Real answers, including where the honest answer is “not yet”.