REVIEW METHODOLOGY

How CSGONAV Reviews CS2 Platforms

Our review process separates first-party rules, interface evidence, original calculations and public-reputation signals so readers can see what is verified, what is interpretation and what can change.

01
FIRST-PARTY SOURCES

Start with the platform's own current rules

We prioritize current Help Center pages, Terms, bonus rules, responsible-use pages, payment documentation and live product pages. Older documents are kept only when they add useful historical context.

02
LIVE INTERFACE EVIDENCE

Use real interface captures when they add information

Screenshots are used to explain current product flows, not to imply live-money testing that did not happen. Official promotional art is labeled separately from interface evidence.

03
CONFLICT CHECKING

Do not hide when two official pages disagree

If current first-party documents conflict, the review states the difference and usually recommends the more conservative interpretation until the live account experience confirms otherwise.

04
CALCULATIONS

Turn marketing numbers into user-readable math

When a promotion has a measurable unlock formula, we show the arithmetic and clearly distinguish the calculation from a prediction of profit or loss.

05
PUBLIC REPUTATION

Treat reviews as signals, not proof

Trustpilot and similar public feedback can surface recurring friction such as KYC, payment or withdrawal complaints. These reports remain user claims unless independently verified.

06
FRESHNESS

Update dates only when the content is actually re-checked

We do not change a visible review date just to make a page look fresh. Dynamic bonuses, limits and regional availability are still marked as items the reader should verify live.

Review pages are not forced into one template

The information architecture should follow the strongest user question for that platform. This reduces cookie-cutter affiliate content and makes comparisons more useful.

Scroll to Top