What to include
Send the public URL, a concise description of the issue, the non-sensitive input used, the result received and the result expected. For a changing source or competitor feature, include the official page that now differs.
What not to send
Do not send passwords, access tokens, identity documents, private contracts, medical records or confidential business files. A minimal recreated example is safer and usually easier to investigate.
How reports are checked
We reproduce the issue against the current public page, review the implementation or calculation, check cited sources and compare the visible guidance with the real interface. If the report concerns an external service, we revisit its official public page.
How confirmed errors are handled
Confirmed material errors are corrected in the relevant tool, metadata, article or comparison. The affected workflow is retested and the visible updated date changes where that helps readers understand the revision.
Disagreements and clarifications
Some results depend on assumptions, locale, browser support or file structure. If the original result is supportable but the explanation is unclear, we may clarify the limitation or example rather than change the output.