AI Spam Filters Allegedly Block Legitimate Emails Based on Biased Keyword Detection
October 22, 2020
This underscores the need for responsible AI governance and trustworthy AI practices in our digital infrastructure. For those interested in shaping Project Cerebellum's efforts towards harm prevention and guardrails for AI, consider joining us at JOIN US. By participating, you can help map, measure, and manage incidents like this to promote safe and secure AI communications.
Matched TAIM controls
Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls
- MEASURE 2.10 — similarity 0.626, rank 1. TAIM detail and related incidents →
- MEASURE 2.6 — similarity 0.624, rank 2. TAIM detail and related incidents →
- MAP 1.6 — similarity 0.616, rank 3. TAIM detail and related incidents →
- Alleged deployer
- yahoo, outlook, laposte, gmx, gmail
- Alleged developer
- yahoo, microsoft, laposte, google, gmx
- Alleged harmed parties
- yahoo!-mail-users, microsoft-outlook-users, laposte-users, gmx-users, gmail-users
Source
Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/83
Data source
Incident data is from the AI Incident Database (AIID).
When citing the database as a whole, please use:
McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.
Pre-print on arXiv · Database snapshots & citation guide
We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.