EMTREE.LIVE
Player Protection

Dispute Policy

How support and operations should investigate payment, game, account, and social disputes with evidence and audit trails.

StatusDraft
MarketPH
ReviewLegal needed

Round Proof

Game disputes need round ID, seed proof, bet state, ledger entries, and game version.

Payment Evidence

Payment disputes need provider reference, ledger entry, user identity, and review notes.

Support Timeline

Every dispute should keep timestamps, owner, status, evidence, decision, and player communication.

Escalation

Complex or regulated disputes escalate to compliance/legal before final decision.

01

Draft

Use this product draft to define operational requirements and missing data fields.

02

Review

Have Philippines gaming counsel, privacy counsel, and compliance owners review before launch.

03

Approve

Version the approved policy and connect it to registration, wallet, game, support, and admin flows.

04

Audit

Log player consent, admin actions, reviews, escalations, and policy-version changes.

Risk Review Matrix

SignalExamplesActionReal-Money Gate
Age/JurisdictionUnder 21, non-PH, KYC mismatchReject or restrictHard block
KYCFailed document, liveness mismatch, duplicate identityManual reviewHard block
AMLVelocity, structuring, duplicate accounts, unusual withdrawalsOpen AML caseHard block
DeviceVPN, proxy, impossible travel, new risky deviceChallenge or reviewSoft/hard block
Payment OwnerMaya/GCash name mismatchHold transactionHard block
Responsible GamingLimit reached, cool-off, self-exclusionRestrict play/marketingHard block
Launch Gate

Draft, not legal approval

This is an implementation and operations scaffold. Real-money launch still requires counsel-approved policies, licensing path, payment approval, KYC/AML readiness, and game certification.