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.

Evidence required

Screenshots, transaction IDs and chat logs make a case actionable.

48h triage

We triage scope first, then request more evidence if the file is incomplete.

Public impact

Repeated evidence-backed cases can change validation posture or trigger a warning.

Case control protocol

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.

Private intake first

Player identity, raw evidence and sensitive documents enter private triage before anything becomes public.

Public file after redaction

Only moderated summaries, SLA posture, response state and outcome posture are published.

Operator answer is attached

Operator replies can change outcome posture, but they remain attached to the same case record.

Pattern affects validation

Repeated evidence-backed cases can move a dossier into watchlist, warning or SEAL review.

Public case file standard

Every published case must show scope, SLA, response status and outcome posture.

Scope

Operator, category, disputed amount and jurisdiction context are recorded.

SLA

Triage target and operator response window are visible in the public file.

Response

Operator answer, counter-evidence or no-response state is attached.

Outcome

Resolved, unresolved, rejected or escalated posture remains visible.

Public dispute authority standard

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.

Evidence threshold

A case is actionable only when dates, transaction references, operator replies or reproducible facts can be reviewed.

Operator answer window

When evidence is sufficient, the operator response window is visible and no-response remains part of the public posture.

Outcome ledger

Resolved, rejected, unresolved and escalated outcomes are appended; settlement does not erase the public record.

Validation impact

Repeated evidence-backed cases can affect watchlist status, warning publication or SEAL review.

Admissibility

A case must include operator, timeline, category and evidence path before it can become public.

SLA posture

Triage and operator-response windows remain visible until a closure or outcome note is attached.

Response record

Operator/admin replies are appended to the file and cannot replace the original player summary.

Validation effect

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.

0
Public cases
48h
Triage target
7d
Operator window

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.

Case escalation standard

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.

Private intake

Player identity and sensitive evidence stay private.

Public case

Only redacted, moderated summaries are published.

Pattern escalation

Repeated cases can trigger watchlist monitoring.

Enforcement

Confirmed harm can affect public file and SEAL status.

By submitting you confirm the information is accurate.

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.