Figures from Who Gets Your Data, a MORVS pilot register built from FTC complaints and orders, Federal Register notices, a Supreme Court opinion, a Sacramento court order, FinCEN's Year in Review and one Geographic Targeting Order, and the California data broker registry as MORVS's Data Broker Register republishes it, table by table and never added across tables: handoff edges and primary documents, counts by legal status with the register's labels, named and class-only recipients, rows with a settlement or a current status, and the review queue's counts (a candidate is never an edge until reviewed); the brokers' California registry answers, with each sharing question as the form words it, the registrations and distinct brokers answering yes, and the government or law-enforcement overlap; FinCEN's fiscal-year Bank Secrecy Act figures with their wording, page and unit, and the Geographic Targeting Order's dates, ZIP count by county group and quoted terms; the register's headlines with their basis, legal status and sources; what is not covered (documents left for manual download, hosts never fetched, the incumbents credited and the register's stated gap), with the stop rules; and, kept separate, the "Bought by the government" lane (obligations by fiscal year with the floor year flagged, by capability with basis, bundles, the top buyers, the people, location and plate-data group, awards pending review, the lane's headlines with their basis, and the mixed, unclassified, context, excluded and dropped amounts kept apart) and the benefits and identity panel with its own headline. FinCEN's figures count searches, reports and filers, never people, and carry the register's count note. Broker rows are each business's own answer to the California registry, with the question as the form words it, and carry the broker note: no broker is accused of anything. Each handoff carries its primary document's own legal status with the register's label exactly as published (a court's finding, an allegation in a complaint, a settlement with or without an admission, an order's terms, or a count of requests): an allegation is not a finding, a request is not a disclosure, and old conduct is not current practice. The three tables (handoffs, broker registry answers, legal duties) hold different kinds of evidence and are never added together, scored or ranked; no answer gives a total across them. The lane is a separate table: never added to the benefits and identity panel, the context (Palantir, Dataminr Defense Department licences), the excluded amounts or the handoff, broker and legal-duty tables. Amounts are obligations net of de-obligations, never outlays: an outlay appears only where the award record gives one, labelled as the outlay for the whole award. A contract is not proof of use on any person. Capability comes from the award's own words or a single-product vendor's product line, each with its basis (transaction_words, award_base_words, vendor_product or review); a bundle naming two capabilities sits in the lane total and in no capability total. The floor year (FY2026 at launch) is a floor, as Defense Department actions reach FPDS late, and each figure for it is flagged. A reviewed universe, not a complete inventory. A pilot: a small, hand-checked set of documented handoffs, the brokers' own registry answers and one legal-duty exhibit, in three separate tables; it is not a census of data sharing. The answer carries the pilot note, lane note, coverage line, as-of date, file dates, legal-status labels, the register's rules, its licence and the source page on morvs.ai. Organisations, companies, agencies and governments only: no individual is named, and there is no bank or personal-report lookup.