Risk evidence intake file

Open a risk triage record

SLA target: 48h
Evidence first

No warning is published from a claim alone; evidence must be attached.

Right to reply

Identifiable companies can answer on record.

Decision path

Accepted reports become monitoring, warning, resolved notes or rejected signals.

Intake classification standard
Source

Who reported it and whether the source can be contacted.

Domain

Exact brand, URL, mirror domain or SEAL destination under review.

Evidence

Screenshots, URLs, transaction references, provider names or regulator records.

Outcome

Dismissed, monitoring, warning review, suspension review or revocation review.

Submitting false or malicious claims can harm the evidence process. We triage before publishing any public warning, watchlist record or validation posture change.

Evidence file opened

A submitted signal creates an internal risk file; it does not publish a warning by itself.

Role and domain checked

The affected operator, provider, infrastructure role or SEAL destination must be identifiable.

Publication threshold

Public movement requires evidence class, repeatability, response posture and risk category review.

Outcome is recorded

The file can close as rejected, monitoring, watchlist, warning review, suspension review or revocation review.

Best evidence

Live URL, archived page, payment reference, provider confirmation, regulator register or copied SEAL destination.

Useful context

Date, username or case reference, affected game/provider, communication trail and whether the company already answered.

Rejected signals

Anonymous claims with no domain, altered media, affiliate disputes, threats, spam or commercial pressure.

Triage before publication

A submitted report does not become a warning or watchlist entry until domain, role, source and evidence class are checked.

Evidence class is recorded

Reports are separated into public evidence, evidence on file, pending evidence and rejected evidence.

Company response path

Identifiable operators, providers or infrastructure partners can submit counter-evidence before escalation.

Decision outcome is controlled

Accepted signals move to monitoring, public warning, suspension review, revocation review or rejected-signal closure.

Validation rules
Exact domain

The validation file must match the casino or partner domain using the SEAL.

Exact role

Operator, provider and infrastructure SEALs are not interchangeable.

Live status

Verified, suspended, warning and revoked states must be visible publicly.

No self-issue

A company cannot generate or choose its own approved role.

Case lifecycle
Signal received

Evidence, source role, domain and risk type are recorded.

Evidence check

We compare SEAL link, provider claim, license claim and payment pattern.

Right to reply

Identifiable operators or suppliers can answer on record.

Public action

Outcome becomes watchlist, warning, resolved note or rejected signal.