Data broker and bulk data transfer rules: outlook to 2027

The Justice Department's bulk data rule governs who abroad may reach Americans' sensitive data, PADFA bars brokers from selling it to foreign adversaries, and California's DROP, Texas, Oregon and Vermont set the rules for brokers at home.

Three laws, three different questions about a data flow

A bank, health system or public agency that shares personal data now answers to three kinds of rule, and each asks something different. The Justice Department's Data Security Program asks who on the other side could gain access: since April 8, 2025 it has barred U.S. persons from selling or licensing bulk sensitive personal data or government-related data to six countries of concern and their covered persons, and allowed vendor, employment and investment arrangements that give such access only under security requirements set by CISA [1] [2]. The Protecting Americans' Data from Foreign Adversaries Act (PADFA) asks whether a data broker is making sensitive data available to a foreign adversary country or an entity it controls [7]. State data broker laws in California, Texas, Oregon and Vermont ask whether an organization is a data broker at all, and if so require registration and, in California, deletion on request through a state platform [9] [14] [18] [19].

The Data Security Program reaches the institutions themselves, because it regulates activities rather than types of entity [4]. PADFA and the state laws mostly reach them through the brokers and vendors they buy from and sell to, since each defines a data broker by the absence of a direct relationship with the person or by the sale of data the business did not collect from that person [7] [9] [18] [20]. Statuses below are as checked on November 16, 2026.

The Justice Department rule: export controls on data, now in force

The final rule was published on January 8, 2025 at 90 FR 1636 and took effect on April 8, 2025 [2]. Its countries of concern are China (including Hong Kong and Macau), Cuba, Iran, North Korea, Russia and Venezuela [1] [4]. Covered persons include foreign entities organized or headquartered in those countries, foreign entities 50 percent or more owned by them or by other covered persons, and foreign individuals who are primarily resident there or who work for a country of concern or a covered entity; the Department can also designate any person, including a U.S. person [1] [4].

The rule counts data in bulk once it passes a threshold at any point in the preceding 12 months: more than 100 U.S. persons for human genomic data, more than 1,000 for other human 'omic data and biometric identifiers, more than 1,000 U.S. devices for precise geolocation data, more than 10,000 U.S. persons for personal health data or personal financial data, and more than 100,000 for covered personal identifiers [1]. Data counts whether or not it is anonymized, pseudonymized, de-identified or encrypted [1] [4]. Government-related data is covered at any volume: precise geolocation data for listed government sites, and sensitive personal data a party markets as linked to current or recent former federal employees, contractors or senior officials [1].

Two kinds of transaction are prohibited outright: data brokerage with a country of concern or covered person, and any covered data transaction that gives them access to bulk human 'omic data or the biospecimens it can be derived from [1] [4]. Data brokerage with any other foreign person is allowed only if the contract bars resale to a country of concern or covered person and the U.S. party reports known or suspected breaches of that clause within 14 days [1]. Vendor, employment and investment agreements that give a covered person access are restricted transactions, permitted only with the CISA security requirements in place; a vendor agreement expressly includes cloud computing [1].

The affirmative duties followed on October 6, 2025: a data compliance program and a yearly independent audit for anyone engaging in restricted transactions, reports within 14 days of rejecting a prohibited data brokerage offer, and an annual report by March 1 from U.S. persons in cloud-computing restricted transactions that are 25 percent or more owned by a country of concern or covered person [1] [5]. The Division's program page, in its description of the final rule, gives October 5, 2025 for the same duties (subpart J, § 202.1103 and § 202.1104), while the rule text, the FAQs and the enforcement policy say October 6 [3] [4] [5]. Records of each transaction must be kept for at least 10 years [4].

Civil penalties under IEEPA can reach the greater of $368,136 or twice the value of the transaction, and willful violations carry fines of up to $1,000,000 and prison terms of up to 20 years [1] [5]. The Division did not prioritize civil enforcement against good-faith violators from April 8 through July 8, 2025, and said that after that period it expected full compliance [5]. It applies a presumption of denial to license applications, and since September 2025 its FAQs point whistleblowers to FinCEN's award program for enforcement actions with penalties over $1,000,000 [4]. The program page, updated October 8, 2026, lists guidance, the rule and its correcting amendment, and no enforcement actions, licenses or advisory opinions [3]. A Federal Register search shows no amendment to part 202 after the correcting amendment of April 18, 2025, and a search for the Covered Persons List returns only the proposed and final rules [6] [23].

