QEI Child Protection
Verify the age or safety signal. Do not build a map of the child’s digital life.
QEI Child Protection brings together two research directions already presented by Institute 1 April: privacy-preserving age verification and event-based safety mechanisms such as QEI Child Key, Safe Check, Silent Alert and Child SOS.
Can a child be better protected without requiring every platform to know exactly who that child is or continuously track where they are?
Verify what is needed.
- An age category such as under 13, 15+ or 18+
- Whether an adult has a verified authorised role in a protected environment
- A protected safety or distress event from a trusted child credential
Do not expand the purpose.
- Sending a child’s full identity to every website
- A central log of every site, message or digital movement
- Continuous location tracking simply because a child uses QEI
From request to verifiable result.
Age/access request
A service asks only for the age status required for access.
Protected QEI proof
The credential returns a verified category instead of a full identity package.
Safety mode
When voluntarily activated, a Child Key could expect a Safe Check or accept an SOS trigger.
Escalation by rule
A missing or distress signal could start a predefined, proportionate verification path rather than permanent tracking.
Technology without boundaries is not the QEI objective.
Protection without surveillance
Safety features should be event-based and purpose-limited, not a default surveillance channel.
Minimum disclosure
Platforms should receive an age or role result when that is all they need.
Authorised response
SOS or escalation paths require clearly defined authorised recipients and procedures.
Fail safely
Loss of signal, battery or connectivity must not automatically be treated as proof of danger.
A research concept. Not an implemented system.
QEI Child Protection is a research concept. It cannot replace parents, schools, social services, police, courts, platform safety teams or child-protection professionals. Its role would be limited to testing whether privacy-preserving verification and carefully governed safety signals can add a useful layer of protection.