Risk-based by design
Controls should reflect the service, user journey, market, data and potential harm rather than applying one process everywhere.
Trust
Safety, compliance and security operating as one connected system.
The group’s trust framework connects platform integrity, policy governance and technical security so that responsible growth is supported by clear controls and accountable decisions.
Three trust pillars
Separate disciplines with shared ownership and evidence.
Each pillar has its own teams and controls, but risk signals, policy decisions, technical records and escalations must connect across the wider platform.
01
Trust & Safety
Prevention, age assurance, moderation, reporting, complaints, fraud controls, enforcement, appeals and operational learning.
Explore pillar 02Compliance Centre
Policy ownership, governance cycles, reporting routes, regional controls and a structured corporate policy library.
Explore pillar 03Security
Identity and access controls, protected data, secure development, monitoring, response and recovery practices.
Explore pillarOperating principles
Controls should be understandable, proportionate and reviewable.
The trust framework is designed to move beyond isolated policies and tools by connecting requirements to product behaviour, operational ownership and decision records.
Accountable ownership
Important decisions need a named owner, documented authority, clear escalation routes and evidence that can be reviewed.
Human oversight
Automation can support prioritisation and consistency, while sensitive decisions remain governed by authorised people.
Regional implementation
Core standards should remain consistent while local law, language, payment systems and operating conditions are addressed explicitly.
Shared evidence
Important outcomes should connect to the policy, control, reviewer and evidence behind them.
Trust and safety cases, compliance reviews and security events may involve different teams, but each benefits from controlled records, defined retention, authorised access and a clear escalation history.
Public claims, metrics and assurance statements should only be published after their definitions, evidence sources and approval responsibilities are confirmed.
Review the corporate policy libraryTrust architecture
Build risk controls into the platform from the beginning.
Discuss trust and safety, compliance or security requirements with the appropriate corporate team.