About · Open Data · Methodology
About & Open Data
Our commitment to transparent, real-time antisemitism tracking — and free access to the data behind it.
“Between annual ADL reports and two-year-delayed FBI statistics, there is a blind spot in antisemitism data. No freely accessible, real-time, open-data tracker with a public API existed — so we built one. We are not a replacement for the ADL’s verified, analyst-reviewed research. We are the real-time signal between their reports: open data that anyone can query, built in public, updated every day.”
— Delilah Hollander, Founder
Methodology disclosure: This data is aggregated from public news sources via automated systems and has not been independently verified. It should be used as a monitoring signal, not a definitive record.
Affiliation Disclaimer: This project is an independent initiative. We are not officially affiliated with the SCN, JFNA, or the ADL, though we utilize their public reporting among our 3000+ primary sources.
01 · Definition
Working Definition
To maintain objective reporting, this tracker utilizes the Working Definition of Antisemitism as adopted by the International Holocaust Remembrance Alliance (IHRA):
“Antisemitism is a certain perception of Jews, which may be expressed as hatred toward Jews. Rhetorical and physical manifestations of antisemitism are directed toward Jewish or non-Jewish individuals and/or their property, toward Jewish community institutions and religious facilities.”
We apply this standard to distinguish between legitimate political expression and antisemitic manifestations in all documented reports.
02 · Editorial Standards
What Counts as an Incident
Every article that reaches this platform passes through a multi-stage verification pipeline. These are the standards that govern which events are documented — and which are not.
An incident must satisfy all three conditions
- A specific harmful act occurred:Assault, vandalism, a credible threat, discriminatory expulsion, property destruction, desecration of religious artifacts, or targeted hate mail. A harmful act must be identifiable — not merely alleged, implied, or reported as a general trend.
- The act was motivated by antisemitism:The act must be directed at Jewish people because of their Jewishness — not because of citizenship, politics, or affiliation with a state or organization. Hostility toward Israel as a nation does not automatically constitute antisemitism.
- The article is reporting the incident — not discussing it:Opinion pieces, editorials, commentaries, and academic analyses of antisemitism are not incidents. A news report about the history of antisemitism is not an incident. Only articles describing a specific, real-world event qualify.
Automatic exclusions
Political Protests
Pro-Palestinian demonstrations, marches, vigils, and rallies are not antisemitic incidents — unless they involved direct targeting of Jewish people with slurs, violence, or destruction of Jewish property.
Criticism of Israeli Policy
Statements by politicians, activists, or public figures about Israeli government action are not antisemitic incidents unless they contain explicit slurs or calls for violence against Jewish people as a people.
Conflict Reporting
Coverage of the Israel–Gaza war, ceasefire negotiations, or military activity is geopolitical news — not antisemitic incident documentation.
Reports, Studies & Statistics
Annual antisemitism reports, survey findings, and academic studies are excluded. This platform tracks real-world incidents, not meta-coverage of antisemitism as a phenomenon.
Editorials & Opinion
Op-eds, columns, book reviews, film reviews, and podcasts discussing antisemitism are not incidents. Commentary about hate is not the same as hate.
Commemorations & Memorials
Holocaust remembrance events, memorial services, and anniversary coverage honor history — they are not new incidents of hate and are excluded from incident counts.
Verification standard
When in doubt, we do not publish.
Articles are classified by an automated verification system. Only high-confidence classifications are published as verified incidents. Lower-confidence articles are held in a pending review queue for human editorial review before any change in status. Precision is prioritized over volume — a missed incident is preferable to a false one.
Human review: Automated classification is a first-pass filter, not a final verdict. Incidents queued for review are evaluated by the platform editor before any change in status. Data corrections can be requested at any time via the contact address below.
03 · Pipeline
Data Methodology
Accuracy is our highest priority. Every incident passes through a multi-stage pipeline:
- Automated Intelligence Pipeline:Our background engine continuously queries multiple news APIs every 15 minutes using an expanded dictionary of antisemitism-related search terms — covering explicit acts, institutional targets, dogwhistles, and reporting language.
- Source Vetting:Priority is given to verified news organizations (e.g., JTA, ADL, Times of Israel, local newspapers) and official law enforcement statements. Articles from unverified sources are flagged for manual review.
- Heuristic Verification:Incidents are marked as Verified only if they meet high-confidence criteria (arrests made, school board confirmation, or multiple independent reports). Others remain Pending Review until corroborated.
- Evidence Preservation:Source web pages are automatically downloaded and SHA-256 hashed through our Evidence Vault, creating immutable forensic snapshots. This ensures that even if articles are removed, the evidentiary record is preserved.
- Legal Cross-Reference:Tracked subjects are automatically linked to federal court dockets via the CourtListener/PACER system, connecting documented incidents to real legal proceedings and ensuring accountability extends to prosecution.
04 · Capabilities
Platform Capabilities
Real-Time News Aggregation
Automated scanning of GNews and NewsAPI every 15 minutes with 19+ search queries covering explicit antisemitic language, institutional targets, and coded dogwhistles.
Predictive Threat Heatmap
Geographic visualization scoring locations by recent incident momentum and severity, color-coded to identify emerging hotspots.
Link Analysis Network
Interactive force-directed graph mapping connections between subjects, incidents, and geographic locations — revealing patterns not visible in linear data.
Federal Court Integration
Subjects are automatically linked to federal court dockets via CourtListener/PACER, connecting documented incidents to real legal proceedings.
Evidence Vault
Automated SHA-256 hashing and archival of source web pages, creating tamper-proof forensic snapshots that preserve evidence even if original content is deleted.
NIBRS-Compliant Dossiers
Printable intelligence briefs for any incident following National Incident-Based Reporting System standards — including chain of custody and evidence hashes.
05 · Open API
Open Data & API Access
All data is freely available for researchers, journalists, and developers. No authentication required.
Email Alert Subscription
Subscribe to incident alerts filtered by location and frequency.
Bulk Data Export
Download the full database
For research, analysis, or journalism.
Reference
Public API
Base URL: https://antisemitic-incidents-tracker.onrender.com
/api/incidentsReturns all documented incidents. Each object includes: id, title, description, date, location, category, source, url, status, evidence_hash. No authentication required.
/api/statsReturns aggregate statistics: total count, status breakdown (verified/pending), category distribution, and top locations.
/api/briefReturns an AI-synthesized brief summarizing recent activity, trends, and patterns. Optional: ?days=7
/api/subscribeSubscribe to email alerts. Body: { "email": "...", "location": "...", "frequency": "daily|weekly" }. Returns confirmation.
Contact
Direct Inquiries & Corrections
For media inquiries or data corrections on this tracker:
antisemiticincidentstracker@gmail.com