Every number on this site is imperfect in a specific, knowable way. This page is the ledger of those imperfections.
Public Filings republishes primary government records — nothing else. Below, per module: sources and their license conditions, coverage measured against the full corpus, known gaps, and the structural caveats that no amount of engineering removes. Everything here is regenerated fromstats.json on every build and is byte-verifiable against the published snapshot.
M1 — Congressional trading
Standing caveat: trades are disclosed in statutory dollar ranges, never exact amounts, and may be filed up to 45 days after the trade — sometimes later. A filing is a disclosure event, not a market event.
Sources & conditions
Known gaps — published, not hidden
Whose trade is it — owner codes
M2 — Institutional 13F
Standing caveat: 13F covers long positions in Section 13(f) securities — no shorts, no cash — as quarter-end snapshots filed up to 45 days late, in era-dependent value units. Only managers over $100M file: it is not a census.
What our 13F derivations do — and refuse to do
M3 — Company financials PLANNED
As-reported XBRL from EDGAR, for a curated universe. Standing caveat, committed now: as-reported ≠ normalized comparables — restatements and taxonomy drift will be shown as vintages, not silently overwritten. This section fills in when the module ships; its gates are published before its data.
M4 — Macro PLANNED
Treasury curve, CPI, employment, COT positioning from agency sources. Standing caveat, committed now: series are revised— each print carries vintage semantics per series, and BLS-derived responses carry the BLS-required citation and disclaimer verbatim.
Principles — what this site is for
The people's financial data, returned to the people. US financial-disclosure data — congressional trades, institutional holdings — pulled only from primary government sources, republished with its receipts. Others sell this free layer back at $30–200/month; here the public record itself is free forever. Convenience layers (alerts, integrations) may someday be paid — the data never will be.
The differentiator isn't coverage — anyone can scrape these filings. It's that every number here tells you exactly how stale it is, what it excludes, and how it was derived.
The published dataset. Every row remains in the published dataset: the congressional feed is served in full as byte-bounded per-year parts, listed with a direct download for each at congress/data, the institutional aggregate as paged files, and the signals as signals.v1.json. A table that shows fewer rows than it holds says so; nothing is withheld from the data.
What happens to a signal that stops matching. Signals are recomputed from scratch on every build over a fixed recent window. A signal keeps the same id and its original first-seen date for as long as it keeps matching. When one stops — the filing was amended, or it fell out of the window — it is kept in signals.v1.json rather than deleted, so a reader comparing two builds sees a departure instead of a silent gap. In the file those entries carry status of superseded and name the build they left in; the page counts them separately and never mixes them into a current total.
Ranges. Congressional amounts are disclosed as statutory ranges, never exact figures; totals over ranges are computed by interval arithmetic — a net range is the purchases interval minus the sales interval, and an open-ended bound propagates as open-ended. "At least $X" is the low end of the disclosed range.
How 13F data is read. Quarter-end positions are disclosed up to 45 days later; they are never current holdings and never a complete portfolio (cash, shorts and non-13(f) assets are absent). Changes are classified from comparable reported positions by share count; a missing position is not proof of a sale, and a value change alone is not a position change.
What counts as one position. A position is one issuer security × put/call × unit as the filer reported it; the producer classifies each change (new · add · trim · exit · no change) from the share delta between consecutive quarters, at that level.
Ticker mapping. A 13F row shows a ticker only where a reviewed, name-and-class keyed mapping row supplies one — verified against the SEC company list on the date the row states. Symbols are never inferred automatically; an unmapped security shows "Ticker not yet mapped".
CUSIP identifiers in disclosure text. Where a filer wrote a CUSIP into the text of a disclosure for a security that already has a reviewed ticker on this site, the published copy replaces that identifier with [CUSIP withheld] and keeps every other word. The marker is deliberately visible: a reader can always tell the published sentence differs from the filing, and the receipt link on the row still opens the unaltered source document. Nothing is withheld from the internal record, and no row is dropped. No disclosure in this build carries the marker.
Site weight. Every page and data file is byte-bounded: no served file exceeds the 1 MiB client-response ceiling for paged data, and the whole site stays under the hosting file-count and per-file caps. A table whose complete set is larger than a page states how many rows it shows and links the full published file.
Publication & verification
Privacy — the reader is not the product
Public Filings measures page traffic with Cloudflare Web Analytics, and nothing else. It sets no cookie, writes no storage key, and builds no fingerprint or cross-site identifier, and no account is required for anything on this site. What the beacon records is the page URL without its query string, the referrer, a coarse user-agent, a viewport bucket, load timing, and a country derived at the server from the connection. Cloudflare retains unsampled beacon data for 7 days, then aggregates it to roughly 10%; the previous six months remain accessible (Cloudflare Web Analytics FAQ, retrieved 2026-08-15). Free-text search never leaves your device — searches resolve to page paths client-side against an index that ships with the build. Watchlists live in your browser's localStorage and are never transmitted. If Public Filings ever offers paid conveniences (notifications, integrations), the records themselves stay free and ungated — a transparency site that paywalled the public record would contradict this page.
Required notices
Prohibited uses. Use of congressional financial-disclosure reports for commercial purposes, for determining credit, or for solicitation is restricted by 5 U.S.C. § 13107(c). Not financial advice. Public Filings reports disclosures; it recommends nothing. Attribution.Data remain U.S. government records; per-source conditions are recorded in the machine-readable conditions register and rendered inDATA-LICENSE ↗ andNOTICE ↗.