Trust centre
Everything a school's data protection officer needs, published rather than promised. Where we fall short of a standard, this page says so.
Lines met
7
DfE standards
Partial
1
Stated with the gap
Not yet
2
Published anyway
DPIA sections
9
4 for the school to complete
UK data residency is the default for every category of data. Where a part of the system does not yet meet that default, it is listed below as a gap rather than described as compliant.
DfE standards, line by line
Including the January 2026 additions. Lines we do not meet are published as lines we do not meet.
Filtering and monitoring
MetProducts used by pupils must not undermine the school's filtering and monitoring duties.
Evidence: Safe AI complements Smoothwall and Senso rather than replacing them; monitoring alerts route to the named DSL, never to leadership generically.
Cyber security
PartialProtect all devices and accounts with multi-factor authentication where available.
Evidence: Role-based access and audited identity reveals are in place.
Gap: MFA depends on the school's identity provider; SSO (REQ-147) is an interface only.
Cyber security
MetMaintain an accurate record of what data is held and where it is processed.
Evidence: The residency register publishes every data category, its store and its processing region.
Cyber security
Not yetHold a recognised cyber security certification appropriate to the service.
Evidence: Certification path published: Cyber Essentials Plus, then ISO 27001, then SOC 2.
Gap: REQ-174: no certification held today. Publishing the gap is the point of this page.
Generative AI in education (January 2026) · new January 2026
MetSchools must know which model providers process pupil data and be told when that changes.
Evidence: The model routing table names every declared route, its provider and whether it is connected.
Generative AI in education (January 2026) · new January 2026
MetPupil data must not be used to train foundation models without explicit, informed consent.
Evidence: Training on pupil data is off by default and cannot be enabled without recorded consent; pupil IP is never used commercially.
Generative AI in education (January 2026) · new January 2026
MetAI-generated content presented to pupils must be subject to human review appropriate to its risk.
Evidence: No atom reaches a pupil without specialist review; marking stays teacher-facing until departmental agreement clears the threshold.
Generative AI in education (January 2026) · new January 2026
Not yetSafeguarding classifiers must have published performance characteristics.
Evidence: An independent audit with precision and recall by risk category is committed to.
Gap: REQ-152, blocked by DEC-003. No audited figures exist yet and none are claimed.
Digital accessibility
MetServices must meet WCAG 2.2 AA.
Evidence: AA contrast, keyboard paths, reduced-motion support and age-adaptive rendering throughout.
Data protection
MetA DPIA must be completed before processing children's data at scale.
Evidence: A pre-filled DPIA is supplied to the school rather than left for the school to write.
Where the data lives
UK by default for every category, with any gap stated rather than smoothed over.
Pupil work and workspace entries
Stored UK · processed UKTutor transcripts and process replay
Stored UK · processed UKSafeguarding records and referrals
Stored UK · processed UKClassification currently runs on a hosted model whose region we do not control (REQ-141 is blocked by DEC-003). Until the self-hosted classifier ships, this is a residency gap and it is published as one.
Staff accounts and roles
Stored UK · processed UKAnonymised reviewed corpus
Stored UK · processed UKOperational telemetry (no pupil content)
Stored UK · processed UK
Pupil work belongs to the pupil
An explicit commitment, not a clause buried in the terms.
Work a pupil writes belongs to the pupil. Safe AI does not use pupil intellectual property commercially: it is not sold, not licensed on, not used to train foundation models, and not used to build products we sell to anyone else.
What we do
- Showing the pupil their own work
- Showing the class teacher and the school, who are the data controller
- Safeguarding routing to the named DSL where a concern is detected
What we never do
- Sale or licensing of pupil work to any third party
- Training foundation models on pupil work
- Marketing, case studies or demonstrations using real pupil work
- Any commercial product built on pupil-authored content
ICO Children's Code and UK GDPR
Our position on each of the fifteen standards, and who is controller for what.
- 1. Best interests of the child — Every routing rule is written so the pupil is the beneficiary, not the buyer.
- 2. Data protection impact assessments — A pre-filled DPIA is supplied to every school.
- 3. Age-appropriate application — Rendering, pacing and extension content adapt by year group; extension is suppressed below KS3.
- 4. Transparency — The pupil is told in their own reading level what the tutor records and who can see it.
- 5. Detrimental use of data — No data is used against the pupil's interests; leadership sees aggregates only.
- 6. Policies and community standards — Published policies are the ones actually enforced in the tutor policy engine.
- 7. Default settings — High privacy by default; training off by default; pseudonymity in the corpus.
- 8. Data minimisation — Cache keys exclude pupil identity; identity reveals are audited events.
- 9. Data sharing — Sharing is limited to the school and statutory safeguarding routing.
- 10. Geolocation — Not collected.
- 11. Parental controls — Where a school enables parental visibility, the pupil is told.
- 12. Profiling — Profiling is used for teaching diagnosis only and never for commercial targeting.
- 13. Nudge techniques — No streaks, no loss aversion, no parasocial framing; sessions have natural stopping points.
- 14. Connected toys and devices — Not applicable.
- 15. Online tools — Pupils can exercise their rights through the school; the tutor explains how.
Controller and processor
- Teaching, tutoring and mastery records — controller: The school (or trust); processor: Safe AI. Safe AI acts only on the school's documented instructions.
- Safeguarding records and referrals — controller: The school (or trust); processor: Safe AI. The DSL owns the record. Safe AI routes and retains it; it never decides the outcome.
- Staff accounts and billing — controller: Safe AI; processor: —. Safe AI is controller for its own contractual and account data.
- Operational telemetry with no pupil content — controller: Safe AI; processor: —. Service reliability data only; no pupil content and no pupil identifiers.
DPIA, already written
Supplied filled in with our own processing. The school edits and signs rather than starting from a blank page.
Nature of the processing
Safe AI processes pupil work, tutor dialogue and derived mastery records to provide Socratic tutoring, and processes safeguarding classifications to route concerns to the school's Designated Safeguarding Lead. Processing is carried out on the school's instructions.
Scope and data categories
Categories: pupil work, tutor transcripts, mastery records, safeguarding records, staff account data, operational telemetry. Special category data may arise within safeguarding disclosures.
For the school to complete: Year groups and subjects in scope, and the expected pupil headcount.
Context and expectations of children
Pupils are aged 4–16. The ICO Children's Code is applied in full: no nudge techniques, no profiling for commercial purposes, high privacy by default, age-appropriate explanation of what the tutor records.
Purposes and lawful basis
Public task (education) for teaching and learning; legal obligation and substantial public interest (safeguarding) for concern routing. Consent is not relied on for core teaching, so a pupil cannot be disadvantaged by withholding it.
For the school to complete: Confirm the lawful basis recorded in your own ROPA.
Necessity and proportionality
Data minimisation: renderings are cached without pupil identity; leadership sees aggregated statistics only; identity reveals (for example book-scrutiny export) are logged as audited events.
Risks identified
Over-reliance on the tutor; misclassification of a safeguarding concern; unauthorised identity reveal; residency gap on classification while REQ-141 is blocked; incorrect content reaching a pupil.
Measures to reduce risk
Anti-dependency reporting to the teacher; four-tier safeguarding routing with DSL ownership; immutable audit log; deterministic verification with a second reader that can only downgrade; specialist review gate before any atom reaches a pupil.
Retention and deletion
Tutor transcripts and mastery records for the duration of enrolment plus one academic year. Safeguarding records to the pupil's 25th birthday, in line with DfE guidance.
For the school to complete: Confirm against your own retention schedule and record any local variation.
Sign-off
Prepared by Safe AI for completion by the school.
For the school to complete: DPO name, date, residual risk accepted, review date.
Declared, not connected
Interfaces exist so the shape is honest. Nothing behind them is live.
Item provenance and board-material licensing
Blocked by DEC-002Every item carries provenance; board materials are never redistributed without a licence, and licensing conversations start in year one.
Next: Open licensing conversations with AQA, Edexcel and OCR before any redistribution.
Self-hosted safeguarding classifiers
Blocked by DEC-003High-volume safeguarding classification on self-hosted small models, where latency, cost and UK residency all matter.
Next: Until this ships, the classification route runs on a hosted model and the residency gap is published.
MIS integration — Wonde first
Interface onlyWonde first, covering Arbor, Bromcom and SIMS; Groupcall Xporter as the alternative.
Next: Wonde application registration and a pilot trust's approval.
Entra ID and Google Workspace SSO
Interface onlyIdentity through Microsoft Entra ID and Google Workspace, while the MIS stays authoritative for classes and enrolment.
Next: App registration in both directories; enrolment continues to come from the MIS, never from the directory.
Independent classifier audit
Blocked by DEC-003An independent audit of the safeguarding classifiers with precision and recall published by risk category.
Next: Commission the audit once the classifier stack is fixed; publish the figures whatever they say.
Certification path
Interface onlyCyber Essentials Plus, then ISO 27001, then SOC 2 when the US motion starts.
Next: Cyber Essentials Plus assessment booked before the first trust-wide deployment.
Safe AI is an illustrative product. Figures, schools and evidence shown across this site are fictional and exist to demonstrate the design.