Three States, Three Bans, Zero Consistency: Choosing Your Personalized Pricing Compliance Path

The Decision You're Facing

Your pricing engine uses customer data, such as location, purchase history, or browsing behavior. Now you need to decide: Do you redesign your pricing logic for each state, build a national compliance floor, or exit certain markets entirely?

Maryland, Connecticut, and New Jersey have enacted laws restricting how you use personal data to set prices, with effective dates ranging from October 2026 to August 2027. New York's One Fair Price Act awaits the governor's signature. The FTC issued a proposed enforcement policy statement in August 2026, signaling federal scrutiny ahead. These laws don't align. Maryland targets food retailers and delivery services. Connecticut phases in provisions for retail sellers and data brokers. New Jersey adds a private right of action through its Consumer Fraud Act.

You can't treat this as a single compliance project. The definitions, covered entities, and enforcement mechanisms vary enough that your choice depends on where you operate, what you sell, and how your pricing systems collect and process data.

Key Factors That Affect Your Choice

Your sector determines exposure. If you're a food retailer or delivery platform, you're in scope across all three enacted laws. If you sell housing, rideshares, or general consumer goods, you're watching bills that target broader categories.

Your data architecture matters. Connecticut defines "surveillance pricing" as customized pricing based on personal data collected through biometric monitoring, cameras, device tracking, or sensors. If your pricing system relies on third-party data purchases rather than direct collection, you still fall under this definition. New York's proposed law would prohibit data collectors and providers from facilitating surveillance pricing, not just the businesses that set final prices.

Your geographic footprint shapes risk. New Jersey's private right of action creates a different liability profile than Maryland's state-enforced ban. If you operate in New Jersey, you're defending against consumer lawsuits, not just regulatory inquiries.

Your pricing mechanism needs scrutiny. Some laws focus on algorithms, others on data inputs, and still others on price variability. Seattle's Fair Pricing and Transparency Ordinance, effective September 2027, prohibits "algorithmic-based price discrimination" and bans electronic shelf label systems that display prices modified through such discrimination. If your pricing is algorithmic but doesn't use personal data, you may comply with one law but violate another.

Path A: State-by-State Compliance

Choose this path if you're a food retailer or delivery service operating only in Maryland, Connecticut, or New Jersey, and your pricing systems are already segmented by jurisdiction.

You need to:

Build separate pricing logic for each state that removes personal data inputs. Maryland's Protection from Predatory Pricing Act prohibits dynamic pricing or using consumer personal data to set prices for consumer goods or services. Connecticut's Public Act No. 26-130 bans customized pricing based on personal data collected through technology including biometric monitoring, cameras, device tracking, or sensors. New Jersey's Fair Price Protection Act prohibits using online activity and other personal information to personalize prices for groceries and other necessities.

Map your data flows to each state's definition. Connecticut's law includes data "gathered, purchased or otherwise acquired" from third parties. If you buy location data from a data broker and use it to adjust delivery fees, you're in scope even if you don't collect that data directly.

Track phase-in dates. Connecticut's data broker provisions took effect October 1, 2026. Its surveillance pricing ban takes effect July 1, 2027. Maryland's law went into effect October 1, 2026. New Jersey's prohibition starts August 1, 2027.

Document your compliance posture for each jurisdiction separately. You'll need to show auditors and regulators that your Maryland pricing engine doesn't touch personal data, while your systems in states without bans may still use it.

This path works when:

• You operate in three or fewer states with enacted bans
• Your product lines fit neatly into covered categories (food, groceries, necessities)
• You can maintain separate pricing systems without operational friction
• You don't plan near-term expansion into states considering broader bans

This path fails when:

• You operate nationally and can't segment pricing by state
• Your product mix includes both covered and uncovered categories
• Your data architecture makes it impossible to isolate personal data inputs by jurisdiction

Path B: National Compliance Floor

Choose this path if you operate in multiple states, face expansion pressure, or want to preempt federal action.

You need to:

Define "personal data" using the broadest state definition. Connecticut's law covers data collected through "any technology or technological method, system or tool." New York's proposed law defines surveillance pricing as pricing "set completely or in part by an algorithm that uses personal data to offer different prices to different customers for the same goods or services." Use the most expansive definition as your baseline.

Eliminate personal data inputs from pricing algorithms nationwide. This doesn't mean abandoning dynamic pricing entirely. You can still adjust prices based on inventory levels, time of day, or aggregate demand signals. You just can't use individual customer data or segmented group characteristics.

Audit third-party data sources. If you purchase data from brokers, verify that none of it feeds into pricing decisions. Connecticut's law explicitly covers data "gathered, purchased or otherwise acquired" from third parties. New York's proposed law would prohibit data collectors from facilitating surveillance pricing, creating upstream liability.

Build disclosure mechanisms even where not required. The FTC's proposed enforcement policy statement commits to action against companies that fail to disclose how personal data is used to set prices. If you're using personal data for non-pricing purposes (recommendations, marketing), document that separation clearly.

This path works when:

• You operate in five or more states
• You face regulatory uncertainty in key markets
• Your board wants a defensible national position
• You can achieve competitive pricing without personal data inputs

This path fails when:

• Your business model depends on personalized pricing for profitability
• You operate only in states without enacted or proposed bans
• You're willing to exit certain markets rather than redesign pricing

Path C: Selective Market Exit

Choose this path if personalized pricing is core to your model and you can't achieve target margins without it.

You need to:

Calculate the revenue impact of removing personal data from pricing in each state with a ban. Compare that to the cost of maintaining separate systems or the risk of enforcement.

Evaluate New Jersey's private right of action separately. The state incorporated surveillance pricing into its Consumer Fraud Act, creating exposure beyond regulatory fines. If your pricing systems can't be redesigned and New Jersey represents a small market share, exit may be the rational choice.

Monitor New York's governor. If signed, the One Fair Price Act would prohibit surveillance pricing broadly, not just for specific sectors. New York's definition covers pricing "set completely or in part by an algorithm that uses personal data to offer different prices to different customers." If you sell any consumer goods or services in New York and rely on personal data for pricing, you're choosing between redesign and exit.

Document your decision process. If you exit a market due to compliance costs, your board and investors need a clear record showing you evaluated alternatives.

This path works when:

• Personalized pricing drives your competitive advantage
• The affected states represent less than 15% of revenue
• You can reallocate resources to higher-margin markets
• You're prepared to defend the exit decision publicly

This path fails when:

• The affected states include major markets (New York, California if it enacts a ban)
• Your brand can't withstand criticism for avoiding consumer protection laws
• You operate in sectors where market exit triggers regulatory scrutiny (essential services, utilities)

Summary Matrix

The FTC's proposed policy statement and the wave of state legislation signal that this issue isn't going away. If you're building pricing systems today, assume you'll need to defend how you use personal data within 18 months. The states that have acted represent the leading edge, not the outliers.

Your choice depends on whether you can compete without personal data in your pricing logic. If the answer is yes, build the national floor now. If the answer is no, you're choosing which markets matter most.