LEG-01Policy set
Terms of Use
Defines the contractual conditions that apply to the corporate website and approved services.
ScopeCorporate and product-specific versions
Read draft Compliance Centre
Clear policies, accountable ownership and visible reporting routes.
The Compliance Centre organises the standards, responsibilities and review processes that help corporate and platform operations remain controlled as the group grows.
Compliance framework
Turn obligations into clear controls that teams can operate.
Compliance is strongest when policies, products, procedures, records and responsibilities support one another. A policy document alone does not show that a control works.
The group’s framework is designed to connect formal requirements with business ownership, implementation evidence, staff guidance and periodic review.
Policy catalogue
A structured library with scope, ownership and version control.
The final production centre will link approved documents and show each policy’s effective date, responsible owner, scope and latest review date.
DAT-01Policy set
Privacy Policy
Explains how relevant personal information is collected, used, protected and handled across approved activities.
ScopeCorporate baseline with regional notices
Read draft DAT-02Policy set
Cookie Policy
Describes the categories and purposes of cookies or similar technologies used on relevant websites and services.
ScopeWebsite and service specific
Read draft PLT-01Policy set
Acceptable Use Policy
Sets expectations for lawful, safe and responsible use of marketplace technologies and connected services.
ScopePlatform participation
Read draft PLT-02Policy set
Content Standards
Defines the content categories, behavioural standards and enforcement principles used in moderation workflows.
ScopeUser-generated content and communications
Read draft COM-01Policy set
Commercial Guidelines
Sets approved standards for advertisers, publishers, partners and other commercial participants where applicable.
ScopeCommercial and partner relationships
Read draft IP-01Policy set
Copyright Policy
Provides a structured route for intellectual-property notices, evidence review and appropriate platform response.
ScopeContent and rights management
Read draft FIN-01Policy set
Refund and Payment Policy
Explains transaction, refund, verification, dispute and settlement principles for approved payment-enabled services.
ScopeProduct and market dependent
Read draft FIN-02Policy set
KYC and AML Overview
Describes the risk-based identity, customer, screening and transaction controls that may apply to relevant products.
ScopeFinancial-integrity controls
Read draft The documents listed above remain subject to legal, operational and executive approval before public publication.
Governance lifecycle
A policy is only current when the surrounding control system is current.
Requirements should move through a repeatable lifecycle from identification and ownership to implementation, review and improvement.
- 01
Identify
Map the legal, contractual, operational and platform requirements relevant to the activity.
- 02
Assign
Give each policy, control and reporting obligation a named business owner and approval route.
- 03
Implement
Translate requirements into product rules, procedures, training, records and technical controls.
- 04
Review
Evaluate changes in law, products, markets, incidents and operating evidence on a defined schedule.
- 05
Improve
Update documents and controls, communicate changes and preserve a clear version history.
Accountability
Compliance responsibilities should be visible across the organisation.
Clear ownership reduces the risk that important obligations remain between departments or are assumed to belong to someone else.
Board and executive oversight
Approve material risk direction, receive significant compliance reporting and ensure responsible functions have authority and resources.
Policy owners
Maintain the accuracy, scope, review cycle and operational alignment of assigned policies and standards.
Product and engineering teams
Translate approved requirements into system behaviour, technical controls, records and user-facing experiences.
Operations and support teams
Apply procedures consistently, preserve evidence and escalate exceptions through defined reporting routes.
Legal and specialist advisers
Provide jurisdictional guidance, review sensitive matters and support decisions that require specialist interpretation.
All team members
Understand applicable responsibilities, complete required training and report concerns without concealing relevant information.
Reporting routes
Direct each concern to an accountable review channel.
The final route used will depend on the product, market and type of concern, but every channel should define required information, ownership and escalation.
User and customer concerns
Product-level support and complaint channels should capture the relevant service, account, transaction and evidence details.
Rights and policy notices
Dedicated workflows should route privacy, copyright, safety and other formal notices to the responsible review function.
Internal compliance concerns
Team members need a confidential route to raise suspected misconduct, control failures or policy breaches without retaliation.
Regulatory and authority requests
Verified requests should be handled by authorised personnel using documented identity, scope, legal and disclosure checks.
Regional governance
One corporate baseline, supported by market-specific requirements.
Corporate standards provide a common foundation, while local legal notices, contractual terms, payment requirements and reporting obligations may differ by country or product.
Regional material should identify the responsible legal entity, applicable service, effective date and jurisdiction rather than relying on broad global wording.
Explore the group’s growth approachPublication standard
No unsupported certification, licensing or regulatory claims.
References to registrations, licences, audits, certifications, legal entities, offices or regulated activities must be supported by current evidence and approved before publication.
Where a control or document is still being developed, the website should describe the direction accurately without presenting future work as an existing assurance.
Governance
Build policy and control requirements into the platform from the start.
Contact the group about compliance architecture, reporting routes, regional controls or policy implementation.