A national approach to KIDS implementation
A national programme can make trustworthy proofs usable across services while preserving public authority and children’s rights.
The proposed public responsibilities
Article 31 would require privacy-preserving parental-responsibility attestations based on authentic national sources, free for guardians. It also addresses inclusive access, alternative procedures and free availability of at least one EU age-verification solution.
Article 33 envisages national strategies for confidential assistance, information and digital literacy, building on Safer Internet Centres. These measures connect technical access with support and education.
A modular implementation package
| Workstream | Programme component | Public value |
|---|---|---|
| Trusted proofs | Connect existing wallets and authorised national sources. | A reusable route without a new child identity database. |
| Inclusion | Assisted access and alternative authority documentation. | Access for families with limited digital skills or atypical circumstances. |
| Developer adoption | Open interfaces, sandbox and reference integrations. | Less repeated work across local providers. |
| Support | Local-language guidance and established help channels. | Practical assistance beyond an age gate. |
| Evaluation | Aggregate outcomes and independent review. | Evidence without routine monitoring of individual children. |
Governance that supports trust
Procure defined modules with open interfaces, exportable data, security requirements and an exit plan. Keep issuing authority, software operation, safeguarding and independent assessment distinct. Involve children, disability organisations and families in usability evaluation.
EU hosting may support procurement requirements, but location alone does not establish data sovereignty or legal compliance. Examine subprocessors, administrative access, keys, retention and transfers.
Discussion
A Valvur national adoption package
| Workstream | Practical deliverable | Public value |
|---|---|---|
| Trust infrastructure | Connect national authority sources and accepted wallet/proof routes. | Free, inclusive routes remain public; providers get a repeatable integration. |
| Developer adoption | Reference game/AI implementations, sandbox and conformance scenarios. | Lower implementation friction and inspectable control coverage. |
| Family + school resilience | White-label family access, KIBI lessons, teacher tools and parent guidance. | Support safe participation and help-seeking beyond the age gate. |
| Local context | Evaluate local languages and slang; agree national referral routes. | Measure who is missed rather than assuming English-language quality transfers. |
| Sovereignty + procurement | Deployment options, data minimisation, open interfaces, portability and exit terms. | Avoid dependency on a single private supplier or central child-surveillance database. |
| Evaluation | Independent testing and privacy-preserving outcome reports. | Separate process success from proven harm reduction. |
Who needs to be at the table
Digital-policy and wallet teams, the competent regulator, child-protection services, education authorities, accessibility representatives, data-protection specialists and the participating providers have different responsibilities. Start with one authority route and a municipality or school cohort; expand only after evidence of safe operation. See the full stakeholder analysis.