Editorial standards and corrections
DirtyPhish publishes cybersecurity explainers and original browser games. Kofi A., its creator, is responsible for the material published on the site.
Research and responsibility
AI tools assist with research, drafting, game development and illustrations. AI-generated claims require checking. Agreement between AI tools is not treated as independent verification.
Our editorial standard is to check technical claims against relevant primary sources, including official documentation, security guidance and original research. Articles should distinguish established facts from opinion and illustrative examples.
This policy describes the standard we apply as we prepare and update material. Its publication does not mean every older article has received a new technical review. Sources and dated correction notes help readers see what supports a claim and what has changed.
Professional input
Experienced cybersecurity professionals in the creator’s network sometimes provide article ideas, practical context and feedback on technical questions.
These conversations do not mean every article has received formal expert review. Where a reviewer is credited, the credit will describe their actual contribution and appear with their permission.
Games and educational limitations
DirtyPhish games simplify cybersecurity concepts for entertainment and learning. Their fictional mechanics do not reproduce every detail of real security work.
The games do not inspect or protect your device, assess your organisation’s security or replace professional advice. Worked examples labelled fictional or synthetic are learning scenarios, not reports of a real incident or a test performed by DirtyPhish.
Updates and corrections
Publication dates show when an article first appeared. Review dates change only after a genuine content check.
We assess reported errors and correct confirmed inaccuracies. Material corrections receive a brief dated note explaining what changed. Minor spelling and formatting fixes do not normally require a public correction note.
Spotted an error?
Email support@dirtyphish.com with the article link, the passage concerned and any supporting source.
Do not include passwords, recovery codes, private customer information or other sensitive material in a correction report. For a security vulnerability, use the separate security reporting policy.