Compliance teams are working to understand the impact of algorithmic pricing on their antitrust programs. The Justice Department's consent decree with Pinnacle Property Management Services has raised important questions about data sharing, third-party software, and automated decision-making. However, much of the concern stems from misunderstandings about where the legal boundaries lie.
These misconceptions persist because the technology feels new and the guidance seems unclear. Your legal team might not fully grasp how the pricing software operates. Your IT team might not be familiar with the Sherman Act. And the vendors selling you "AI-powered competitive intelligence" likely aren't emphasizing the antitrust risks in their presentations.
Let's clarify what the Pinnacle case actually teaches us about algorithmic coordination and what your compliance program needs to address.
Myth 1: "Using pricing algorithms is inherently illegal"
Reality: Algorithms are tools. The violation occurs when you use them to coordinate with competitors.
The proposed consent decree doesn't prohibit Pinnacle from using pricing software. It prohibits using algorithms that generate recommendations based on competitors' sensitive data or that incorporate anticompetitive features designed to align pricing across landlords.
You can use data analytics to optimize your own pricing based on your costs, occupancy rates, and publicly available market information. You cross the line when you feed your competitors' non-public pricing data into a shared algorithm and then follow its recommendations to raise rents in lockstep.
The distinction matters for your training content. Employees need to understand that the problem isn't automation. It's using automation as a vehicle for coordination that would be illegal if done in a conference room.
Myth 2: "If a third-party vendor handles the data, we're insulated from liability"
Reality: You own the antitrust risk, even when a vendor operates the platform.
The complaint against Pinnacle and other landlords makes clear that outsourcing coordination to RealPage didn't create a legal shield. The landlords actively participated in the scheme by sharing their competitively sensitive information, accepting pricing recommendations generated from competitors' data, and conferring on pricing strategies at vendor-hosted meetings.
Your compliance program can't treat vendor relationships as black boxes. When you contract with a third-party service that involves data sharing with competitors, you need due diligence on:
- What data the vendor collects from you and your competitors
- How that data is aggregated, anonymized, or kept separate
- Whether the vendor's algorithm incorporates features that effectively coordinate pricing
- What forums or meetings the vendor hosts that could facilitate improper information exchange
The proposed decree requires Pinnacle to accept a court-appointed monitor if it uses any third-party pricing algorithm that isn't certified as compliant. That's a strong signal that "the vendor did it" won't fly as a defense.
Myth 3: "Antitrust only matters for pricing decisions"
Reality: Competitively sensitive information sharing is the core violation, regardless of the business function.
The Pinnacle case focuses on rental pricing, but the principle extends to any area where competitors share non-public strategic data. The decree prohibits Pinnacle from sharing competitively sensitive information with competitors, full stop.
That includes capacity plans, cost structures, customer terms, expansion strategies, and salary benchmarks. If your procurement team, HR team, or operations team is participating in industry working groups or data-sharing consortiums, you need guardrails.
Your compliance training should help employees recognize what makes information "competitively sensitive." It's not just current prices. It's future pricing intentions, cost data that reveals pricing strategy, customer-specific terms, and supply or capacity plans that signal how you'll compete in the market.
Myth 4: "Industry benchmarking is always safe if the data is aggregated"
Reality: Aggregation doesn't sanitize coordination. The design of the data exchange matters.
Many legitimate benchmarking services exist. They collect data from multiple companies, aggregate it to prevent identification of individual participants, and report historical trends. But the Pinnacle case shows that calling something "benchmarking" doesn't make it legal.
The complaint describes landlords using RealPage's algorithms that incorporated competitors' data to generate forward-looking pricing recommendations, not backward-looking trend reports. The landlords also allegedly conferred directly on pricing strategies and algorithm parameters.
Safe benchmarking typically involves:
- Historical data, not real-time or forward-looking data
- Aggregation that prevents reverse-engineering individual competitors' information
- No mechanism for competitors to signal future pricing intentions
- No direct communication among competitors about how they'll use the data
If your team participates in benchmarking, your antitrust training should cover these boundaries. Employees need to know when to stop a conversation that's drifting from "here's what the market did last quarter" to "here's what we're planning to charge next month."
Myth 5: "We're only liable if we explicitly agree to fix prices"
Reality: The Sherman Act reaches coordinated conduct, not just explicit cartels.
You don't need a signed agreement or a smoke-filled room. The enforcement action against Pinnacle and other landlords describes a scheme where competitors shared data through a common platform, used algorithms designed to align their pricing, and participated in vendor-hosted meetings to discuss competitively sensitive topics.
That's coordination. It doesn't require a formal agreement to charge specific prices. It requires conduct that has the practical effect of reducing independent decision-making and aligning competitive behavior.
Your compliance program needs to address the gray areas: the trade association committee where competitors start comparing notes on pricing trends, the vendor conference where competitors discuss how they've configured their shared software, the Slack channel where competitors in a data consortium share more detail than the formal reports provide.
Train your team to recognize situations where information exchange or joint conduct could reduce competition, even without an explicit agreement.
What to Do Instead
Start with a clear policy on competitively sensitive information. Define what it includes, prohibit sharing it with competitors (directly or through intermediaries), and require legal review before participating in industry data exchanges or benchmarking programs.
Conduct due diligence on third-party platforms that involve competitor data. Ask vendors how they prevent coordination, whether they host competitor meetings, and how their algorithms use shared information. If you can't get satisfactory answers, escalate to legal.
Train employees who interact with competitors or use shared platforms. Use realistic scenarios: "You're at an industry conference and a competitor asks how you're thinking about pricing for next year. What do you say?" Help them recognize the situations where they need to stop talking and call legal.
Build monitoring into your vendor management process. If you use third-party pricing tools, analytics platforms, or benchmarking services, periodically audit what data you're sharing and how it's being used. The Pinnacle decree's requirement for court-appointed monitors signals that passive oversight isn't enough.
The technology will keep evolving. The legal principles won't. Competitors can't coordinate pricing, capacity, or other competitive terms, whether they do it in a conference room or through an algorithm. Your compliance program needs to translate that principle into practical guidance your teams can actually use.
