Editorial standards and corrections
Read HighRTP’s standards for sourcing RTP claims, labelling worked examples, preserving scope and dates, disclosing affiliate links and correcting errors.
Updated 17 November 2026Answer the question and show the assumptions
A guide should give a direct answer, explain the relevant definition and show a worked example when arithmetic clarifies the issue. Expected values must not be presented as guaranteed session outcomes. A higher return should be compared on the same turnover and rule basis before any claim about lower expected cost is made.
Hypothetical payout models and sample calculations are labelled as examples. They must not be attributed to named games without matching evidence. Unknown active settings, mode costs or payout probabilities should remain unknown rather than being replaced with plausible figures.
Use sources for the claims they actually support
A studio source can support a published product specification. A regulator’s provision supports a scoped requirement. A statistical reference supports a method under its assumptions. Each link should appear with enough context for readers to understand its role.
Avoid universal claims about all casinos, all licensed products or all demos when the source covers a particular jurisdiction or implementation. A public fairness implementation, for example, can describe a seed algorithm without establishing operator solvency. A certificate or badge needs a matching product, version, date and scope before it can substantiate a specific verification claim.
Make updates and authorship understandable
The guide byline identifies the HighRTP editorial team. It does not imply an unsubstantiated academic qualification, independent laboratory review or a named expert’s approval. Original publication dates are kept separate from substantive update dates.
A content review date describes a review of the page and its sources; it is not a promise that every linked operator was tested that day. A retrieved-data timestamp describes the associated feed. These dates should remain attached to the relevant claim rather than being treated as interchangeable freshness badges.
Keep commercial context separate from evidence
Some links to operators may be affiliate links. That commercial context is not evidence that a game uses a maximum RTP setting, that an offer has positive expected value or that a withdrawal is guaranteed. Readers should review eligibility, wagering and withdrawal terms before relying on an offer.
A list should describe what is being compared. Selected source-linked product examples should not be labelled a complete market ranking, and popularity data should not be described as a prediction of future payouts.
How to request a correction
Use the contact page and identify the URL, specific statement, public source and date. For game figures, include the complete title, studio, version and mode where available. Explain whether the concern is a published specification, an active setting or a measured sample.
Keep private account information out of a public correction request. A source-linked discrepancy is more useful than a screenshot containing only a session balance. A correction should address the underlying statement and any related calculations or links, rather than merely changing a badge.