Reader reports
Correction Policy
Last updated: May 2026
What this page tells you: how to report an error, what we review, how we prioritize correction requests, and what changes after a correction is accepted.
What this means for you
If something on EmailLeaked looks inaccurate, outdated, unclear, or unsafe, we want to know. Security guidance changes over time as services update settings, breach details are clarified, and safer account-protection steps become available.
What we correct
We review reports about incorrect breach details, outdated account-security steps, broken links, unclear risk labels, missing disclosures, inaccurate dates, unsupported claims, and guidance that could cause readers to take the wrong action.
How to request a correction
Send the page URL, the section that needs review, and the reason you believe it should be changed. If you have a reliable source, include it.
Do not send passwords, full identity documents, or private account screenshots.
How we review reports
We compare the report against the page text, available source material, service-provider documentation, and reader-safety impact. Corrections that affect account security, privacy, money, identity documents, or breach exposure are prioritized.
What changes after a correction
When a correction is accepted, we update the affected page and adjust the modified date where the page template supports it. For larger changes, we may revise nearby guidance so the page remains clear and complete rather than patching one sentence in isolation.
Editorial limits
EmailLeaked provides educational security guidance. We cannot verify every individual account case, remove accurate public-interest breach information on request, or provide legal, financial, or law-enforcement advice.