Safeguarding & Data
Most common school data concerns are neutralised by how YoYo is built, not by policies bolted on afterwards. Everything below is documented and ready for DPO review.
No real names stored against pronunciation scores. Student identity is held by the school, not by YoYo.
Pronunciation is scored in real time and the audio is discarded immediately. No recordings are kept — ever.
All processing on UK infrastructure (Alibaba Cloud, London). No international transfers. EU Cloud CoC certified (2020LVL02SCOPE013).
YoYo integrates generative AI as a teacher tool, not a student-facing feature. Teachers can use it to create speaking prompts manually or generate syllabus-aligned content automatically. Pedagogical structuring is built into the AI with outputs graded by difficulty, mapped to curriculum objectives, and always subject to teacher review before students see them. Our use of generative AI has been reviewed against DfE guidance on AI in education and meets its requirements.
Independent controller model under UK GDPR. Not joint controllers. Data Sharing Agreement included in pilot documentation.
No user IDs sent to scoring engine. 7-day operational log retention only (timestamps, IP, error logs). No model training on data.
Identified as a compliance obligation under the independent controller model. Formal mapping assessment in progress — we'll share this with your DPO once complete.
YoYo has been reviewed against the DfE's guidance on AI in schools. No generative AI, no chatbot, no conversational AI. We're confident in our position and happy to share the detail with your DPO.
All documents available on request before any pilot begins.
Transparency is part of our approach — not something we add at the end. We're happy to walk your DPO through the full documentation before any pilot begins.