The New York City Council approved legislation on November 12 that would prohibit surveillance pricing, moving a proposed consumer-protection rule from the debate stage to an enacted Council measure awaiting the remaining city-law process. Introduction 891-A defines the covered practice as pricing set completely or partly by an algorithm that uses personal data to offer different customers different amounts for the same goods or services.
The vote is a material development from the Council's earlier announcement that the bill was scheduled for consideration. Businesses and consumers should still check the official legislative record for the final adopted text, mayoral action, effective date and any later rules. Council approval establishes the chamber's decision; it does not mean every compliance obligation began immediately on November 12.
The measure is aimed at individualized pricing that is difficult for a buyer to detect. A customer normally sees only the amount presented on one device or account and may not know that a different person received another quote. When the price depends on inferred urgency, location, browsing behavior or another personal attribute, ordinary comparison shopping may not reveal the mechanism.
The Council's framework distinguishes the prohibited process from transparent discounts and rewards. Publicly described loyalty programs, student or veteran discounts and familiar promotions can use understandable eligibility rules without secretly calculating what one person may tolerate. The compliance question is therefore not whether every customer always pays the same amount, but whether personal data and an algorithm generated an undisclosed individual price.
Enforcement is expected to involve the Department of Consumer and Worker Protection. The Council's pre-vote description included investigations, penalties and a corrective route for qualifying small businesses. The final law and implementing guidance will need to specify records, complaint procedures and the circumstances in which a correction avoids a monetary penalty.
Technical boundaries matter. Retailers and online services use algorithms for inventory, time-based offers, fraud controls, geographic availability and market-wide demand. Regulators will need to determine whether a price difference came from a generally applied business rule or from a personal profile. That task may require documentation of model inputs, customer segments, testing and changes to quoted prices.
Consumers should not be expected to reverse-engineer a pricing system before filing a complaint. A practical process can accept receipts, screenshots, timestamps, account conditions and comparable offers, then allow investigators to request the relevant internal records. Privacy safeguards are also necessary because a complaint about personal-data use should not expose more personal information than the investigation requires.
For companies, the next step is to map where prices are generated and which data fields reach the decision system. A written policy is not enough if a third-party service or experimentation platform changes amounts in practice. Contracts with vendors should identify responsibility for data use, audit access and response when the city requests records.
Public reporting can help the city evaluate whether the rule works. Aggregate figures on complaints, substantiated violations, corrections and penalties would show activity without disclosing consumer identities or proprietary code. Guidance should also offer examples that separate permissible public discounts from prohibited individual calculations.
The Council's action places a limit on how personal data may be converted into a price, not only on whether the data may be collected. The law's effectiveness will depend on clear definitions and enforceable access to evidence. Until the final effective date and agency instructions are published, consumers and businesses should rely on the adopted record rather than assuming every form of variable pricing is covered.
Primary sources: New York City Council passage announcement; Introduction 891-A legislative record. Reviewed November 13, 2026. Development: Council approval announced November 12, 2026.