Moraph's view

Moraph's view: for banks and health systems the rule's weight falls on vendor, staffing and ownership arrangements more than on data sales. Few regulated institutions sell data to buyers in China or Russia; many rely on offshore support teams, analytics firms and cloud or software vendors whose ownership or staff could make them covered persons. Because the exemptions are tied to activities, and de-identification does not take data out of scope, the working control is an inventory of every arrangement that gives a foreign party access to data, tagged by country, ownership and data category, and refreshed when ownership changes.

What the exemptions cover for banks, hospitals and agencies

Financial institutions are not exempt as institutions. The exemption covers data transactions to the extent they are ordinarily incident to and part of financial services, including banking, payments and funds transfers, and activities permitted to national banks and bank holding companies [1]. The Justice Department's FAQs say a vendor agreement such as a cloud contract, or an employment agreement such as a board seat, that gives a covered person access to bulk data is not ordinarily incident to financial services for an institution's wholly domestic operations, and that transactions required or authorized by federal law, such as Bank Secrecy Act reporting, may be exempt on that separate ground [4]. The rule does not generally bar opening or keeping an account for a covered person [4]. Personal financial data includes card, account, statement and credit report data whoever holds it, so the term is not limited to data held by financial institutions [4].

Health data is covered regardless of who collects it. The FAQs contrast the rule's personal health data, which includes data such as exercise logs from fitness apps, with HIPAA's health information, which is defined by the type of entity that holds it [4]. There is no HIPAA exemption; the health-related exemptions cover data needed to obtain or keep FDA authorizations and data incident to FDA-regulated clinical investigations and post-market surveillance, de-identified or pseudonymized to the standard of 21 CFR 314.80 where the exemption requires it [1]. Research funded under a federal grant or contract is exempt to the extent the grant directs or authorizes the transaction, while research without federal funding gets no general exemption and may need a specific license if it involves a commercial transaction [1] [4].

For government, the exemption covers the official business of the United States Government, its employees, grantees and contractors [1]. The exemptions listed in the rule do not name state or local governments [1] [4]. Purely domestic transfers between U.S. persons are generally outside the rule, unless a U.S. person has been designated a covered person [4].

PADFA: a narrower ban, and FTC warning letters

PADFA made it unlawful, from 60 days after its enactment on April 24, 2024, for a data broker to sell, license, transfer or otherwise make available personally identifiable sensitive data of a U.S. individual to a foreign adversary country or an entity controlled by one [7]. Control includes an entity in which persons from those countries hold at least a 20 percent stake [7]. Sensitive data covers government identifiers, health information, financial account numbers and income or balance information, biometric, genetic and precise geolocation data, private communications, data on individuals under 17, and status as a member of the Armed Forces, among other categories [7].

The statute defines a data broker as an entity that, for valuable consideration, makes available data it did not collect directly from the individual to another entity that is not acting as a service provider; its exclusions include service providers, entities whose product or service is not the sensitive data itself, and transfers made at the individual's request or direction [7]. The Justice Department's comparison notes that PADFA covers four countries (China, Iran, North Korea and Russia) against the rule's six, includes an exception for transfers at the individual's request that the rule lacks, and is enforced case by case by the FTC [4]. Violations are treated as violations of an FTC trade regulation rule [7]. On February 9, 2026 the FTC sent warning letters to 13 data brokers, said some offered data on individuals' military status, and noted civil penalties of up to $53,088 per violation [8].

Moraph's view

Moraph's view: few banks, hospitals or agencies will be PADFA data brokers, because most of their data comes directly from customers, patients or residents. The statute matters to them as a test for suppliers: a marketing, analytics or identity-data vendor that is a data broker under PADFA and has a foreign adversary-linked owner or customer is a vendor whose data supply could be cut off by an FTC case. Contract terms that ask a broker to warrant PADFA and Data Security Program compliance are a modest step with a clear purpose.

