KWS is a suite of tools and services provided to developers for free to help them manage youth audiences. Our Parent Verification and Consent Management products are relied on by some of the largest games and platforms in the world. Kids Web Services Ltd is part of the Epic Games group.
Kids Web Services (KWS) platform enables web publishers and app and game developers to implement kid-safe registration and authentication, parental consent and parent verification services in compliance with data privacy laws. KWS combines optimised parent workflows with the most appropriate age verification methods for each jurisdiction and use case, so that developers have maximum flexibility in their approach to kids’ privacy compliance.
AgeGraph from Epic Games / Kids Web Services (KWS)
KWS is a parental consent, parent verification, and age verification platform owned by Epic Games. It is designed for developers and platforms to embed into their own user journeys using APIs and SDKs, supporting global compliance where services must treat children differently or obtain verifiable parental consent. KWS provides consent management tooling to capture and manage parental permissions.
KWS includes an interoperability feature called AgeGraph. This is a network of verified parents or guardians where a successful adult verification can be reused across other services that also use KWS, reducing repeated verification. AgeGraph achieves this by storing a hashed representation of the parent’s email address alongside their verified status, so a parent can be recognised (for verification purposes) when the same email address is used again in another KWS-powered flow, without revealing that email address in readable form.
This approach differs from user-held credentials (such as passkey-based age tokens or wallet-based proofs). Instead, it is a platform-mediated reuse model that primarily supports reusability of verified adult status for parents or guardians across participating services, rather than a general-purpose age token that a user can present anywhere.
The graph is populated as follows:
- A service integrates KWS and triggers a parental consent or adult verification flow
• The parent or guardian completes verification using a method enabled by that service, for example payment card, ID document, or another approved method
• During this process, KWS derives a hashed identifier from the parent’s email address
• KWS stores the hashed email together with the outcome of the verification, for example verified adult or verified parent
• No readable email address is stored or shared with relying services
When another service also using KWS initiates a parental verification flow:
- The parent enters the same email address
• KWS hashes it in the same way
• If a matching hash exists in AgeGraph and the prior verification is still valid under policy, the parent can be recognised as already verified
• The service receives a confirmation result from KWS without repeating the full verification process