Player identity, raw evidence and sensitive documents enter private triage before anything becomes public.
Public case intake
Open a public case file.
Submit evidence for withdrawal delays, KYC disputes, disputed terms, fake SEALs or game-integrity concerns. Every case is triaged before it can affect the public record.
Screenshots, transaction IDs and chat logs make a case actionable.
We triage scope first, then request more evidence if the file is incomplete.
Repeated evidence-backed cases can change validation posture or trigger a warning.
A complaint becomes public only as a controlled case file.
The complaint center is not a comment wall. It protects private evidence while preserving a public dispute record when a case reaches moderation and evidence threshold.
Only moderated summaries, SLA posture, response state and outcome posture are published.
Operator replies can change outcome posture, but they remain attached to the same case record.
Repeated evidence-backed cases can move a dossier into watchlist, warning or SEAL review.
Every published case must show scope, SLA, response status and outcome posture.
Operator, category, disputed amount and jurisdiction context are recorded.
Triage target and operator response window are visible in the public file.
Operator answer, counter-evidence or no-response state is attached.
Resolved, unresolved, rejected or escalated posture remains visible.
A complaint is handled as a public case file, not a review comment.
The case center is designed to preserve evidence, record operator response posture and show whether the dispute creates a wider validation risk.
A case is actionable only when dates, transaction references, operator replies or reproducible facts can be reviewed.
When evidence is sufficient, the operator response window is visible and no-response remains part of the public posture.
Resolved, rejected, unresolved and escalated outcomes are appended; settlement does not erase the public record.
Repeated evidence-backed cases can affect watchlist status, warning publication or SEAL review.
A case must include operator, timeline, category and evidence path before it can become public.
Triage and operator-response windows remain visible until a closure or outcome note is attached.
Operator/admin replies are appended to the file and cannot replace the original player summary.
Repeated unresolved patterns can move the operator into watchlist, warning or SEAL status review.
Public case file desk
Public case lifecycle, not a private inbox.
A case should show what happened, whether the operator answered on record, and how the evidence file ended. We publish only moderated, evidence-backed records; private player data stays private.
Submitted
Player submits evidence, amount, category and timeline.
Triage
We check scope, specificity and whether more proof is needed.
Operator answer
The operator is asked to answer with evidence, settlement proof or counter-evidence.
Public outcome
Resolved, unresolved or escalated patterns are visible in the public case record.
A case can become a validation signal.
Single cases are handled carefully. Repeated evidence-backed patterns can move into watchlist, warnings or SEAL status review.
Player identity and sensitive evidence stay private.
Only redacted, moderated summaries are published.
Repeated cases can trigger watchlist monitoring.
Confirmed harm can affect public file and SEAL status.
Public dispute ledger
Published public case files
Published records are redacted and evidence-led. Each file shows SLA posture, operator response state and outcome posture when available.
No public case files yet
New submissions enter private triage first. A case becomes public only after moderation, evidence review and privacy redaction.