Bias Bounties and Algorithmic Bug Bounties

Security bug bounties typically ask researchers to find specified technical vulnerabilities within an authorized scope. Algorithmic bias bounties adapt the idea by asking external participants to identify or demonstrate potential harms in a model. Twitter’s 2021 challenge focused on its image saliency/cropping model: Twitter provided the model and crop-generation code, invited quantitative and qualitative assessments, and used a limited prize pool. Its scope was the crop/display process, not every recommendation or moderation system. A bounty can discover failure modes a developer missed, improve reproducibility and invite perspectives outside the organization. It can also skew effort toward harms that are easy to demonstrate with available access and time. Participants may lack deployment data, documentation or representative samples; a prize contest can reward novelty over severity or create incentives to overstate results. Absence of a submitted finding is not proof of safety. A one-off event is not continuous monitoring, and participants should not access real users’ sensitive data without authorization. Useful rules define the model version, affected decision, allowed data, threat/impact categories, evaluation criteria, privacy restrictions, disclosure channel, response timeline and how fixes will be verified. The organization should pay for valid work, protect good-faith testers and explain selection criteria. Review should involve people with methodological, domain and lived-experience perspectives. Reports should distinguish observed disparity, plausible mechanism, downstream harm and legal violation. The result is an input to risk management, not a fairness certificate or substitute for internal testing, consultation, appeal rights or regulator oversight.