Corrections & Removal Policy

Last updated: May 2026

This page describes how Game Hub Arena handles two related categories of catalog change: corrections (fixing errors in existing game pages) and removals (taking games out of the catalog). The procedures differ: corrections are typically routine maintenance; removals can be DMCA-driven, content-standards-driven, broken-game-driven, or developer/rights-holder-requested.

Part 1: Corrections

How corrections are identified

Reader reports. Most catalog errors are caught by readers. Email info [at] gamehubarena [punto] fun with subject line Correction.
Source-feed cross-referencing. Periodic spot-checks against the source feeds (CloudArcade, GameDistribution, etc.) surface metadata inconsistencies.
Broken-game detection. Automated checks identify games that have stopped working (broken asset hosting, deprecated dependencies); broken games are removed or restored.
Developer updates. Where developers update their games (new versions, bug fixes), the catalog metadata may need updating.

Severity classification

Critical errors

Errors that materially mislead users about what a game is. Examples: wrong developer attribution; wrong game-page genre that affects discovery; content rating that is meaningfully too lenient (a violent game rated for general audiences); thumbnail / preview image for a different game entirely.

Response standard:

Correction within 24-48 hours of identification.
Correction notice in the change log.
Where the error has been propagated through search-engine indexing, the corrected entry is what indexers update to over the following week.

Substantive errors

Outdated metadata; missing genre tag; incomplete rating flag; description that no longer matches the current version of the game; broken or stale internal links.

Response standard: correction within 7 days of identification. Note in change log.

Minor errors

Typos, formatting issues, cosmetic issues. Production-level rather than substantive errors.

Response standard: fixed when noticed.

Content-rating reviews

Reader feedback that a content rating is wrong (too lenient or too strict) triggers a content-rating review. The framework on Content Ratings is applied; the rating is adjusted if the framework supports the change. Where feedback comes from a parent concerned that a game is mis-categorized, the review is expedited.

Part 2: Removals

DMCA-driven removals

Where a rights holder issues a valid DMCA notice, the procedure on DMCA applies:

Acknowledged within 7 business days.
Substantive response within 3 business days for procedurally-valid notices.
The complaining party is notified of the action taken.
Counter-notice procedure is available where the takedown is believed to be in error.

Content-standards-driven removals

Where games are identified as not meeting Content Standards (a real-money gambling game that slipped through, an adult-content game disguised as casual, a malware-adjacent game), the game is removed.

Response standard: removal as soon as identified. Where the game was added based on insufficient screening, the screening process is reviewed.

Broken-game removals

Games that no longer work technically:

Developer asset hosting has gone offline.
Game depends on deprecated browser features (Flash, deprecated WebGL extensions).
Source feed has removed the game.
Modern browser security policies have made the game unrunnable.

Broken games are removed from the catalog (rather than left as broken-experience entries that frustrate users).

Developer-requested removals

Where a game developer requests removal of their game from the catalog (without invoking DMCA), the request is honored:

Developers may request removal because they have updated the game and removed the older version, because they have changed distribution licensing, because they have decided to take the game offline.
The request is honored within 3 business days.
No DMCA notice is required for developer-requested removals; we trust developer requests.

Source-feed removals

Where a source feed (CloudArcade game feed, GameDistribution feed, etc.) removes a game, our catalog is updated accordingly. The catalog tracks source-feed changes and reflects them in catalog state.

User-requested removals

Where individual users have a specific concern about a game in the catalog (e.g., a content-rating dispute that escalates), the request is evaluated individually. Most are resolved through the corrections process (rating adjustment) rather than removal.

Restoration after removal

Where a removal was made in error, restoration is possible:

DMCA counter-notice procedure per DMCA.
Content-standards reconsideration where new information indicates the original removal was wrong.
Developer re-engagement where the developer changes position about distribution.
Source-feed restoration where the source feed re-includes the game and our automated import re-adds it.

Change log and version history

The catalog maintains a change log for substantive corrections and removals. The log is internal but available to reviewers (rights holders, regulators) on legitimate request.

What we do not do

We do not silently remove games to avoid acknowledging error or takedown.
We do not refuse takedown requests based on convenient interpretations of fair use.
We do not selectively apply standards based on a game's popularity.
We do not retain games that violate categorical exclusions on Content Standards.

How to report an error or request removal

Catalog corrections: info [at] gamehubarena [punto] fun with subject line Correction.
DMCA notices and rights-holder takedowns: dmca [at] gamehubarena [punto] fun per DMCA.
Content-rating disputes: info [at] gamehubarena [punto] fun with subject line Rating dispute.
Inappropriate game reports: abuse [at] gamehubarena [punto] fun.
Privacy / parental concerns: privacy [at] gamehubarena [punto] fun.
Developer removal requests: info [at] gamehubarena [punto] fun with subject line Developer removal request and reasonable proof of authorship.