Security

Security controls for school data and operational workflows

This page summarises the technical and organisational controls Schoolgle uses to protect school information.

Last updated: 14 May 2026

Access control

Product routes use authenticated sessions and role-based access controls. Sensitive modules should restrict access to authorised staff such as SLT, administrators, governors or module owners.

Organisation scoping

Schoolgle workflows should scope records to the authenticated organisation. Server routes must not trust caller-supplied organisation ids for ordinary school users.

Encryption

Connections use HTTPS/TLS. Database and hosting providers apply encryption controls for stored data according to their platform commitments.

Audit logs

Key workflows use audit logs for actions, approvals, compliance records and changes. AI-assisted workflows should record source references and human approval status.

AI and sensitive data

AI features must follow the Schoolgle model registry and approved provider policy. Sensitive data should be minimised before AI processing, and AI outputs must remain reviewable by school staff.

Incident and breach handling

Schoolgle aims to support schools with audit trails and investigation records. Where a personal data breach affects a school, Schoolgle would notify the school without undue delay, work with the school as controller and provide relevant information for UK GDPR breach assessment and notification duties.

Continuous improvement

Schoolgle maintains an internal security and data-protection improvement plan so that our controls continue to mature as the product develops. Current areas of routine improvement include audit logging, minimising unnecessary browser-side storage, documenting incident-response steps, and refining user privacy and admin controls.

These improvements are governance and product-quality tasks. They do not change the core position that school data is only processed where needed to provide the subscribed service, under the contract and data processing agreement.

DPO review before reliance

A DPO or legal reviewer should confirm the final DPA, supplier list, transfer safeguards, breach workflow and retention schedule before a school relies on the public legal pack.

No hidden decision-making

Security and governance controls should preserve the product rule that AI outputs are advisory, reviewable and auditable, not final school decisions.