Security at Schoolise

01 Security by Design

Schoolise is built as a modern, cloud-hosted platform. Security decisions — how organisations are separated, who can see what, and how information moves in and out of the system — are part of the platform’s core architecture rather than a layer added on top.

• Every school, centre or training provider operates in its own separated space within the platform
• Staff, teachers, students and families each see only the information relevant to their role
• Security practices are reviewed as new features, packages and integrations are added

02 Organisation & Data Isolation

Schoolise is used by many different schools, tutoring centres and training providers at once. Each one operates in its own logically separated space: staff and families at one organisation cannot see or access records belonging to another.

Your organisation’s data stays within your organisation. This separation applies to student and guardian records, admissions data, finance information, communications, and files uploaded to the platform. For organisations that run more than one site, group administrators can be given oversight across their own sites — without that ever crossing into another, unrelated organisation’s data.

03 Access Control & Permissions

Every person using Schoolise — administrator, teacher, finance officer, student or parent — is assigned a role, and that role determines what they can view and do. A teacher managing their own class does not automatically see finance records; a parent sees their own child’s information, not the whole cohort’s.

• Individual staff and family accounts — logins are not shared
• Role-based permissions across administration, teaching and family access
• Extra restrictions around safeguarding and other sensitive records, on top of standard role-based permissions
• Permissions checked centrally, rather than left to individual pages of the app

04 Protecting Your Data

Data sent to and from Schoolise — including sign-ins, messages and file uploads — travels over encrypted, SSH-secured connections. This applies across the platform, including the online sessions and communications packages.

• All traffic to and from Schoolise is sent over encrypted connections
• Student, admissions and finance records are held in a structured database, reachable only through the application’s own access controls
• Accounts are protected with standard modern session-security practices, including protection against common credential-based attacks

05 Application Security & Files

Schoolise is built on a mainstream, actively maintained web application framework, which provides standard protections against common risks such as cross-site request forgery (CSRF) and cross-site scripting (XSS), and these protections remain enabled across the platform.

Documents, images and other files uploaded to Schoolise — for admissions, safeguarding or general school use — are stored against the record they belong to and inherit the same organisation- and role-based access rules as the rest of the platform, rather than being reachable independently.

06 Backups & Resilience

Schoolise takes daily backups of organisation data as part of normal operations, so that information can be restored in the event of a technical failure.

07 Monitoring & Accountability

When the Schoolise support team needs to access your organisation’s account to help resolve a request, that access is limited to what’s needed to address the issue you’ve raised.

08 Privacy & Data Protection

This page explains the safeguards and practices behind how Schoolise protects your data day-to-day. For details on what data is collected, why, how long it’s kept and your rights over it, see our Privacy Policy. Our Terms & Conditions and Data Processing Agreement cover the legal terms of using the platform.