What this policy establishes
Factual correction checklist
Keep the exact page URL, disputed sentence, primary source URL, document title and access date. Explain whether the information varies by country, account status, product or login state.
Casino investigation requests
Provide the exact brand name and official domain, plus any known operator or licence claim. Similar names and mirrors must be separated before research begins.
Complaint evidence
Preserve dates, terms in force, transaction status with sensitive fields redacted, support replies and the operator’s final position. Explain what remedy was requested and whether the matter was resolved.
Factual correction checklist
Keep the exact page URL, disputed sentence, primary source URL, document title and access date. Explain whether the information varies by country, account status, product or login state.
State the correction you believe the evidence supports. A marketing page, screenshot without URL or unsupported assertion may be logged as a lead but cannot automatically replace a primary record.
Casino investigation requests
Provide the exact brand name and official domain, plus any known operator or licence claim. Similar names and mirrors must be separated before research begins.
A request does not predetermine a verdict or publication date. Priority depends on reader demand, potential harm, evidence availability and whether the product is still operating.
Complaint evidence
Preserve dates, terms in force, transaction status with sensitive fields redacted, support replies and the operator’s final position. Explain what remedy was requested and whether the matter was resolved.
A single report is not presented as representative of all players. It may contribute to a pattern only when comparable, relevant reports can be responsibly grouped.
Security and phishing reports
For impersonation or phishing, preserve the exact hostname, redirect path and a screenshot showing the browser address bar. Do not reconnect a wallet or continue interacting merely to collect more evidence.
Urgent account-security problems should be reported to the relevant operator and wallet provider through independently verified channels.
Information we will not request
Do not send passwords, seed phrases, private keys, one-time codes, full identity documents, unredacted payment cards or full wallet balances. The editorial desk does not need control of an account to review a public claim.
If a future investigation requires sensitive evidence, a separate secure process and explicit handling notice must exist before submission.
Response and publication principles
A submission may be acknowledged, researched, incorporated with attribution or declined when it cannot be verified. Sending material does not guarantee publication, removal or a score change.
Credible corrections are evaluated consistently whether they come from a reader, operator, regulator or commercial partner.
Common questions
Why is there no public email yet?
The permanent domain and mailbox are not active. Publishing an invented or temporary identity would undermine the evidence standard.
Can I send account credentials so you can investigate?
No. Never send passwords, codes, private keys, seed phrases or identity documents.
Will every casino request become a page?
No. Requests inform prioritization, but publication depends on evidence, relevance and editorial capacity.