Skip to content

FTC press releases log (daily)

Commercial use OKAging
Query in workbench

Follow this dataset

Get a notice in your feed when a new snapshot is published. Optionally, we also POST it to your webhook.

Must be a public https address. We never follow redirects.

The full snapshot isn't published yet — check back after the next refresh.Download sample CSVDownload sample JSONSample rows only (up to 20) — not the complete dataset.

Daily log of U.S. Federal Trade Commission press releases observed in the Commission's official RSS feeds (keyless): one row per distinct release with headline, canonical URL, feed publication date, and a section from topic-feed membership (competition, consumer-protection, other). Method: the main feed plus the Bureau of Competition and Bureau of Consumer Protection topic feeds are polled and unioned by feed guid; the frame is deterministic per feed state, so an unchanged feed mints no new snapshot. Units: one release per row; pub_date is an ISO date; country_code is the USA join key. Covers enforcement actions, rulemakings (e.g. subscription click-to-cancel, fake reviews, junk fees), merger challenges, and consumer-refund distributions — the regulatory event stream for online-shop and subscription businesses. Complements the other publisher press-release logs (SEC, FDIC, OCC, BEA, Bank of Canada, StatCan). No summary column: release descriptions carry FTC media-contact phones/emails that would trip the hub PII gate; the canonical link reaches the full release. Caveats: the feeds surface a rolling window (61 distinct releases over 2026-04-17 → 2026-09-28 at build time), not a complete archive. License: U.S. federal public domain (17 U.S.C. 105). commercial_use=yes; attribution Federal Trade Commission.

Rows
60
Columns
8
Source cadence
Daily
Last refreshed
Oct 3, 2026
Theme
news

Use your own AI key

Once today's free allowance is used up, AI features can run on your own provider account.

Kept in this browser tab only (cleared when you close it) and sent with each AI request. Our servers use it for that request and never store or log it.