Surveillance Pricing Ban: The Data Isn't Yours | Elacity
New York City voted to pass a surveillance pricing ban that would stop stores using your data to charge you a different price. A city rule can stop the trick. It does not make the data yours.
New York City Voted to Ban Surveillance Pricing. Your Data Still Sets the Price.
On November 12, New York City voted to pass a surveillance pricing ban: a rule that would stop a business from using data about you to charge you more than the person next to you for the same item. Until the mayor signs it, that rule is not law. Even after it is, the data that set the price will still not be yours.
That day the New York City Council approved Introduction 891-A, sponsored by Speaker Julie Menin. The bill defines surveillance pricing as a price 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. Menin called the practice "deceptive and insidious." The Council voted 44 to 5. The bill now goes to the mayor, and until he signs it, New Yorkers do not yet have the protection the vote described.
The bill would give the Department of Consumer and Worker Protection the power to investigate and to issue fines of up to $1,000 for each violation, with each affected consumer or transaction treated as a separate violation, according to the Council. It would still allow bona fide discounts and rewards that are legitimate and transparent, from buy-one-get-one-free deals and loyalty programs to discounts for veterans and students.
On October 8, Seattle Mayor Katie Wilson signed a law that bars large grocery retailers and delivery services from using personal information to charge shoppers different prices for the same product. That law does not apply to chains with fewer than 20 locations. According to EPIC, a signed New York City bill would join Seattle and existing state bans in Maryland, Connecticut and New Jersey. On October 28, the Federal Trade Commission said it is ordering Delta Air Lines, Walmart and other companies to provide detailed information on how they use consumers' data when setting prices.
A city can write a rule about the checkout. It cannot, by itself, change who holds the file.
The Failure of a Surveillance Pricing Ban
A surveillance pricing ban is a geographic instruction to a business: in this city, do not use personal data that way when you set a price. That matters, because the practice is designed to be invisible. You are not shown a second price. You are not told which facts about you were fed into the quote. You only see the number you are asked to pay.
What the ban does not do is give you the data back. The copies already sit with retailers, delivery apps, ride-share platforms and the brokers who sell profiles of your habits. You cannot set terms on a record you do not hold. You cannot withdraw a feed you never granted as a specific use. When companies treat customer data as an asset, the people who generated it often have no seat in what happens next, as we wrote when Spirit Airlines' data went up for sale.
Law also moves on a political clock. A bill can pass a council and wait on a desk. A carve-out can leave a whole class of seller outside the rule, as Seattle did for smaller grocery chains. None of that is an argument against the bill. It is a reminder of what a statute is: a rule about conduct in a place, not a transfer of ownership.
The Elacity Solution
The deeper failure is the theory of the data itself. As long as your profile is raw material for someone else's pricing engine, the best outcome you can hope for is that a city tells them to stop. The better design is to treat that data as property whose owner sets the terms of use. That is the core of Elacity's manifesto, and it is how you turn your data into capital instead of leaving it as an input someone else meters.
That is what we are building Elacity dDRM for. In the design, you package data, work or IP into a Wealth Capsule: a programmable good with its terms and royalties written in. A buyer or a service that wants to use it does so under a grant the owner issued, not under a store policy the owner cannot edit.
1. Terms that travel with the data
A privacy policy and a city ordinance both live outside the file. One is written by the company. The other is written by a legislature. The record itself carries no terms. A Wealth Capsule is designed to carry its terms of use with it, so the conditions are part of the good, not a notice you receive after the copy has already been made.
2. A grant from the owner, not a silent feed
Surveillance pricing works because a business can use a profile without asking you for that specific use. The Elacity design we are building treats use as something the owner grants. If a firm wants to rely on data you have packaged, it should need a permission you issued for that purpose. A quiet feed into a pricing algorithm is not a grant.
3. The owner sets the terms of use
The point is not a promised payout from a fine. It is control. The owner decides whether the good may be used, for what, and on what terms, including any royalty written into the capsule. That is a property rule, not a hope that an investigator will catch an invisible price.
A city ban still has a job. It can forbid a practice you cannot see, in a market you have to use. Elacity dDRM will not automatically cover data others create about you, a location ping or a browse trail, unless that data is something you can hold and package. The law and the property model do different work, and you need both.
If a price was set from your data, ask a simpler question than whether your city has passed a ban: who holds that data, and who is allowed to change the terms? Follow Elacity on X.