RentGrow's $2.25M FTC Deal: Source Disclosure Is Not Optional

RentGrow's $2.25M FTC Deal: Source Disclosure Is Not Optional
July 25, 2026

What Changed: A $2.25 Million Tenant-Screening Settlement Landed This Month

On July 9, 2026, the FTC announced that RentGrow, Inc. will pay $2.25 million to settle allegations that it violated the Fair Credit Reporting Act and the FTC Act, according to the FTC press release. RentGrow is a Delaware corporation headquartered in Massachusetts that compiles background screening reports and sells them to landlords and property managers as tenant screening reports.

If you advise any company that scores, matches, or resells consumer data, this settlement is not background noise. It is a direct signal about which FCRA obligations the FTC will actually enforce.

The action to take this quarter is narrow and concrete. Confirm that your consumer reporting agency clients can name every source of data they use to match records to individuals — and that they disclose those sources to consumers on request. RentGrow could not, and it cost them $2.25 million.

The Undisclosed Source: LexisNexis Accurint Sat at the Center of the Complaint

The most instructive detail is not the dollar figure. It is the source-disclosure failure. The complaint alleged that RentGrow failed to disclose to consumers that LexisNexis Accurint was a source of historical address information and middle names that RentGrow used to match criminal and eviction records to consumers.

That matters because matching data drives the entire accuracy chain. If a company uses historical addresses and middle names to attach a criminal or eviction record to a person, and it does not tell the consumer where that matching data came from, the consumer cannot meaningfully dispute a false match.

FCRA Section 609 / 15 U.S.C. § 1681g requires a consumer reporting agency to disclose the sources of information in a consumer's file. Many teams read that as "disclose the record vendor" and stop there. The FTC read it to include the auxiliary matching sources — the address and name data that decides whose file a record lands in. That is a wider reading than most tenant-screening CRAs operationalize today.

Enforcement Signal-Reading: Four Theories, One Referral, a 2-0 Vote

The statutory stack the FTC assembled

The complaint, available as a PDF from the FTC, invokes three FCRA provisions plus the FTC Act:

  • FCRA Section 607(b) / 15 U.S.C. § 1681e(b) — reasonable procedures to assure maximum possible accuracy.
  • FCRA Section 611 / 15 U.S.C. § 1681i — dispute reinvestigation procedures.
  • FCRA Section 609 / 15 U.S.C. § 1681g — disclosure of sources to consumers.
  • Section 5(a) of the FTC Act — the unfair-or-deceptive practices hook.

How the case reached court

The complaint was filed by the Department of Justice upon referral from the FTC in the U.S. District Court for the District of Columbia. The civil action number is 1:26-cv-02415 and the FTC matter number is 222-3002, per the FTC case page. The Commission vote to authorize the referral and approve the stipulated order was 2-0.

One caution for counsel. As of the July 9, 2026 announcement, the proposed stipulated order was pending approval by the District Court. It does not carry the force of law until a District Court judge signs it. Do not describe it as final in a client memo yet.

This Is a Pattern, Not a One-Off: Read It Against the 2023 TransUnion Settlement

The RentGrow action does not stand alone. In October 2023, the FTC and CFPB jointly settled with TransUnion Rental Screening Solutions, Inc. and Trans Union LLC for $15 million over FCRA accuracy failures in tenant screening reports, described at the time as the largest amount ever recovered in an FTC tenant-screening matter. You can review that action in the 2023 FTC release.

Read through a consumer protection lens, the throughline is consistent. The FTC is targeting the accuracy of the match — not merely the accuracy of the underlying court record. A criminal record can be entirely accurate about the person it describes and still be a false result when attached to the wrong applicant.

That is the regulatory reality check. Telling a regulator "the source data was correct" will not fly when the harm is a mismatched record that cost a family a lease. The FTC cares about the procedure that connects a record to a human being.

Action Items for CRA and Data-Broker Counsel This Quarter

Work these in order. Do not draft notices before you finish the inventory.

  1. Map every matching source. Identify each vendor and dataset used to attach records to individuals — including auxiliary sources such as historical addresses and middle names. LexisNexis Accurint was the named source in RentGrow; assume your equivalent is in scope.
  2. Audit your Section 609 disclosures. Confirm that consumer file disclosures name the sources of matching data, not just the record vendor. This is where RentGrow fell short.
  3. Stress-test your reasonable procedures under 1681e(b). Document the logic that connects a record to an applicant, and record the false-match rate you can tolerate before a report goes out.
  4. Review dispute reinvestigation under 1681i. Ensure the reinvestigation actually re-runs the match, and that post-dispute notices to consumers and to landlords say the same thing.
  5. Preserve your audit trail. Regulators expect data maps, retention schedules, and source logs on day one of an inquiry — not after.

Each step maps to a specific count in the complaint. That is the point. The FTC laid out its theory statute by statute; your control matrix should answer it the same way.

Key Takeaways and Where to Get Help

  • Source disclosure is a live enforcement risk. The FTC read FCRA Section 609 to cover the matching data — historical addresses and middle names from LexisNexis Accurint — not just the record vendor.
  • The number is $2.25 million and the date is July 9, 2026. The proposed order remains pending District Court approval, so it is not yet final.
  • This is a pattern. The 2023 TransUnion tenant-screening settlement of $15 million and the RentGrow action share one theory: the accuracy of the match matters as much as the accuracy of the record.
  • The complaint is a roadmap. Sections 1681e(b), 1681i, and 1681g plus FTC Act Section 5(a) tell you exactly what to audit.
  • Inventory first. You cannot disclose or govern sources you have not mapped.

Rikka Law helps consumer reporting agencies, data brokers, and adtech companies operationalize FCRA and privacy compliance — from source-disclosure audits to dispute-process design and regulator-ready data maps. If you resell or match consumer data, we will pressure-test your procedures against the theories the FTC actually brings.

Start a conversation at fintechlaw.ai/contact, or learn more about our work at fintechlaw.ai.

This post is for general informational purposes only and does not constitute legal advice. No attorney-client relationship is formed by reading or acting on this content. Consult qualified counsel about your specific facts.