California's Delete Act and DROP: one request, every registered broker

California defines a data broker as a business that knowingly collects and sells to third parties the personal information of consumers with whom it has no direct relationship, and excludes entities to the extent they are covered by the Fair Credit Reporting Act, the Gramm-Leach-Bliley Act or the state's insurance privacy law, and HIPAA covered entities and business associates to the extent their processing is exempt under the CCPA [9]. Brokers must register by January 31 after each year in which they meet the definition [9]. Since January 1, 2026 the registration statement must say whether the broker sold or shared data in the past year with a foreign actor, the federal government, other state governments, law enforcement (outside a subpoena or court order) or a developer of a generative AI system, and whether and how far it is regulated by FCRA, GLBA or HIPAA [9].

The Delete Request and Opt-out Platform (DROP) has taken consumer requests since January 1, 2026 and sends one request to over 600 registered data brokers [10]. From August 1, 2026 each broker must check DROP at least once every 45 days, delete the data within 45 days, treat a request it cannot verify as an opt-out of sale or sharing, pass the request to its service providers and contractors, keep deleting every 45 days and stop selling or sharing new data about that consumer [9]. Data exempt from deletion under the CCPA's exemptions, including those for GLBA and HIPAA data, may be kept but used only for the exempt purpose [9]. Independent audits of DROP compliance start January 1, 2028 and repeat every three years [9].

Fines are $200 a day for failing to register and $200 per deletion request for each day a broker fails to delete [9]. In Board decisions announced on January 8, 2026, after settlements reached by CalPrivacy's Data Broker Enforcement Strike Force, Rickenbacher Data LLC (doing business as Datamasters) was ordered to pay $45,000 and S&P Global, Inc. $62,600 for failing to register as data brokers [11]. On August 10, 2026 the Board ordered LocateSmarter to pay $116,490 for registering late and requiring partial Social Security numbers before consumers could opt out, and on August 13 CalPrivacy announced a $52,400 fine against Cybba for failing to register [12] [13]. The agency says it has brought more than a dozen actions against unregistered data brokers [13].

Texas, Oregon and Vermont: registries with different reach

Texas has required data brokers to register with the Secretary of State and pay a $300 fee since its 2023 law, which applies to data collected or transferred from December 1, 2023 [14]. The law exempts governmental entities, consumer reporting activity regulated by FCRA, and financial institutions subject to Title V of GLBA; its exemption list does not name HIPAA covered entities [14]. Two 2025 amendments took effect on September 1, 2025: S.B. 2121 dropped from the definition the requirement that brokering be the principal source of revenue, leaving as the test whether, in a 12-month period, a broker derives more than 50 percent of its revenue directly from data it did not collect directly or revenue directly from such data on more than 50,000 individuals [15], and S.B. 1343 added a website notice and a registration link telling consumers how to use their Texas privacy rights [16]. Penalties start at $100 a day plus unpaid fees and are capped at $10,000 per broker in a 12-month period [14]. The Secretary of State now cites the law as chapter 510 of the Business and Commerce Code and says it is the filing officer only, without authority to regulate brokers' business practices, investigate alleged violations or enforce the law [17].

Oregon requires registration with the Department of Consumer and Business Services under ORS 646A.593 [18]. It excludes FCRA-regulated activity, GLBA-regulated activity of financial institutions and their affiliates, and businesses collecting data about their own customers, employees, investors or donors, along with their service providers; the state and local governments are not business entities under the section [18]. Penalties are up to $500 per violation or per day, capped at $10,000 a year [18].

Vermont's current law requires registration by January 31 with a $100 fee and penalties of $50 a day up to $10,000 a year [19]. Act 138 of 2026, signed June 16, 2026, rewrites it from January 1, 2027: registration within 30 days of becoming a data broker and every July 1, a $900 fee, a $20,000 bond, the same kinds of disclosures about sales to foreign actors, governments, law enforcement and AI developers as California, $200 a day for failing to register and $25,000 for materially incorrect information [19] [21] [9]. Vermont's current definition of a business includes financial institutions and excludes the State, State agencies and political subdivisions, and from 2027 a direct relationship requires the consumer to have intended to interact with the business [20]. The Act also orders the Secretary of State to study a California-style deletion mechanism, with an interim report due December 1, 2027 and a final report by December 1, 2028 [21].

