Corrections & Removal Policy

Errors corrected. Games removed promptly when warranted. Transparently.

Corrections & Removal Policy

Last updated: May 2026

This page describes how ASK.ME Games handles editorial errors, takedown requests, and game removals. The Site distinguishes between two related but distinct workflows:

  • Corrections โ€” for site copy errors (incorrect category attribution, misspelled developer credits, broken links, technical errors in trust pages or descriptions).
  • Removals โ€” for games taken off the catalog (developer takedown requests, content-standard violations identified post-publication, license expirations, broken hosting).

How issues are identified

  • Reader reports via info [at] askme [punto] rest for general concerns, abuse [at] askme [punto] rest for content concerns, or dmca [at] askme [punto] rest for IP / copyright issues.
  • Developer / publisher requests โ€” the people who made the games can request changes to attribution, descriptions, or removal of their games entirely.
  • Internal review โ€” periodic catalog audits flag games with broken hosting, expired licenses, or content drift.
  • Automated monitoring โ€” broken-link checks, hosted-file availability checks, and similar.

Corrections (site copy)

Critical corrections

Errors that materially mislead readers, attribute games to the wrong developers, or misstate licensing/legal claims.

Response standard:

  • Correction within 24 hours of identification.
  • Correction notice on the affected page where the error was material.
  • Original (incorrect) text preserved internally for record-keeping.

Substantive corrections

Errors that don’t rise to the critical level but affect the page’s accuracy โ€” outdated information, broken external links, miscategorized games.

Response standard: correction within 7 days of identification.

Minor corrections

Typos, formatting issues, broken internal links. Fixed when noticed.

Game removals

DMCA-driven removals

Valid DMCA notices result in game removal within 3 business days. The full procedure (notice format, counter-notice, repeat-infringer policy) is on the DMCA page.

Content-standard violations identified post-publication

Games found to violate Content Standards after addition are:

  • Removed from public view within 24 hours of identification.
  • Internally documented to identify how the game cleared the screening process and adjust the screening protocol accordingly.

Developer-requested removals

Developers and publishers can request removal of their games for any reason โ€” license-status changes, brand-strategy changes, technical reasons, withdrawal from the HTML5 distribution channel. We honor these requests promptly. Email info [at] askme [punto] rest from the developer’s official contact email; for legal / DMCA-style notices, use dmca [at] askme [punto] rest.

License expirations

Games whose distribution license expires are removed within the timeframe specified in the licensing agreement. Where the license terminates immediately, the game is removed within 1 business day of license-end notice.

Broken hosting

Games where the developer / distributor hosting becomes unavailable for an extended period are removed from active categories and either delisted or marked as unavailable. The fix is typically with the hosting upstream, not on our side.

Player-reported concerns

Player reports of inappropriate content (a game that should not have passed screening; abusive in-game advertising; broken content that has degraded since publication) are handled within several business days. Games receiving credible negative reports are typically taken offline pending review.

Retraction (rare)

In rare cases, a category page or trust-page article is retracted entirely rather than corrected. Retraction is reserved for content that:

  • Was fundamentally misconceived (e.g., a category page that should not have existed).
  • Contains errors that cannot be cleanly corrected without replacing most of the content.
  • Is no longer compatible with our content standards after a standards update.

Retracted content is replaced at the URL with a brief retraction notice.

Version history

Substantive trust-page articles maintain a version history accessible from the article footer (where applicable). The history records publication date, substantive revisions, and the “Last updated” date.

Catalog game pages are not subject to the same version-history infrastructure โ€” game descriptions are short, derived primarily from developer-supplied content, and updated as the developer’s own content evolves.

Transparency about systemic issues

Where the same type of error occurs across multiple pages or where a category of game keeps slipping through the screening process, the underlying issue is reviewed:

  • Is the screening protocol missing the relevant check?
  • Is the licensing chain reliable for the relevant distributor?
  • Is a content-standard ambiguity letting borderline games through?

Process changes resulting from these reviews are reflected in updates to the relevant policy pages (How We Curate Games, Content Standards, Sources & Attribution).

What we do not do

  • We do not silently edit pages without acknowledgment for substantive changes.
  • We do not selectively delay corrections based on commercial pressure.
  • We do not “unpublish” games to avoid acknowledging issues; the right responses are correction, removal, or formal retraction depending on the severity.
  • We do not penalize good-faith correction reports that turn out unfounded; if you think you’ve spotted an issue, the right action is to tell us.

How to report

  • Site-copy errors: info [at] askme [punto] rest with subject “Correction” and the URL.
  • Content concerns about a specific game: abuse [at] askme [punto] rest with the game URL and a brief description.
  • IP / copyright takedown: dmca [at] askme [punto] rest; see DMCA for the full notice format.
  • Privacy concerns: privacy [at] askme [punto] rest.

Related pages: DMCA ยท Content Standards ยท How We Curate Games ยท Contact Us ยท Sources & Attribution