Editorial policy
One rule governs everything published here: if we cannot verify it, we do not show it. This page explains how that rule is applied, where it came from, and what to do when we get something wrong.
Where it came from: the 2026 integrity purge
In June and July 2026 we audited the entire site against one question: can every visible number, date and claim be traced to a real source? Everything that failed was removed or rebuilt, not patched over:
- News posts that could not be verified against primary sources were unpublished, in every language.
- Tools that displayed simulated data were rebuilt on real server-side sources or had the fake parts deleted.
- A dormant price-adjustment mechanism was removed from the pricing pipeline outright, so the capability to publish altered prices no longer exists in the code.
- Freshness labels were switched from build dates to data-capture timestamps, with visible staleness warnings.
- Outbound marketplace links were converted to plain, visible anchors you can inspect before clicking.
That audit is the origin of this policy. The rules below exist so none of it can happen again.
Sourcing
- Item facts (names, wear ranges, rarities, odds, contents) come from the CS2 game files and Valve’s official localization files.
- Prices come from our licensed market-data provider and are published with capture timestamps, as documented in the pricing methodology.
- Marketplace facts come from each platform’s own documentation and are periodically re-verified (last pass: July 1, 2026).
- News and guides cite primary sources: Valve announcements, official patch notes, platform statements. No claim ships on rumor alone.
- We make no expertise claims we cannot show the work for. "We analyzed N" appears only with the analysis linked.
AI assistance, disclosed
We use AI tools to draft, translate and maintain content at the scale this catalog requires. The boundaries are strict: every number, price, date and fact on the site comes from our data pipelines and named sources, never from a language model’s memory. AI-drafted text is reviewed by the team before publication, and English and Russian are written to read natively, not machine-translated. A language model is never allowed to invent prices, reviews, events or statistics — if a fact is missing from our data, the page shows its absence.
Corrections
- Report errors to contact@steamdb.com. We respond within 48 hours.
- Data errors (a wrong fee, a stale status, a mismatched price) are fixed at the source dataset, so the correction propagates to every page and language at once.
- Substantive corrections to editorial claims are acknowledged on the page rather than silently rewritten.
Update cadence
- Prices update per snapshot; the capture time and staleness state are visible next to every table.
- Marketplace facts are re-verified in scheduled passes, with the verification date printed on each dossier.
- Guides and explainers carry their dates and are revised when game mechanics change, not on a cosmetic schedule.
Language policy
English, Russian and Brazilian Portuguese are written and reviewed by the team. The skins catalog renders in 28 languages using Valve’s own localization files for item terminology; free-form editorial content is not published in a language until it has had native review, which is why tools and long-form pages currently exist in English, Russian and Brazilian Portuguese only.
Safety boundaries
- No gambling promotion. Case-odds content is consumer information: we show the odds and the expected loss, never "how to profit from opening".
- Payment-rail availability is described as dated fact ("works / does not work as of {date}"), never as instructions for circumventing restrictions.
- Skins are not investment advice. We publish market data; decisions and risk are yours.