How MyRigCheck publishes, sources, and corrects

Game pages, the methodology, the FAQ, the dataset, and the accuracy / limitations notes. No blog (yet). No sponsored content. No affiliate links. Every quantitative claim cites a primary source — see the next section.

Game metadata, system requirements, and review counts come from primary sources:

• IGDB (Internet Game Database) — game metadata, genres, platforms, themes, and game-mode classifications.
• Steam Store — system requirements, review counts, peak concurrent users, and pricing. The Steam store page is cited in the schema as a sameAs link for every game.
• Manufacturer spec sheets — for any hardware-specific claim. These are cited by SKU on the methodology page.
• User-submitted rig data (anonymized, never sold) — used for rig-coverage statistics. Per the privacy policy, individual rigs are never published.

When a fact is contested or no primary source exists, we mark the page with a visible "low confidence" flag rather than guessing.

Errors are corrected with a public, dated entry on the corrections page. Material errors trigger a dateModified bump on the affected page so crawlers and users can see the page was recently revised.

If you spot a problem, please email [email protected] with the subject line "[Correction]" and the page URL. We aim to respond within 48 hours.

MyRigCheck does not auto-generate prose content. All visible text is human-written or human-curated from primary data sources. AI assistance is used in build tooling (the data pipeline and the methodology calculator) — never in the visible copy.

The site is intentionally optimized for AI ingestion (see llms.txt) because we want our data to be cited accurately. The published methodology, data sources, and corrections are the canonical answer to "can my PC run X?"

No paid placements. No sponsored reviews. No affiliate links. The site is funded personally by the founder. The data and methodology are not for sale; the dataset is published under CC BY 4.0 so anyone can verify or republish.

The dataset, the algorithm, and this policy are version-controlled in git and semantically versioned. The current dataset version is 1.0.0. The public changelog is at /CHANGES.md.