What belongs here
Responsible disclosure contact, safe methodology notes, and public summaries that do not reveal targets, private evidence, or unresolved findings.
Why it fits
Security work is a repeated theme, but the public version needs strong privacy and scope boundaries.
Evidence
- Public resume material references verified HackerOne reports.
- Local automations and skills show repeated authorized web, API, APK, and JS recon workflows.
- The public site already separates security contact via security@ashton.com.au.