How GameDataStream Verifies Information
Verification on GameDataStream means recording what could be checked, when, and what the result proves โ and what it does not. This page describes each check exactly, including its honest limits.
Metadata and media
Titles, release dates, genres, developers, publishers, posters, and screenshots are compared against Steam, SteamDB, and official sources before an entry goes live. Where data is incomplete, the game page simply shows less โ we would rather leave a field empty than invent it. If you notice a mismatch, report it from the game page.
Version history
Every release has a version number and a public change history. When a new build appears, the entry is updated and the previous version is recorded, so you can see not only the current build but what it followed. Recent version changes are collected on the updates page.
Download link availability
Sources are checked for network availability before and after publication. A successful check means the remote server responded โ it does not verify every byte hosted behind that link. Sources that stop responding are marked on the game page instead of staying as dead buttons.
File identity
Uploaded torrent files receive MD5 and SHA-256 identifiers, shown in the download block of the game page. A matching hash confirms the file you downloaded is identical to the one listed. Hashes check identity, not safety โ they are not malware scans.
Moderation and corrections
Community submissions and reports are reviewed before publication and after they are flagged. Broken links, wrong metadata, and suspicious files reported from game pages are checked and corrected. Repeated abuse of the reporting tools is handled under the community rules.
See verification in action
The checks above are visible on the site itself: version histories and hashes live on game pages, recent changes on the updates feed, and installation guidance in the FAQ. Something wrong or missing? Send us a note through the contact page.