Enforcement Data
Structured enforcement actions from the FTC, HHS, and 19 state attorneys general. Each event includes the entity, fine amount, violation types, laws cited, remedies, and a link to the official source.What’s included
Every enforcement event contains:| Field | Type | Description |
|---|---|---|
title | string | Official title of the enforcement action |
event_date | date | When the action was announced |
jurisdiction | string | Enforcing authority (CA, FTC, NY, TX, HHS, etc.) |
event_type | string | settlement, consent_decree, fine, enforcement_action, investigation, etc. |
entity_name | string | Company or organization involved |
fine_amount | number or null | Monetary penalty (null for non-monetary actions) |
violation_types | string[] | Categories from a fixed taxonomy of 19 types |
risk_level | string | critical, high, medium, or low (based on fine amount and scope) |
summary | string | Plain-English summary of the action |
laws_cited | string[] | Statutes referenced (CCPA, FTC Act, COPPA, etc.) |
remedy_types | string[] | Required remedies (monetary_penalty, injunction, compliance_program, etc.) |
primary_source_url | string | Link to official government press release |
document_urls | string[] | Links to complaints, judgments, consent orders |
is_multistate | boolean | Whether multiple jurisdictions were involved |
co_enforcers | string[] | Other agencies involved in multistate actions |
Jurisdictions covered
21 federal and state authorities:| Level | Jurisdictions |
|---|---|
| Federal | FTC, HHS (HIPAA enforcement) |
| State | CA (OAG + CPPA), TX, NY, CT, CO, OR, NJ, VA, MN, GA, OH, IN, FL, IL, PA, MA, WA |
| City | NYC (DCWP) |
Violation types
19 categories organized by data subject:| Category | Types |
|---|---|
| Consumer data | opt_out_failure, notice_failure, consent_failure, dark_patterns, data_sharing_unauthorized, data_broker_noncompliance |
| Sensitive data | children_data, student_data, health_data, employee_data, biometric_data, geolocation_data |
| Security | data_breach, security_failure, breach_notification_delay |
| Other | record_retention, ai_automated_decisions, surveillance_pricing |
Risk levels
| Level | Criteria |
|---|---|
| Critical | Fine exceeds $10M or involves industry-wide injunction |
| High | Fine exceeds $1M |
| Medium | Fine between 1M |
| Low | Fine under $100K or no monetary penalty |
Access methods
Enforcement data is available through:- MCP Server: Use
search_enforcement_actions,get_enforcement_details, andget_enforcement_statstools. See MCP Integration. - Web Console: Browse and filter events at courtrules.app/enforcement.
Data quality
- Every event extracted from official government press releases
- Entity names normalized (company suffixes stripped for deduplication)
- Deduplication via content hash (entity + date + jurisdiction)
- Source quotes preserved for traceability
- Pipeline re-extracts when source pages are updated
Data freshness
The enforcement pipeline checks government press release pages on a regular schedule. New events typically appear within 24-48 hours of the official announcement. The pipeline covers:- FTC: RSS feed (near real-time)
- State AGs: HTML press release pages (daily checks)
- HHS OCR: Breach portal (daily checks)
date_from with search_enforcement_actions:
date_from filters.