Spell & Grow · Trust · Privacy
What we collect, what we keep, and what we never see.
Spell & Grow is a trading name of Igloo Labs Limited, a private limited company registered in England and Wales (company number 16931262; registered office 1st Floor, Gallery Court, 28 Arcadia Avenue, London, N3 2FG, United Kingdom; ICO registration reference ZC163696, controller name “IGLOO LABS LIMITED”). The schools portal is a processor acting on behalf of each subscribing school (the controller) under our Data Processing Agreement. For any data-protection enquiry, contact our data protection lead at dpo@spellandgrow.app. We respond within two working days. You also have the right to complain to the Information Commissioner’s Office at ico.org.uk/make-a-complaint or on 0303 123 1113.
Status: v1.0 — pending legal review
The data-handling commitments below match the live product. Counsel has not yet reviewed the wording. Mirrors plans/features/schools-portal/trust-and-compliance/policies/privacy.md.
What we collect
| Category | Data | Why |
|---|---|---|
| Pupil identity | First name, last name, year-band, optional SEN tag | To roster classes and personalise spelling lists. No DOB beyond month and year; no contact details. SEN tags are special-category data: off by default, and the school confirms its Article 9 condition before switching them on. |
| Pupil practice | Word attempts, accuracy, timing, error patterns | To drive Smart Lists and class insights. |
| Teacher / admin identity | Email, name, role | To authenticate and authorise. |
| School metadata | Name, year groups, term-calendar overrides | To bound RLS scopes and configure terms. |
| Audit metadata | Event type, actor UUID, IP hash, coarse user-agent class | To honour the GDPR Article 5(2) accountability principle. |
Google Classroom (optional)
A school administrator can connect Google Classroom. We then read the classes taught by the person who connects it and the first and last names of students in the classes they choose to import; we create spelling assignments and set each one’s grade to the class’s average completion. Disconnecting in School settings asks Google to revoke our access and deletes the stored tokens. What we access, store and share, and our Limited Use commitment, are set out under “Google user data” in the family privacy notice.
Children who move from a family to the school
When a family deletes a child, or their account, while the child is confirmed in one of the school’s classes, the child is not deleted. Their profile (first name, last name, month and year of birth, year group), practice history and progress move into the school’s records as a school-managed pupil, and the school becomes responsible for them under the Data Processing Agreement (clause 2.2A). The family’s own lists, certificate messages and sign-in details are removed. Copies of home practice the school received stay with the school when a family unlinks or deletes the child. Deleting the pupil in the portal deletes the child.
What we never see
- Pupil PII never appears in audit-log metadata. The audit emitter accepts UUIDs only; names, emails, and class names are explicitly rejected at runtime.
- OpenRouter receives word/list text and aggregate confidence signals, and ElevenLabs receives word/sentence text — no pupil identifiers.
- Vendor-side advertising and tracking cookies are hard-prohibited.
How long we keep it
| Category | Data | Why |
|---|---|---|
| Account + pupil rows | Until the school deletes or terminates | Backup periods are listed on the sub-processor register. |
| Home practice copies | Kept when a family unlinks or deletes the child | Deleted with the pupil. |
| Anonymous spelling records | Indefinite, without names or dates | Kept with age, school and year group when practice is deleted, for reporting and to improve the service (DPA clause 12.3). |
| Class data after deletion | Cascade-deleted immediately | Via ON DELETE CASCADE through the pupil graph. See /school/data-controls. |
| Audit log | Currently unbounded | A 2-year rolling window is the adopted target and will be stated here once the scheduled deletion is live. |
| OpenRouter / ElevenLabs payloads | Not retained for model training (vendor data policies; contract terms being confirmed at DPO review) | Stream-only contracts. |
| Vendor logs | 30–90 days | Per vendor — Vercel, Supabase, Resend, Sentry. See /compliance/sub-processors. |
Your rights
- Access (Article 15). Per-pupil SAR export at
/school/data-controlsproduces a downloadable ZIP of every row tied to a pupil. - Erasure (Article 17). Per-pupil delete at
/school/data-controlscascades through the FK graph; class-level delete via “Delete this class and all its data”. - Portability (Article 20). School-wide “Export everything” archive at
/school/data-controls. - Rectification + restriction. Email dpo@spellandgrow.app.
- Withdrawal of consent. The schools portal does not rely on consent as the legal basis — it relies on the school’s contract; raise a request via the school’s DPO.
Sub-processors and transfers
Listed verbatim at /compliance/sub-processors. Nine entries — Supabase, Vercel, ElevenLabs, Microsoft (Azure AI Speech), Resend, Sentry, PostHog, OpenRouter and Apple (push notifications) — each with hosting region, transfer mechanism, and data categories. Google supplies Gemini models downstream of OpenRouter. Google Classroom, when a school connects it, is the school’s own system and is listed separately as an integration. Schools listed as data controllers receive at least 30 days’ written notice before a new sub-processor is engaged.
Security
- All data at rest is encrypted in Supabase EU.
- Row-Level Security policies scope every table read to the caller's school / organisation / role.
- Service-role keys live in Vercel-encrypted environment variables; only Server Actions and Edge Functions touch them.
- Every security-relevant action is audited.
- IP addresses appear only as salted SHA-256 hashes in the audit log.