Corrections Policy
Effective 11 August 2026.
What to report
Report a factual error, outdated limit, broken internal link, accessibility barrier, privacy contradiction, or reproducible tool result to darth9081@gmail.com. Include the exact URL, affected text or control, non-sensitive input, expected result, actual result, browser, and a primary source where relevant.
Verification
A report is reproduced and compared with the current implementation and primary documentation. Account-specific cases are not presented as global platform defects without evidence.
How corrections are published
Material website or tool corrections are recorded in the Site Changelog. A page review date changes only when that page was actually checked and materially changed. Minor spelling or presentation changes need not receive a misleading new factual-review date.
Privacy and security
Never include passwords, tokens, webhook URLs, private server exports, payment details, or unnecessary personal data in a report.
Correction priority
Security, privacy, accessibility, broken downloads, wrong calculations, and materially outdated Discord requirements receive priority over wording preferences. A clear source-backed correction can be made directly; an uncertain report may require reproduction or additional evidence before the page changes.
Correction format
A material correction should fix the tool, visible explanation, metadata, examples, and structured data together wherever they contain the same error. The site should not leave a correct FAQ beside an incorrect tool warning. Significant changes are summarized in the Site Changelog without exposing a reporter’s personal information.
Disagreements and appeals
If a report is not adopted, the reporter may send a current primary source or reproducible test case to darth9081@gmail.com. This process covers ThisCord Tools content only; Discord account or enforcement appeals must go to Discord.
