Skip to main content
The enforcement data holds privacy enforcement events from federal and state regulators, such as settlements, fines, consent decrees and investigations. Each event names the company and the violation types, lists the laws cited and the remedies, gives the fine amount when one was announced, and links to the official source.

Why teams use enforcement data

In-house legal teams need to know when regulators take action in their industry. An event against a competitor or a vendor can lead to a contract review, a policy update or a report to the board. Each event is a structured, searchable record with a link to its press release, so it can feed your legal workflows directly. Common uses:
  • Watch the enforcement events that affect your industry.
  • Scan vendor contracts when a new type of violation appears, using the search_terms of an event.
  • Create a matter in your legal workspace when a high-risk event appears.
  • Track enforcement by jurisdiction or violation type for compliance reports.

What an event contains

Call search_privacy_enforcement_actions with filters to find the events you need:
The response is shortened here:
See MCP: enforcement data for the full search_privacy_enforcement_actions reference.

Jurisdictions

The data covers the FTC and state regulators. To list the jurisdictions available today, call get_privacy_enforcement_stats with group_by set to jurisdiction. Use the codes it returns in the jurisdiction filter.

Violation types

Each event carries one or more violation types, in four groups:

Risk levels

Each event has a risk level, which depends on the fine and the remedies:

Access methods

You can reach the enforcement data in two ways.
  1. The MCP server has three tools, search_privacy_enforcement_actions, get_privacy_enforcement_action and get_privacy_enforcement_stats. See MCP: enforcement data.
  2. The web console lets you browse and filter events at courtrules.app/enforcement.

Data freshness

The enforcement data is updated daily, and a new event appears after the next daily check. To get only the events since your last check, call search_privacy_enforcement_actions with date_from. One call a day is enough:
The API has no webhooks, so poll with date_from to find new events.