Three kinds of claim
The site makes three kinds of statement and treats them differently. Measurements about the games here - a deflect window is 0.18 seconds, a heavy attack recovers in 0.34 seconds, a brute costs three points of core integrity. These are read directly from the source code, not estimated from playing, and they are correct by construction.
Descriptions of behaviour - 'sentry turrets are more dangerous at range' or 'the sweep recovers too fast to punish'. These come from playing the game and are verified by playing it again specifically to check.
Judgements - 'this is the fastest way to improve', 'reload speed is the strongest first upgrade'. These are opinions formed from a lot of play. They are written so that a reader can tell they are opinions, and they are not dressed up as measurements.
What is verified, and what is not
Every factual claim about how a game on this site behaves has been checked against that game. That is a claim this site can make because it wrote the games.
It is not claimed that every sentence on the site has been independently verified by a second person. This is a small independent project and it does not have a separate fact-checking desk, and saying otherwise would itself be a false claim of the kind this page exists to prevent.
Statistics
No statistic appears on this site unless it can be traced to a real source. The only figures published are ones the site can measure directly: the number of games, the number of guides, and values read from its own code.
The site does not publish play counts, player numbers, popularity rankings or engagement figures, because it has no accounts and no server-side storage and therefore no way to measure any of them. Where a page might be expected to show such a figure - the popular games page, for instance - it explains what it is showing instead and why.
Where a general claim about games or players would need external data to support it, either a source is cited or the claim is not made.
Sources
The primary source for almost everything here is the site's own source code and the games themselves.
Where a guide refers to something outside this site - a browser API, a piece of standard game-design terminology, a general principle - it is written in terms a reader can check independently, and linked where a specific reference is genuinely useful rather than decorative.
Corrections
A factual error is fixed as soon as it is identified, and corrections take priority over publishing anything new.
Where a correction changes what a guide actually says rather than fixing a typo, the guide's updated date changes so a returning reader can see that something moved.
Reports of errors are welcome through the contact page and are the most useful messages the site receives.
Reviewing older content
When a game changes, the guides that describe it are reviewed and updated. This is the most common reason for a guide to change, and it is why the games and the guides are maintained together rather than separately.
Guides are otherwise reviewed periodically rather than on a fixed schedule. The site does not claim a review cadence it does not keep to.