For social networks, games & websites

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.

Better product design

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.

Children using devices
Social discovery can become age-aware.
Family using devices
Parents can understand what the rules do.
Group of children
Child-only spaces can look positive, not restrictive.
Integration principle

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?

Schoolverifies student
UuLApp IDverified minor + minimal age attributes
Servicevalidates credential
Interaction rulesadult exclusion + allowed age groups
Required service behaviour

What an UuLApp-enabled service should implement.

1

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.

2

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.

3

Restrict direct communication

Friend requests, DMs, voice chat, video chat and similar contact should follow the child’s permitted age-group policy.

4

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.

5

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.

6

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.

Gaming example

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.

  1. Player signs into the game and presents a valid UuLApp credential.
  2. The game receives only the verified status/age band it needs.
  3. Matchmaking selects the permitted minor age group.
  4. Voice/text chat follows the same age-group rule.
  5. Adult accounts remain outside that child-only interaction pool.
Children enjoying games together
Young people communicating in a positive environment
Social network example

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.
Adopt UuLApp

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.

Important

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.

Discuss integration