Moraph's view

Moraph's view: the state laws will reach regulated institutions mostly through their counterparties. A bank's GLBA data or a hospital's HIPAA data is carved out to the extent of those laws, but the carve-outs are written around data and activities, not whole companies, so an affiliate selling marketing data or a health system's consumer app can still meet the definition. The more useful effect is transparency: California's public registry already shows which brokers sell to governments, law enforcement and AI developers, Vermont's will from 2027, and a buyer that checks those fields before signing learns something its contract may not tell it.

Who counts as a data broker, law by law

Data broker and bulk data rules: reach and carve-outs, as checked November 16, 2026
LawWhom it bindsBanks and financial dataHealth dataGovernment
Data Security ProgramAny U.S. person in a covered data transaction with a country of concern or covered person [1] [4]Exempt only where ordinarily incident to financial services [1] [4]Covered whoever holds it; FDA-related exemptions only [1] [4]Federal official business exempt [1]
PADFAData brokers selling to foreign adversary countries or entities they control [7]Financial account and balance data is sensitive data [7]Health information is sensitive data [7]Service providers to governments excluded [7]
California Delete ActBusinesses selling data of consumers they have no direct relationship with [9]Excluded to the extent covered by GLBA or FCRA [9]Excluded to the extent exempt under the CCPA's HIPAA provision [9]Registration discloses sales to governments [9]
TexasBrokers over the revenue or 50,000-person threshold [15]GLBA financial institutions exempt [14]No named HIPAA exemption [14]Governmental entities exempt [14]
OregonBusinesses selling or licensing brokered personal data [18]GLBA-regulated activity excluded [18]No named HIPAA exclusion; customer relationships excluded [18]State and local government excluded [18]
VermontBusinesses selling data of consumers they have no direct relationship with [20]Financial institutions included in "business" [20]Turns on whether the consumer has a direct relationship with the business [20]State, State agencies and political subdivisions excluded [20]

At the federal consumer-finance level, the CFPB withdrew its proposed Regulation V rule on data broker practices under the Fair Credit Reporting Act as of May 15, 2025, saying it would take no further action on it [22].

What to watch through 2028

  • A first public Data Security Program enforcement action, a published advisory opinion or general license, or a first designation to the Covered Persons List, none of which the program page showed as of its October 8, 2026 update [3] [23].
  • Whether the FTC turns its February 2026 warning letters into a PADFA complaint [8].
  • CalPrivacy's first cases about DROP processing rather than registration, now that the August 1, 2026 duties are in force [9] [13].
  • Vermont's new registration regime from January 1, 2027 and the Secretary of State's interim report on a deletion mechanism, due December 1, 2027 [19] [21].
  • California's first independent DROP audits, which begin January 1, 2028 [9].

Scope and method

We read the rule text in the eCFR, the Federal Register record, the Justice Department's program page, FAQs and enforcement policy, the United States Code, FTC and CalPrivacy releases, and the enacted text or official code for each state law on November 16, 2026, and took dates from those documents. The piece covers rules on selling or giving access to personal data to foreign adversaries and on data brokers; it leaves out consumer health data laws and comprehensive state privacy laws (covered in our health data privacy outlook), the CFPB's personal financial data rights rule (covered in our open banking outlook), and data broker laws in states other than California, Texas, Oregon and Vermont, which we did not check. This is a description of the laws, not legal advice on how they apply to a given organization.

