Esports.NGO — Esports for Good
Our impact areas →Support VYBEPartner area →
Esports.NGOBecome a partner →

#PLAY4GOOD / GAME DEVELOPERS & PUBLISHERS

Better player experiences.
Safety built into the release.

A practical route from age-appropriate design to moderation, staff training and auditable evidence — for studios, publishers and youth-facing digital services.

Co-founded by ESPORTS.NGO and Valvur.AI · With Passport.GG as ecosystem partner

01 / START WITH THE EXPERIENCE

Map the whole player journey.

Look beyond the age gate: installation, discovery, lobbies, chat, purchases, player-created worlds, creator tools, AI characters and account deletion. Agree which organisation owns each surface, including outsourced moderation and companion communities.

Assess before release

Identify who can access each feature, what can go wrong and how you will test it. Record residual risks and an accountable release decision.

Protect in the product

Use age-appropriate defaults and clear controls. Do not make a child find the help centre before they can block unwanted contact.

Prove the response works

Test a report from first click to human triage, user feedback and appeal. Review whether safeguards actually work after deployment.

02 / RECOMMENDED CONTROL DOMAINS

Turn intentions into release evidence.

A proposed VYBE readiness framework for developers and publishers. Assign a named owner and keep evidence for the precise service, version, audience and market being assessed.

DomainRecommended actionOwnerEvidence to prepare
Age, access & consentMap age groups and service risks. Use proportionate age assurance and guardian permission where required; verify authority without collecting extra identity data.Product + privacyAge-flow tests, consent/revocation paths, data-flow and retention map.
Contact & communityChoose age-appropriate chat and discovery defaults. Restrict risky adult–child contact, make block/mute visible and cover voice, text, groups and UGC.Product + trust & safetyDefault-setting captures, abuse scenarios and end-to-end reporting tests.
Moderation & responseGive reports a human owner. Define urgency, escalation, appeals, staff access and safe evidence handling; train teams before launch.Trust & safetyPlaybooks, training record, report receipt and appeal test.
Privacy & securityMinimise collected data; control access and retention. Protect accounts, secure dependencies and review third-party SDKs.Engineering + privacyThreat model, privacy impact review, access-control tests and deletion checks.
Commerce & persuasionMake real costs clear, offer spending controls and purchase confirmations, and review pressure tactics, subscriptions and chance-based features.Commerce + legalPurchase/refund walkthrough, pricing screens and market-specific review.
AI & synthetic mediaDisclose AI interaction; test age-inappropriate outputs, coercive or dependency cues, memory and privacy settings, and paths to human help.AI + productAdversarial test cases, model/version record, memory controls and release decisions.
Accessible supportUse child-readable explanations and accessible reporting. Involve young people and families in testing through a safeguarded research process.Research + accessibilityUsability findings, accessibility issues and tracked fixes.
Change & accountabilityReassess material feature changes, review incident trends and publish meaningful information about protection and its limits.Safety owner + leadershipRisk register, release gates, remediation owners and review dates.

03 / COMPLIANCE STARTS WITH SCOPE

Match the rules to your features and markets.

FrameworkWhat to establishOfficial starting point
EU · DSA minors protectionsDetermine whether your service or features qualify as an online platform and which obligations apply, including relevant exemptions. Assess the risks created by actual child access. DSA duties do not apply identically to every game.Commission guidelines →
UK · Online Safety ActAssess UK links and user-to-user functionality. Where in scope, address illegal-content duties and children’s access and risk assessments, protections and records.Ofcom gaming guidance →
Data protection & children’s designDetermine applicable EU/UK privacy law and the UK Children’s Code’s scope. Review lawful bases, data minimisation and high-privacy defaults; parental permission is not a substitute for the whole assessment.ICO defaults guidance →
Other markets & product featuresCheck local privacy, consumer, advertising, gambling and age rules, plus platform terms. Assign counsel or a qualified reviewer to your market map.Record the source, owner and review date.

This is a readiness guide, not a legal determination. Content ratings, age assurance, a technology integration and a voluntary badge each address different questions; none alone establishes legal compliance.

04 / THE VYBE BADGE PATHWAY

Integrate. Train. Pledge. Demonstrate.

  1. Define the assessment scope

    Identify the service, version, age range, countries and features covered.

  2. Integrate and maintain Valvur.AI

    Valvur.AI is required to earn and retain the badge. Agree the required controls and integration responsibilities; document behaviour when a safety dependency is unavailable.

  3. Train people and sign the safety pledge

    Prepare product, engineering, moderation and support teams. Give each escalation a human owner.

  4. Submit evidence and resolve gaps

    The proposed process includes independent review and selected tests. Only approved services would receive badge assets for their verified scope; renewal and material changes require review.

The initiative is in development.

Using Valvur.AI is mandatory but does not automatically earn the badge. The public Safety Passport and independent assessment arrangements are being developed. Sponsors do not purchase an assessment outcome.

Read the proposed Charter →

05 / PREPARE THE FIRST REVIEW

A usable first evidence pack.

Your next actions0 of 8 marked for planning

Optional planning aid. Ticks are saved only in this browser; they are not a safety score, audit or badge approval. Do not enter personal or incident data.

TAKE THE NEXT STEP

Build safety into your next release.

Tell us your product type, markets and highest-risk features. We can scope the Valvur.AI integration and the proposed VYBE pilot evidence requirements.

Discuss the developer pilot →

Opens your email app. No application is submitted on this page. Please do not include children’s personal information or incident evidence.

SOURCES & REVIEW

Built on practical guidance.

These recommendations combine VYBE’s proposed programme design with the official guidance below. Sources inform the content; the organisations linked here have not endorsed VYBE. Guidance reviewed 13 November 2026.

ONE CONNECTED COMMUNITY

Keep the safety conversation going.