How we protect your school's data

Where your data lives

SSMS is hosted on servers in India by default. Each school's data is kept separate through tenant isolation at every layer; groups can choose a dedicated database, a dedicated server or on-premise installation.

Who can see what

Access is controlled by roles, fine-grained permissions and data scope — teachers see their own sections, parents only their own children, accountants only what their role allows. Sensitive identifiers (Aadhaar, PAN, bank accounts) and health information are encrypted, masked by default, and every access to them is logged.

Sign-in protection

Two-step verification, password policies, lock-out after failed attempts, device sessions and, by default, one active sign-in per user. Suspicious sign-ins are recorded as security events.

Audit trail

Important actions — fee changes, refunds, concessions, mark edits, record changes — are recorded with the old and new values, the user, time, device and reason. Financial and academic history is never silently edited.

Consent and retention

Consent-sensitive data such as APAAR is recorded with the consent status. Nothing is published to the school website unless switched on, and students' names appear publicly only with families' agreement. Retention, masking, export and anonymisation policies are configurable per school.

Backups and recovery

Database and file backups are encrypted, verified and periodically restore-tested by the SSMS team. School administrators can see backup status.

AI and third parties

AI features use only the providers whose keys your school adds, send only the minimum needed for a draft, and log every call. We never use your data for advertising or sell it.