Separate database per school
Each school's operational data lives in its own database, and requests are bound to the school's own address.
Security and tenant isolation
Isolation by design, not by convention.
School data is sensitive. BAINI separates schools at the database, binds every session to its school, and checks authority on the server for every request.
A separate database for each school
Each school's operational records live in that school's own database. Shared platform services — accounts, school directory, plans — sit in a separate control plane.
Your school's own address
Pre-sign-in pages and branding are resolved from the school's verified address. An unknown address gets nothing — never a default school.
Sessions bound to the school
A signed-in session belongs to one school. Presented at another school's address, it is refused.
Role and class scope
Permissions follow the role and the classes a person is assigned; checks run on the server for every request, not only in the screen.
Audit trails
Sensitive actions — configuration changes, approvals, report revisions — are recorded with who did them and when.
Versioned reports
Published reports are never edited in place. Corrections are reissued as a new version; the earlier one is withdrawn.
Device-bound mobile access
Mobile sign-in is tied to an enrolled device; parents add a device PIN.
What we do not claim
- BAINI does not hold an independent security or privacy certification today.
- Production hosting region, backup restoration, monitoring and incident response must be verified for the deployed service before any school goes live.
- Data-processing terms between BAINI and each school are still being prepared and are not published here.
- Schools remain responsible for lawful collection and use of learner data; BAINI's safeguards support that responsibility.
Security built into the platform
Audit trails
Sensitive changes — configuration, approvals, report revisions — are recorded for review.
Platform operations console
Provisioning, lifecycle and support access for BAINI's own operators.
Parent Android access
Phone-based registration, confirmation by the school and a device-bound PIN.
Questions about how your data would be handled?
Ask us. We will show you the isolation and access model in detail, and be clear about what is still being prepared.