School staff
Staff name, school email, role and school or class information used to manage access.
INFORMATION FOR SCHOOL LEADERS & DATA PROTECTION LEADS
Data protection & safeguarding
Understand school-managed access, pupil information, recordings and teacher oversight before introducing YourStoryWorld in your setting.
Clear roles before pupils begin.
For school-managed pupil data, the school normally determines the purposes of use and YourStoryWorld processes it to provide the agreed service. Confirm the contracting organisation, controller and processor roles, and the applicable data processing agreement before rollout.
What information is involved?
Pupil profiles
A first name or pseudonym, class and login identifier, together with age or reading settings. Avoid full names and sensitive details in story prompts.
Reading & learning activity
Generated stories, reading activity, comprehension responses and related dashboard information.
Optional recordings
Audio linked to a pupil profile and story for authorised review. Agree when recording is appropriate and explain it to pupils and families.
Access, storage and retention.
- School-managed accounts and roles restrict access to the relevant school users.
- The service uses cloud infrastructure including Google Firebase, with HTTPS and provider storage safeguards.
- Ask for the current sub-processor list, processing locations and transfer arrangements as part of your school’s review.
- Agree retention, exports and deletion arrangements, including what happens at the end of a trial or subscription.
- Contact support for authorised export, correction or deletion requests. Backup and audit requirements may affect timing.
Detailed handling of personal data is described in the Privacy Policy. This page is a school-oriented summary, not a substitute for the agreed contract or your school’s assessment.
AI safeguards support teacher oversight.
Prompts and content filters are designed to reduce inappropriate outputs. AI can still make mistakes, so staff should review generated stories and questions before using them with pupils.
- Use age-appropriate settings and clear, positive story instructions.
- Do not enter sensitive pupil information into free-text fields.
- Model how to question invented or inaccurate details.
- Follow your school’s safeguarding and incident-reporting arrangements if a concern arises.
- Report unsuitable generated content to support with enough detail to investigate, while minimising personal information.
YourStoryWorld is not an open public chat or social network. It is an additional classroom tool, with the adult choosing how it is used.
Read the Child Safety policy →Information for your school’s supplier review.
Involve your data protection officer, safeguarding lead and IT team before introducing pupil accounts. Your review should cover the data processing agreement, current sub-processors, processing locations, retention and deletion, incident reporting, and whether prompts, stories or recordings are used to train AI models. Confirm the arrangements for your school before entering pupil data.
DfE generative AI product safety standards ↗ · DfE guidance on AI and school data protection ↗
Questions to settle before rollout.
- Who will administer school accounts and reset pupil credentials?
- Which year groups, staff and devices will take part?
- Will pupils record reading or access the platform from home?
- What information will families receive and what permissions are needed?
- What evidence, retention and deletion arrangements does your school require?
We can discuss these during a demonstration or supported-trial enquiry.
See how it fits your school.
Explore the pupil and teacher experience with us before deciding on a trial or wider rollout.
Arrange a demonstration →