⚠️ Draft for review — not legal advice.
This is a working draft. It must be reviewed and approved by a qualified data-protection / education-law professional and the responsible Data Protection Officer before it is published or relied upon. Placeholders in [square brackets] need real values.
Acceptable Use Policy
Last updated: Draft — not yet published
What may and may not be put into Storyjar. Teachers are the moderators, so this is mainly a guide for staff.
Storyjar is for children's learning moments
It is a place for a child's own work — drawings, photos of what they've made or done, and their words — kept for the class journal. It is not a general photo store, a messaging tool, or a place for personal or sensitive records.
The teacher's role
Every moment passes through a teacher before it is kept. Teachers should approve only content that is appropriate, and send back or delete anything that is not. Please do not approve:
- Images or text that identify a child beyond their first name (e.g. surnames, addresses, dates of birth) or that show another child without the school's consent arrangements being met.
- Anything upsetting, unsafe, discriminatory, or unlawful.
- Personal or special-category information that isn't needed for the journal (e.g. medical or family details).
- Content that isn't the child's own learning work.
Not allowed
- Giving a child their own login, email or password (they don't need one).
- Sharing login details or letting unauthorised adults access children's work.
- Using Storyjar to contact children directly or outside the school's supervision.
- Attempting to access another class's or family's data, or to circumvent access controls.
- Uploading malware, or content that infringes others' rights.
If something's wrong
If inappropriate content is uploaded, a teacher should return or delete it and, if it raises a safeguarding concern, follow the school's procedures and inform the Designated Safeguarding Lead. See the Safeguarding page. We may suspend access where needed to protect children.