Document: LearnSphere Horizon Privacy Notice Β· Generated: 29/09/2026, 10:02:54
The LearnSphere Horizon Privacy Notice demonstrates an acutely deficient compliance posture with an overall high-risk score of 28/100 across both domestic and European child-safety frameworks. Primary critical exposures stem from the explicit failure to complete a mandatory child-specific Data Protection Impact Assessment under the UK Children's Code, compounded by the unlawful use of engagement-driven algorithmic notifications and daily streaks restricted by the EU KIDS Act. Continued inaction carries acute regulatory urgency, leaving the organization vulnerable to formal supervisory intervention, operational disruption, and severe statutory fines from the Information Commissioner's Office and European data protection authorities. As an immediate remediation priority, the organization must suspend all gamified, engagement-nudging features and execute a comprehensive, child-centric Data Protection Impact Assessment to establish lawful processing baselines.
Age Appropriate Design Code (ICO)
| Standard | Finding | Score |
|---|---|---|
| π΄ Std 1: Best interests of the child | Subordinates children's privacy to commercial metrics by calibrating engagement algorithms for school licence renewals (Section 3.2) and sharing data with commercial consortia (Section 3.7). | 30/100 |
| π΄ Std 2: Data protection by design and default | Violates privacy-by-default standards by enabling peer visibility, tracking, profiling, and connected device data syncing automatically upon registration (Sections 7.1 and 14.3). | 25/100 |
| π Std 3: Age appropriate application | Distinguishes age tiers (under 13, 13-15, 16+) but relies on unverified self-declared age (Section 2.1) and enforces an arbitrary barrier denying under-16s direct control of their rights. | 50/100 |
| π Std 4: Transparency | Notice provides comprehensive disclosures but lacks child-friendly formatting and uses browsewrap terms stating access implies acceptance of the privacy notice (Section 1.4). | 50/100 |
| π΄ Std 5: Detrimental use of data | Leverages behavioural data to maximise daily session lengths and screen time via EngagementBoost nudges (Sections 3.2 and 5.2), contrary to child health and wellbeing guidance. | 30/100 |
| π’ Std 6: Policies and community standards | Maintains clear safeguarding commitments in Section 3.4 by integrating automated risk alerts with school Designated Safeguarding Leads in compliance with KCSIE 2024. | 80/100 |
| π΄ Std 7: Default settings | Directly breaches Standard 7 by defaulting all accounts to public peer profiles, active behavioural profiling, and push notifications with under-16s unable to change them (Sections 7.1 and 7.3). | 25/100 |
| π΄ Std 8: Data minimisation | Collects non-essential data including ambient classroom audio (Section 14.1) and response latency, retaining profile data for 36 months after school departure (Section 6.1). | 30/100 |
| π΄ Std 9: Data sharing | Mandates data sharing with commercial analytics consortium members and partner universities without student opt-out rights or consent (Sections 3.7, 3.8, and Appendix A). | 30/100 |
| π’ Std 10: Geolocation | Section 8.1 adheres to Standard 10 by strictly avoiding the collection of precise GPS geolocation, limiting geographic inference to city-level IP lookups solely for curriculum regionalisation. | 85/100 |
| π΄ Std 11: Parental controls | Section 10.2 violates requirements by allowing parents via FamilyView to covertly monitor emotional wellbeing pulse histories and activity patterns without notifying the child. | 35/100 |
| π΄ Std 12: Profiling | Profiling is switched on by default (Section 7.1), cannot be disabled without severe service degradation (Section 9.4), and is used to drive targeted university outreach (Section 3.8). | 25/100 |
| π΄ Std 13: Nudge techniques | Deploys gamified streak warnings and AI-calibrated EngagementBoost notifications designed to manipulate children into maintaining daily platform use (Sections 3.5 and 5.2). | 25/100 |
| π΄ Std 14: Connected toys and devices | Section 14.2 enables automatic syncing of LearnPad device telemetry and ambient audio without separate consent, child notification, or student controls to disable sync. | 30/100 |
| π΄ Std 15: Online tools | Provides no in-platform self-service tools for children to exercise rights (Section 13.4) and unlawfully restricts under-16s from submitting requests directly (Section 13.3). | 30/100 |
European Commission Safety-by-Design Obligation Β· COM(2026) 681
β οΈ Legal Disclaimer: This report is generated by AI for guidance purposes only and does not constitute legal advice. It must not be used as a substitute for assessment by a qualified data protection solicitor or registered DPO. Any decisions taken on the basis of this report must be reviewed and signed off by a competent professional.
Framework versions assessed: childrenscode Β· eukidsact.
Framework criteria last reviewed: August 2026. Regulatory frameworks are subject to change. Always verify analysis against the most current published guidance from the ICO, Ofcom, DfE and European Commission before taking compliance action.
β οΈ Emerging regulation β ICO EdTech Code: The ICO published its 'EdTech Examined' report on 24 June 2026, following audits of 28 EdTech providers which identified 596 compliance recommendations. The ICO is now working with the Department for Education and devolved authorities on a new EdTech Code of Practice. Once enacted, this will introduce mandatory compliance requirements for EdTech providers. UK GDPR criteria in this report already incorporate the ICO's EdTech Examined findings. Monitor ico.org.uk for code development updates.