Corrections policy

What counts as a correction

A correction addresses a factual error, a misleading omission, a calculation mistake, a broken product distinction, or a source interpretation that changes the answer. Routine copy edits and formatting improvements are not presented as factual corrections.

How an issue is evaluated

Potential errors are checked against the relevant live source and, where possible, a second independent first-party reference such as a changelog, API response, rulebook, or market rule. Feedback is useful evidence of a problem; it is not automatically accepted without verification.

How a correction is published

• The visible statement is fixed in the article.
• The review or modified date is updated when the change is material.
• Related pages, tables, examples, metadata, and structured data are checked for the same error.
• A brief note is added when readers would otherwise misunderstand why a material conclusion changed.

Source updates are not always corrections

If Polymarket changes a fee, supported network, geographic status, API limit, or product name after an article was accurately reviewed, the page needs an update rather than a retraction. The new copy should identify its current review date and avoid implying that the earlier product state never existed.

Contact limitation

No monitored public corrections address was provided for this release, so the site does not invent one. Verifiable feedback received through any future contact channel published by the site operator should be handled under this policy.