A submitted signal creates an internal risk file; it does not publish a warning by itself.
The affected operator, provider, infrastructure role or SEAL destination must be identifiable.
Public movement requires evidence class, repeatability, response posture and risk category review.
The file can close as rejected, monitoring, watchlist, warning review, suspension review or revocation review.
Live URL, archived page, payment reference, provider confirmation, regulator register or copied SEAL destination.
Date, username or case reference, affected game/provider, communication trail and whether the company already answered.
Anonymous claims with no domain, altered media, affiliate disputes, threats, spam or commercial pressure.
A submitted report does not become a warning or watchlist entry until domain, role, source and evidence class are checked.
Reports are separated into public evidence, evidence on file, pending evidence and rejected evidence.
Identifiable operators, providers or infrastructure partners can submit counter-evidence before escalation.
Accepted signals move to monitoring, public warning, suspension review, revocation review or rejected-signal closure.
The validation file must match the casino or partner domain using the SEAL.
Operator, provider and infrastructure SEALs are not interchangeable.
Verified, suspended, warning and revoked states must be visible publicly.
A company cannot generate or choose its own approved role.
Evidence, source role, domain and risk type are recorded.
We compare SEAL link, provider claim, license claim and payment pattern.
Identifiable operators or suppliers can answer on record.
Outcome becomes watchlist, warning, resolved note or rejected signal.