Trust

How QuestHub reviews games

A game is not considered reviewed merely because it opens in an iframe. QuestHub records specific evidence and displays gaps instead of filling them with assumptions.

Source and license

Each game record points to an upstream source repository and a pinned source commit. Code-license facts, asset-review status, commercial-use allowance, and attribution requirements come from the fixed game-library snapshot. Code and media rights are reviewed as separate concerns.

Build, media, and network behavior

QuestHub uses reviewed, vendored gameplay media rather than remote screenshots. The current games passed build and network review with no approved external connections. Runtime capabilities and restrictive Content Security Policy rules are recorded per game.

Compatibility meaning

The current verification covers real Google Chrome desktop and mobile contexts, including the listed keyboard, mouse, or touch inputs. Browsers shown as unverified are not silently treated as passed. A device badge means the recorded check passed on the listed date; it is not a universal compatibility guarantee.

Separate runtime and first input

The game Runtime uses a separate origin and loads only after Start. The Portal accepts runtime messages only for the active frame, exact origin, Bridge schema, game ID, and launch ID. Recently Played is written only after the Runtime reports a real first gameplay input—not on page load, iframe load, or Start click.

What “verified” does not mean

Each game detail page shows its exact last-tested date, source commit, compatibility facts, and any metadata gaps available in the catalog.