Minimum-necessary inputs
Define the smallest player and game context needed for each recommendation workflow rather than collecting data without a concrete purpose.
Trust by design
Community health belongs in the matching decision.
Social recommendations can affect player experience and opportunity. The platform must give studios clear boundaries, controls, and evidence for how those decisions are made.
Design principles
Developer-controlled policy
Keep eligibility, blocking, reporting, and enforcement aligned with the game's authoritative systems and community standards.
Explainable factors
Make the factors behind a recommendation available for evaluation, tuning, and governance.
Scoped player references
Prefer pseudonymous, game-scoped identifiers over directly identifying player information.
Measured outcomes
Evaluate group stability and safety outcomes, not only whether an API produced a technically valid response.
Human accountability
Product and safety owners must remain able to review policy, investigate issues, and change or disable recommendation behavior.
Requirements still to be defined
Production data flows, retention, deletion, access control, incident response, availability, and audit requirements will be agreed with design partners before live player data is used. This page states design direction, not a claim that a production compliance program has already been completed.
Website privacy
The current public site does not include advertising trackers or submit its contact form to a website backend. Read the website privacy notice for details.