FTC's Personalized Pricing Statement: A Section 5 Warning Shot
What Changed: The FTC Put Personalized Pricing on the Enforcement Docket
On August 19, 2026, the FTC announced a proposed Enforcement Policy Statement Regarding Personalized Pricing and voted 2-0 to open a 30-day public comment period. The docket is FTC-2026-1057. This is a proposed statement, not a final rule, and it is not in force.
Do this quarter: inventory every place your product uses personal data to set an individual consumer's price, and decide whether you can defend that practice under Section 5 before a comment file becomes an enforcement file.
Read the vote for what it is. The Commission is telling the market how it intends to apply existing unfairness and deception authority to data-driven pricing. Counsel who wait for a final rule are reading the signal backwards.
The Authority Tell: Section 5, Not a New Statute
The most important sentence in the package is a concession. The proposed statement relies on Section 5 of the FTC Act and does not assert new statutory authority, and the FTC explicitly acknowledges it lacks authority to ban personalized pricing outright.
Chairman Andrew Ferguson framed the consumer expectation directly: when consumers see a listed price, they expect it to be the same price everyone else sees, not the retailer's estimate of how much they are willing to pay based on their personal data. That framing is a deception theory, not a per-se prohibition.
Why the framing matters
- Deception turns on whether your pricing conduct creates a net impression that misleads a reasonable consumer.
- Unfairness turns on substantial injury consumers cannot reasonably avoid and that is not outweighed by benefits.
- Neither theory requires a new rule. Both can support an enforcement action today.
That won't fly with a regulator: assuming that the absence of a final rule means the absence of exposure. Section 5 has been on the books the entire time.
Enforcement Signal-Reading: The 6(b) Study and the State Patchwork
This statement does not arrive in a vacuum. In July 2024, the FTC ordered eight intermediary firms to provide information under its Section 6(b) authority, and on January 17, 2025 released preliminary research summaries describing a wide range of personal data used to set individualized prices. The August 2026 statement is the enforcement posture that study was building toward.
The states are moving faster and harder. Maryland Governor Wes Moore signed the Protection From Predatory Pricing Act on April 28, 2026; it takes effect October 1, 2026 and bans surveillance pricing for large food retailers and third-party delivery services.
Connecticut Governor Ned Lamont signed HB 5563 on June 4, 2026. Note the timeline precisely: the surveillance pricing provisions take effect July 1, 2027, not October 2026. New Jersey enacted its Fair Price Protection Act on July 23, 2026, per a Holland & Knight advisory, becoming the third state to ban surveillance pricing for groceries with a private right of action.
The pattern is the same one we flagged with the state privacy law patchwork: federal signaling plus divergent state statutes means you cannot manage this from a single national policy.
Action Items for Counsel This Quarter
Treat the comment window as a compliance deadline, not a spectator event.
- Map the pricing data flow. Identify every input — browsing history, device signals, location, loyalty data, inferred willingness to pay — that feeds an individualized price. You cannot govern what you have not mapped.
- Classify the theory of harm against your own conduct. Ask whether a reasonable consumer would be surprised that their listed price reflects personal data. If yes, you have a deception exposure under Section 5.
- Check the state footprint. If you sell groceries or operate delivery in Maryland, New Jersey, or Connecticut, calendar the distinct effective dates — October 1, 2026 for Maryland, July 1, 2027 for Connecticut — and confirm whether your model falls within each statute's covered-entity definition.
- Preserve documentation now. A Section 6(b)-style inquiry expects data maps, model inputs, and logging on day one. Reconstructing them after a civil investigative demand is not a defense.
- Decide whether to comment. The docket closes 30 days after Federal Register publication. If your business model depends on data-driven pricing, silence in the record is a strategic choice you should make deliberately.
Do not conflate this proceeding with the April 2026 food-delivery fee ANPRM. They are distinct dockets, and treating them as one action will muddy your record and your risk assessment.
Key Takeaways
- This is enforcement signaling, not a ban. The FTC voted 2-0 to open comment while conceding it lacks authority to prohibit personalized pricing outright — the exposure runs through existing Section 5 unfairness and deception theories.
- Section 5 already applies. Waiting for a final rule misreads the posture. The Commission can bring a deception or unfairness action against data-driven pricing today, without any new statutory authority.
- The state map controls more than the federal statement. Maryland (effective October 1, 2026), New Jersey (enacted July 23, 2026), and Connecticut (surveillance pricing effective July 1, 2027) impose real, divergent obligations, including a private right of action in New Jersey.
- Documentation is the deliverable. The 6(b) study framework signals what a future inquiry expects: data maps, model inputs, and logging. Build them before the demand letter arrives.
- The comment window is a decision, not a courtesy. Docket FTC-2026-1057 closes 30 days after Federal Register publication. Firms whose economics depend on individualized pricing should decide whether to shape the record.
How FinTech Law Helps
Personalized pricing sits exactly where product design, data governance, and consumer-protection law collide — and that is the seam most companies staff badly.
FinTech Law helps companies operationalize privacy and consumer-protection compliance for data-driven pricing: pricing-data maps, Section 5 risk assessments, state surveillance-pricing coverage analysis for Maryland, New Jersey, and Connecticut, and comment-file strategy for docket FTC-2026-1057. The firm works where legal, engineering, and pricing teams actually meet, so your data maps and logging survive a regulator's first request rather than getting built after it.
If your model sets prices based on what an individual consumer will pay, do not wait for a final rule to test whether it survives Section 5.
This post is for general informational purposes only and does not constitute legal advice. Reading it does not create an attorney-client relationship. Consult qualified counsel about your specific facts.
For related counsel, see SEC exam counsel.
Contact FinTech Law to discuss.