Identify the organisation and the national context

This guide concerns UK data protection principles, not a single education regime applying identically everywhere. School governance, education-record access and safeguarding frameworks differ across England, Wales, Scotland and Northern Ireland. Department for Education guidance cited here is directed at England. A tutoring company, academy trust, maintained school and commercial learning platform should not simply copy one another’s legal explanations.

Create a map of the legal entities involved before reviewing documents. Identify who decides why pupil records are used and who is handling information on instructions. An external service can be a processor for one operation and a controller for a separate purpose. Contract wording is relevant evidence, but the actual decisions and activities determine the role. School responsibility does not disappear when records move into an app.

Challenge the amount of information the product needs

Ask the provider to demonstrate an ordinary pupil journey using a test account. Which identifiers, learning records and device details are collected? What is optional? What does the teacher see, what does the parent see, and what can supplier support staff inspect? Include analytics, automated recommendations and integrations rather than reviewing only the fields on the enrolment form.

Our suggested procurement test is to remove a proposed field and ask whether the educational task still works. A reading exercise may need a progress record but not a home address. Differentiate genuine teaching requirements from convenient commercial profiling. Health, disability and safeguarding information can need additional legal conditions and tighter controls. Do not populate every available integration simply because the platform makes importing easy.

Select the basis for the activity, not a blanket permission form

Public task or legal obligation may support functions of a public education body where the relevant legal foundation exists. That does not mean a private supplier can invoke the school’s public task for unrelated commercial uses. Consent also needs real choice and must be appropriate for the activity; it is not a general cure for compulsory classroom processing.

Explain processing to pupils in language they can understand and provide appropriate information to parents or carers. Separate the explanation for core education records from optional publicity or additional services. Consider whether an apparently optional feature is genuinely avoidable without disadvantage. Where consent is used, make withdrawal workable and keep track of which images, activities or services a particular permission covers.

Assess the Children’s Code and high-risk processing properly

The ICO distinguishes a school’s educational activity from commercial edtech services when assessing the Children’s Code. A provider processing outside the school’s instructions may have controller responsibilities and need to assess whether its online service falls within the Code. Neither “we sell only to schools” nor “children did not create the account themselves” settles the question.

Independently assess whether the processing is likely to create high risks and therefore requires a DPIA. Consider monitoring, profiling, sensitive information, novel technology and the children affected. Make the assessment before procurement becomes irreversible. It should examine realistic harms such as inappropriate disclosure to a parent, unfair categorisation or exclusion from learning, not just the chance of a password being stolen.

Contract for everyday control and a practical exit

For a processor, require the applicable Article 28 terms and understand subprocessors, security, assistance with rights requests, breach reporting and deletion or return. Establish whether information can be accessed internationally and check any restricted transfers. Ask whether the supplier uses pupil information for advertising or training general-purpose AI models, and obtain a clear answer about the actual product configuration.

A useful demonstration is an exit rehearsal: export one test record in usable form, remove the account and explain what remains in backups. Check that staff cannot accidentally retain access after changing schools. For a trust or provider with multiple sites, test isolation between them. A polished procurement questionnaire is less persuasive than a working demonstration of the controls you will depend on.

Share for safeguarding without abandoning judgment

Data protection should not be used as a blanket reason to withhold information necessary for safeguarding. Equally, a safeguarding label does not justify unrestricted circulation. Establish the purpose, relevant legal basis, recipient and necessary content, following the applicable national safeguarding framework. Record a reasoned decision and seek appropriate advice when uncertain rather than allowing uncertainty to become inaction.

Design safe communication routes in advance. Staff should know how to escalate an urgent concern and how to verify a recipient. Avoid placing detailed allegations into general classroom notes merely because that system is convenient. Consider family circumstances before sharing updates automatically: a technically correct email address can still be an inappropriate destination for a sensitive disclosure.

Prepare for requests, changes and the end of enrolment

A child’s data protection rights and a parent’s separate education-record entitlements are not interchangeable. Assess the child’s competence, authority to act and the applicable law when a parent requests records. Do not assume that parental responsibility gives unconditional access to every item. Mixed records may contain information about other pupils, staff or family members requiring careful review.

Finally, assign owners for retention, access reviews and supplier changes. Test what happens when a pupil leaves, a parent’s contact restrictions change or a teacher’s account is compromised. Keep the incident process connected to safeguarding and the data protection lead. This is a practical starting framework, not a substitute for nation-specific education advice or an assessment of a particular high-risk product.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.