Editorial Policy

Who maintains this

Gaxload is run by a small curation team. Nobody is paid by a developer to place, promote or rank a listing, and there is no paid placement anywhere on the site — ordering comes from the sort you pick, nothing else.

What gets verified, and against what

Every listing carries a set of structured fields. These are the ones we check against a primary source before an entry is published, in order of how often they are wrong:

• Version — checked against the developer's own release announcement (their Patreon post, itch.io devlog, Discord release channel or project site). We do not take a version number from a re-uploader.
• Platforms — a platform badge is only added when a build for that platform actually exists in the release. Community Android ports are listed as platforms but flagged in the entry text where the developer did not build them.
• Engine — taken from the build itself (folder layout and executable) rather than from a description, because engine determines save behaviour and we surface that.
• Changelog — reproduced from the developer's own notes for that version. Where a release ships without notes, the field stays empty rather than being invented.
• Languages, status and censorship — taken from the release page. Status moves to Abandoned only after a documented gap or an explicit statement from the developer.

What we do not verify

We do not test-play every build, and we do not audit game files for behaviour beyond a virus scan. Screenshots come from the developer's own release material. Ratings are aggregate community input, not an editorial score.

Mirrors

Download links point at third-party hosts. A mirror is checked when it is added and re-checked whenever a report comes in against it. Broken mirrors are removed rather than left in place, and an entry with no working mirror is unpublished rather than shown as a dead end.

Re-check cadence

• Entries with an Ongoing status are re-checked against the developer's channel when a new version is reported.
• Any entry that receives a report is re-checked before the report is closed.
• The "Last update" date shown on a listing is the release date of the version we verified — not the date we edited the record.

Corrections

The Report Issue button on every game page is the fastest route; it files the report against that exact entry. Reports are triaged within roughly 48 hours. Copyright notices are handled separately and faster — see the DMCA page.

If we get something wrong, we correct the record rather than deleting it quietly. Developers can request changes or removal from an address connected to their project at [email protected], and that request is honoured without argument.

AI-generated content

Listing copy is written and reviewed by a person. We do not publish machine-generated descriptions of games nobody on the team has looked at, because the failure mode — plausible text describing a build that does not exist — is exactly the thing this catalog is meant to protect you from.