Recognising a child is only useful if the service changes what that child can do — and who can reach them.
A participating service does not “join UuLApp” merely by checking an age. It adopts a set of interaction rules based on a school-verified minor credential.
Platforms can apply the protocol without losing a friendly user experience.
The verification step happens in the background. The visible product experience can still feel bright, welcoming and easy to understand for children and families.



The service receives a trusted child-safety signal, then enforces the correct experience.
The minimum integration should answer: Is this user a school-verified minor? Which age band or education group applies? Is the credential valid? Which child-interaction policy must this service apply?
What an UuLApp-enabled service should implement.
Do not accept self-declaration as a UuLApp child credential
A public signup form cannot manufacture “verified minor” status. Only a valid school-originated credential can.
Separate adult and child discovery
Adult accounts must not be suggested to, matched with, or allowed to search for children inside child-only discovery systems.
Restrict direct communication
Friend requests, DMs, voice chat, video chat and similar contact should follow the child’s permitted age-group policy.
Apply age-group matchmaking
Multiplayer games can use verified age bands so minors play and communicate within the approved group rather than unknown mixed-age pools.
Keep professional adult contact separate
Teacher, counsellor or safeguarding access — if the service provides it — must use separately verified, clearly labelled, purpose-limited professional roles, outside ordinary child socialisation.
Respect revocation immediately
If a school or authorised process revokes or expires a credential, the service must stop treating it as a valid minor credential.
A child can play the same game — without being placed in the same communication pool as unknown adults.
UuLApp does not need to own the game. The publisher keeps the game, account system and gameplay. Its UuLApp integration changes matchmaking and communication for verified minors.
- Player signs into the game and presents a valid UuLApp credential.
- The game receives only the verified status/age band it needs.
- Matchmaking selects the permitted minor age group.
- Voice/text chat follows the same age-group rule.
- Adult accounts remain outside that child-only interaction pool.


A child can still use a social service, but the service has a reliable basis for child-safe contact rules.
- Verified minors can be placed in a protected minor mode automatically.
- Search, discovery and recommendations can exclude adult-to-child social contact.
- Direct messaging can be limited to approved minor age groups or existing school relationships.
- Public content policies remain the responsibility of the social service; UuLApp specifically strengthens identity and interaction control.
Help make verified child interaction a common internet standard.
Children do not need another isolated app. They need the services they already use to recognise a trusted child credential and act on it.
Platforms, social networks & games
Integrate the school-verified signal into discovery, matchmaking, chat, friend requests and child-only areas.
Schools & education authorities
Become the trusted source of minor verification and help define accountable issuance, renewal and age-band rules.
Governments, NGOs & child-safety bodies
Evaluate the protocol, support common standards and help build the learning, alert and support layers around verified users.
Adoption means implementation — not simply displaying a UuLApp badge.
A service that presents itself as UuLApp-enabled is expected to recognise the school-verified child credential and apply the required child-only and age-group interaction rules. Wider adoption can grow through voluntary integration, industry standards, institutional agreements and public policy.
Technology provider, game studio or social platform?
Contact UuLApp to discuss the protocol model, required child-safety controls and an implementation specification.
