Editorial policy

Voice

We write like a consumer-comparison desk, not a fan site or a storefront. We do not tell readers to buy. We show prices, claims and risks and let them decide. Vendors are referred to by their trading name, without adjectives.

Facts and sourcing

• Every price in a post carries the date it was read from the vendor page and matches the entry in our dataset on that date.
• Patch versions, season dates and enforcement statements link to a primary source (publisher patch notes, help centre article, official blog) or, failing that, to a named press report.
• We do not invent quotes, statistics or version numbers. Where a vendor did not publish a number we say "not published".
• Review counts and star ratings are reported as vendor claims ("claims 4.9 from 1,477 reviews") and are never emitted as structured review data.

Things we never write

• That any script or device evades detection, is "safe" or is "ban-proof".
• That a script "works" on the current patch. We write that the vendor "states" or "claims" support, with a date.
• Anything that omits platform-enforcement risk where it applies (Fortnite, Call of Duty).

Equal treatment

Every vendor — large creator storefront, aggregator library, single-product site, reseller or Patreon — gets the same template, the same fields and the same scrutiny. When we flag a concern we state what the page appears to show, link the source and use "appears to" rather than asserting intent.

Scheduling and updates

Posts are published on a schedule. Each shows a "Published" and "Last updated" date. When a price or status in a post changes materially we update the post, bump the date and note the change at the point in the text where it matters.

Corrections

Send corrections to desk@cronusmarket.com. We fix errors of fact as soon as we can verify them and note material corrections in the affected page. See also how we track and the disclosure.