HackerOne vs Bugcrowd AI policy
HackerOne encourages AI across the whole research workflow, while Bugcrowd allows GenAI only if no confidential information reaches it. Both make you verify every report, and neither asks you to disclose AI use.
| HackerOne | Bugcrowd | |
|---|---|---|
| AI use | Permitted and encouraged | Allowed |
| Verify by hand | Required | Required before you submit |
| Confidential data in AI tools | No AI-specific rule. You stay responsible for what third-party tools produce, and the program policy may add limits. | Not allowed if confidential information reaches the tool. |
| Fully automated reports | Hackbots must not run fully autonomously | Not accepted as valid submissions |
| Disclose AI use | Not required | Not required |
| Penalty for AI slop | Final warning, then a 12-month ban, then a permanent ban | Rejection, a 30-day suspension, and a cap of 6 reports a week under 50% accuracy |
| Program rules on top | Yes, with program-level sanctions | Yes, the program brief wins |
HackerOne
"HackerOne permits and encourages the responsible use of AI tools throughout the research workflow, including for learning, reconnaissance, vulnerability discovery, proof-of-concept development, and report quality improvement."
HackerOne Code of Conduct, read November 18, 2026
"Hackbots must not operate in a fully autonomous manner."
HackerOne Code of Conduct, read November 18, 2026
Bugcrowd
"Do not use GenAI tools (applications and services that rely on generative artificial intelligence models to create new and original content, such as text, images, audio, and code [example: ChatGPT]) except in a manner that avoids disclosure of confidential information"
Bugcrowd Code of Conduct, read November 18, 2026
"You manually review and validate any vulnerability report you've created with the help of GenAI tools before submitting it. (Reports determined to have been submitted without human review are subject to rejection.)"
Bugcrowd Code of Conduct, read November 18, 2026
Which rule bites first
On Bugcrowd, confidentiality comes first. Decide where program data may go before you paste anything. On HackerOne, the bar is proof. A report closes as N/A when it "doesn't contain a valid reproducible issue, and the security implications have not been demonstrated" (report states).