Protection enforced in the database — not just hidden on screen.

Grounded in voluntary child participation, non-punitive responses to absence and protection of children's data under the Children Act 2022 and national positive parenting guidance.

General consent registry

Separate parent consent, child assent, media consent and purpose-specific permissions, each with version, scope and withdrawal status

Safeguarding report access

Role-based access for the coordinator and head teachers acting as safeguarding leads

Disability information

Held in separate protected support records, not on the learner register

Absence triggers

Configurable thresholds with contextual assessment, not automatic judgement

Notifications

Privacy-preserving — never exposing sensitive child information

Child help button

Named responsible officer, 24-hour response deadline and escalation

Audit logs

Append-only records of changes to cases, referrals, consents, support records and roles

Volunteer verification

Independent verification with evidence notes; self-verification is blocked in the database

Non-negotiable safeguards

No sensitive information in ordinary SMS or email notifications
No public identification of children — learners use codes and initials
No automated diagnosis of disability, abuse or mental-health conditions
Child wellbeing check-ins are always optional
No public rankings of individual teachers, parents, learners or schools
No automatic case closure — closure needs a completed action, a verified follow-up and a recorded outcome
Help requests carry a named responsible officer and a 24-hour response deadline
Append-only audit records for sensitive cases, consents and role changes
Volunteers cannot verify their own activities
Permissions enforced inside the database, not only hidden on screen

A data protection impact assessment and documented retention and deletion policies are required before operational deployment.