Our Editorial Methodology

Last updated 2 October 2026

Project Nim publishes research-based information about slots and casino apps for readers in Malaysia. This policy explains what our assessments cover, what a source can establish, and what you should not infer from a guide.

What “review” means here

A review is an editorial assessment of available information, game mechanics and limitations. It is not a security audit, a recommendation to deposit, or proof that a casino will pay a withdrawal. We do not claim hands-on experience unless the page identifies the tested product, date, device or environment, method and observations. A screenshot alone is not a test record.

Our current guides do not include documented deposit or withdrawal tests. We use no invented reviewer names, customer reviews, star ratings or numerical scores. About Project Nim explains who is responsible for this publication.

How we choose and use sources

  1. Start with the exact product. Distinguish a developer, a casino operator, an app distributor and an individual game. Similar names and sequel titles can refer to different products.
  2. Prefer primary material. Use the developer's game page or rule sheet for mechanics, the relevant regulator's register for licence details, and official organizations for support contacts.
  3. Keep claims within the evidence. A developer's statement about certification is attributed to that developer unless the certificate or register has also been checked. Marketing copy does not establish an operator's safety or local legal status.
  4. Resolve disagreements. Look for differences in version, configuration, date or jurisdiction. If a precise claim cannot be supported, omit it or state the uncertainty rather than selecting the most attractive figure.
  5. Make sources usable. Link the material close to the relevant statement or in a clearly labeled sources section. A homepage link is not evidence for an unrelated number.

How we compare games

We separate layout, payout mechanics, bonus features and presentation. Reel count describes the grid; paylines or ways describe how combinations pay; volatility describes the spread of outcomes. Those dimensions should not be collapsed into a single “best” score.

Examples in a comparison illustrate these differences. They are not a measured popularity ranking or a promise of better results. A page describing trends must explain its evidence and time period; otherwise we describe themes or examples without claiming market-wide popularity.

RTP, versions and the limits of a demo

A published RTP figure applies to a particular game configuration, not necessarily every version carrying that name. When quoting a specification, identify the game, the available configuration and the source. Do not average a studio's catalogue without a defined dataset and calculation.

RTP describes a long-run theoretical return, not the result to expect from one session. Our numerical teaching examples are labeled as examples. A demo can illustrate controls and features, but a short run cannot verify RTP, prove fairness or predict real-money outcomes. See the UK Gambling Commission's explanation of RTP.

Licensing and Malaysian context

A software supplier's licence is not an operator's licence. A foreign licence is not Malaysian authorization, and an identifiable brand is not a guarantee about every website using its logo. We link to the legal context and support information separately from the description of a game.

Paid placements and drafting tools

Our guides currently contain no paid placements or affiliate links. Any future paid relationship will be disclosed where relevant. Commercial terms must not be represented as independent evidence.

Software-assisted tools are used for drafting and editing. Generated prose is not a source. We do not present software assistance as personal playing experience or independent professional review.

Updates and corrections

The last-updated date records an editorial change to the page, not a promise that every external offer or product remains unchanged. Original publication dates are retained. Formatting and navigation changes alone do not refresh an article's content date.

Report a possible error to support@project-nim.com with the page URL, the specific statement and a source if available. We assess the evidence, correct supported errors and add a correction note when a change materially alters a conclusion. We do not promise a fixed response time.