SchoolJewel

Information for trusts and multi-academy trusts

5 November 2026 · Version 1.2

For multi-academy trusts, academy chains and schools that report to a trust or governing body.

Who is the controller?

In an academy, the academy trust is the legal entity and normally the data controller. If your trust is the controller, the trust (not each academy) agrees the SchoolJewel Terms and Data Processing Agreement, and the lawful basis and DPIA are recorded at trust level. In a local authority maintained school, the school or governing body decides, with its local authority and data protection officer where applicable. If you are unsure, ask your data protection officer.

How it works with SchoolJewel today

Each school registers its own School Leader account, and pays for its own plan if it uses a paid level. A trust does not currently have a trust-wide dashboard, and SchoolJewel does not share pupil information between schools.
Each school chooses its own way of naming pupils. We recommend a first name and surname initial, and full names are never needed.
The trust can accept the DPA once, in the DPA record, and list the schools that are covered:
Each school completes its own settings (Houses, features, prizes) and can complete a school-level DPIA using the trust’s DPIA as a base.
Invoices and purchase orders are available. Email info@schooljewel.com.

Checklist for the trust board or DPO

The trust is recorded as controller, and the DPA record is filed
A DPIA has been completed at trust level, with school-level notes
The trust’s privacy notices for families and staff mention SchoolJewel
A naming policy has been agreed () and shared with schools
The trust’s record of processing includes the SchoolJewel entry
The trust’s breach procedure covers SchoolJewel (see the Data incident contact sheet)
Schools know how to remove leavers each year (see the Staff quick guide)

Trust-level reporting and single sign-on are not available yet. If either matters to your trust, tell us at info@schooljewel.com.