What this means for you

  • Banks: List the arrangements that give a foreign party access to customer data (offshore support, cloud and analytics vendors, board and investor rights) and test each against the financial services exemption, which the Justice Department says does not cover a vendor or employment agreement giving a covered person access in wholly domestic operations [4]. Check affiliates that sell or license data outside GLBA-covered activity against the California, Texas and Oregon definitions [9] [14] [18].
  • Health systems: Count patient, app and research data toward the personal health data threshold of more than 10,000 people regardless of HIPAA status or de-identification [1] [4]. Review research collaborations without federal funding, which have no general exemption [4], and check consumer-facing apps and data partnerships against state broker definitions, since Texas names no HIPAA exemption [14].
  • Public agencies: Federal business is exempt from the Data Security Program, but the rule's exemptions do not name state or local governments [1] [4]. Agencies that buy brokered data can read California's public registry for each broker's sales to governments and law enforcement, and Vermont's from 2027 [9] [19].
  • Data and analytics vendors: Expect customers to ask for warranties on Data Security Program, PADFA and state registration compliance; a broker selling to a non-covered foreign buyer needs an anti-resale clause and a 14-day report on breaches of it [1], and California brokers must process DROP requests every 45 days [9].

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 60% Open

    The Justice Department does not publicly announce any civil penalty, settlement or criminal charge for a violation of 28 CFR part 202 on or before December 31, 2027.

    How we will check: Search the National Security Division's Data Security Program page and justice.gov press releases for an enforcement action citing 28 CFR part 202 or the Data Security Program; the call is right if none is announced by December 31, 2027.

    Basis: The program page, updated October 8, 2026, lists no enforcement actions [3]; the rule applies a knowledge standard rather than strict liability and the Division credits voluntary self-disclosure [4]; the limited enforcement period ended July 8, 2025 [5].

  2. P2 By Confidence 55% Open

    The FTC files or announces a complaint or settlement alleging a violation of the Protecting Americans' Data from Foreign Adversaries Act (15 U.S.C. 9901) on or before December 31, 2027.

    How we will check: Search ftc.gov press releases and cases for a complaint, proposed order or settlement that pleads a violation of 15 U.S.C. 9901; the call is right if one is filed or announced by December 31, 2027.

    Basis: The FTC sent warning letters to 13 data brokers on February 9, 2026, naming military status data and penalties of up to $53,088 per violation [8]; PADFA violations are treated as trade regulation rule violations [7].

  3. P3 By Confidence 70% Open

    CalPrivacy announces at least one enforcement action alleging that a data broker failed to meet its DROP deletion duties under Civil Code section 1798.99.86 on or before December 31, 2027.

    How we will check: Search CalPrivacy announcements and Board decisions on privacy.ca.gov and cppa.ca.gov for a decision or settlement citing section 1798.99.86; the call is right if one is announced by December 31, 2027.

    Basis: Brokers have had to process DROP requests every 45 days since August 1, 2026, with fines of $200 per request per day [9]; CalPrivacy says it has brought more than a dozen enforcement actions against unregistered data brokers, and its August 2026 Cybba decision already orders a broker to access DROP and process deletion requests through it [11] [13].

  4. P4 By Confidence 85% Open

    On December 31, 2027, 28 CFR 202.601 names the same six countries of concern as in November 2026: China, Cuba, Iran, North Korea, Russia and Venezuela.

    How we will check: Read 28 CFR 202.601 in the eCFR as of December 31, 2027 and compare the list with the six governments named here.

    Basis: The list has not changed since the rule took effect, and the only later Federal Register change to part 202 was the correcting amendment of April 18, 2025 [1] [6].

  5. P5 By Confidence 85% Open

    None of Texas, Oregon or Vermont operates a state-run platform that lets a consumer send one deletion request to all registered data brokers by December 31, 2027.

    How we will check: Check the Texas Secretary of State, Oregon Department of Consumer and Business Services and Vermont Secretary of State websites on December 31, 2027 for a live single-request deletion service for data brokers.

    Basis: Vermont's Act 138 orders only a study, with an interim report due December 1, 2027 [21]; the Texas and Oregon laws set registration, notice and penalty duties without a deletion platform [14] [16] [18].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • Data brokers
  • DOJ Data Security Program
  • 28 CFR part 202
  • PADFA
  • California Delete Act
  • DROP
  • Texas
  • Oregon
  • Vermont
  • Cross-border data