New Jersey Just Turned Algorithmic Rent Coordination Into an Antitrust Case
Governor Mikie Sherrill signed the Forbidding the Algorithmic Inflation of Rent (FAIR) Act on July 20, 2026, making New Jersey the fourth state to expressly regulate algorithmic rent-setting practices (Governor's Office, July 20). Effective July 1, 2027, the law prohibits specified use of algorithmic systems to coordinate residential-rental prices, lease terms, and occupancy practices through nonpublic, competitively sensitive information. It doesn't ban every pricing algorithm. It treats a defined set of coordinated practices as violations of New Jersey's existing Antitrust Act.
That last detail is the one worth reading twice. New Jersey didn't write a new AI statute to address this. It reached for antitrust law that already existed and pointed it at a specific way algorithmic systems can be used. Attorney General Jennifer Davenport described the target as landlords and "tech companies" that "conspire to artificially inflate rents." Sherrill was more direct: landlords "should be competing to provide the best price to renters" instead of coordinating through a shared algorithm. "That stops now."
If your organization filed this under "a housing problem" and moved on, that's the read worth reconsidering. The FAIR Act doesn't create a universal rule for every staffing, allocation, or dynamic-pricing tool in every industry, and this newsletter isn't claiming it does. What it offers instead is a governance warning that travels well beyond residential real estate: when a system pools or references competitors' nonpublic, competitively sensitive data to shape pricing or allocation decisions, "the software decided" stops being an adequate answer to a regulator, whether the enforcement mechanism is a new AI statute or, as in New Jersey's case, an antitrust law that was already on the books.
That's also the throughline connecting this to the other governance story running in parallel right now, the unresolved fight over whether the FTC can preempt state AI rules on output steering. Different mechanism, same underlying exposure: regulators reaching for whatever legal tool already fits, rather than waiting for a purpose-built AI statute to catch up. An organization with no documented answer to "what data does this system use, and where did it come from" is exposed either way, regardless of which law ends up applying to it.
This month's action: ask your revenue-management, staffing, or dynamic-pricing vendor one direct question in writing: does this tool pool, receive, or reference competitors' nonpublic data to generate its recommendations? Ask what data sources it actually uses, whether it has guardrails against coordination, and how those controls are documented. The legal exposure will vary by industry and jurisdiction, and this isn't legal advice for your specific situation. The governance question, what data is going into the system and who else's data that might include, shouldn't wait for a state to answer it for you.