Spell & Grow · Trust · Safeguarding

Safer than the baseline.

Spell & Grow is built for children aged 4–13 (Reception to Year 8). We hold ourselves to a higher bar than the GDPR baseline. This page documents our commitments, how we map to KCSIE 2025 as a supplier, who our Designated Safeguarding Lead is, and how to report a concern.

Status: v1.0 — pending legal review

Igloo Labs is a small company, and Spell & Grow has no way for anyone to message or contact a child, so we expect few safeguarding concerns. No concern has yet been handled through this process, and it has not yet been tabletop-drilled; the first drill will run before the first paying school goes live. Mirrors plans/features/schools-portal/trust-and-compliance/policies/safeguarding.md.

Our commitments

KCSIE 2025 mapping

Keeping Children Safe in Education (DfE, September 2025) is written for schools and colleges. Spell & Grow is a supplier, not a school, so most paragraphs do not bind us directly; this table shows which areas touch an online learning product and what we do about each so a school’s DSL can see where we fit into their own policy.

KCSIE areaApplies to a supplier?What Spell & Grow does
Part 1 — safeguarding information for all staffIndirectly: our staff may see a concern in support dataAll directors have completed basic safeguarding training. The DSL is the internal reporting route.
Part 2 — management of safeguarding: DSL role, policies, record keepingYes, in miniatureNamed DSL: Anthony Eskinazi (Director). This statement is the policy. Each concern and what we did about it is recorded in writing.
Part 2 — online safety: filtering and monitoringNot applicable — Spell & Grow is not an internet gateway and does not monitor pupils' wider device useWe do not filter or monitor the device. We run the content-safety gate on every word and sentence shown to a child, and never surface open web content, links, chat or user-generated media. Treat Spell & Grow as a closed content app in your filtering policy.
Part 2 — online safety: content, contact, conduct, commerceYesContent: safety gate + no open web. Contact: no messaging, no profiles, no adult-to-child channel. Conduct: no pupil-to-pupil interaction exists. Commerce: no advertising, no in-app purchases for children, no sale of data.
Part 2 — data protection and information sharingYesProcessor under a DPA; data minimised to roster, practice and optional SEN tags; no pupil contact details; audit log of every privileged action; sharing with a school's DSL or the police under formal disclosure only.
Part 3 — safer recruitment and staff vettingYes, for anyone with data or support accessAll directors hold DBS checks and have completed basic safeguarding training, and use MFA. Anyone else would be DBS-checked, trained and bound by a written confidentiality undertaking before being given access. Support access is via the audited view-as path only.
Part 4 — allegations about staff and volunteersYesReport an allegation about anyone working for Igloo Labs, including the DSL, to the Local Authority Designated Officer (LADO) and, where it concerns a child at a school, to that school's DSL. If an allegation reaches us first, we pass it to the LADO and cooperate fully.
Part 5 — child-on-child sexual violence and harassmentNot applicableNo pupil-to-pupil surface exists.
Annex B — online safety, including remote learningPartiallySpell & Grow can be used as home learning; teachers see practice outcomes, never a camera, microphone stream or location. We do not record pupil voices.
Annex C — role of the DSLYes, for how we interact with a school's DSLWe treat the school's DSL as the first contact for any concern about a specific child; our role is to supply evidence (audit-log slices, product-surface detail) when asked.
Age-appropriate design (ICO Children's code)YesHigh privacy by default; no nudge techniques toward sharing data; no geolocation; parental controls via the grown-up gate; child copy avoids score/fail/wrong/test; data minimisation per the DPA.
Data minimisationYesNo pupil contact data, photos or free-text behaviour notes; SEN tags are opt-in per school with the school's Article 9 condition confirmed first.

Named lead

How we respond to a concern

  1. Within 1 working dayAcknowledge

    We reply to say we have your report, normally within one working day.

  2. NextLook into it

    The DSL reviews the product surface involved and, where relevant, the audit log. If the concern is about a child at a school, we tell that school's DSL. If a child may be at risk of harm, we contact the school's DSL, the local authority or the police straight away.

  3. Within 5 working daysReply

    We send the person who reported it (and the school's DSL, where involved) a written reply, normally within five working days, saying what we found and any change we are making.

  4. AfterwardsRecord

    We keep a written record of each concern and what we did. Lessons are reflected in this statement.

Tabletop drill

Per REQ-6 of the trust-and-compliance sub-PRD (amended 19 October 2026), the response process is tabletop-drilled before the first paying school goes live. No drill has been run yet. The drill and its lessons are recorded in the sub-feature changelog.

Reporting concerns

What we do not do

Cross-references