Security

Built for sensitive school operations

Student, fee, and parent data deserves careful isolation, least-privilege access, and recoverable backups.

01

Instance isolation

Each school runs as its own Sipinor instance so campus data stays separated.

02

Roles & permissions

Staff only see the modules and records their role allows.

03

IP filtering

Optional IP allowlists help lock down administrative access.

04

Backups

Scheduled backup workflows help protect against accidental loss.

05

AI permission boundaries

AI action mode uses only data the signed-in user can access.

06

Operational privacy

Support and onboarding practices minimize unnecessary data exposure.

Next step

Need a security review for procurement?

Contact us for questionnaire support on applicable plans.

Our standard

School software we would run ourselves

Security overview →

Built for schools

Designed for Indian campus desks — not generic CRM templates.

Multi-campus ready

Instance isolation with shared oversight for school chains.

Parent communication

Fees, attendance, and notices without WhatsApp chaos.

Data isolation

Each school workspace stays separate with role-based access.

Admin support

Walkthroughs and setup help for principals and office staff.

Book DemoFree Trial