Privacy Policy Changes: One Side Holds the Pen | Elacity
Ohme deleted its promise never to sell your data for marketing. Dave & Buster's now names data brokers. A privacy policy is an agreement only one side can edit, and that is the real problem.
Privacy Policy Changes Deleted the Promise Not to Sell Your Data. Only One Side Holds the Pen.
Somewhere in your inbox is an email saying a company has updated its privacy policy. For some customers this month, that email was the only notice that a promise about their data had stopped existing.
On November 9, the EV charger maker Ohme updated its UK and Ireland privacy policy. The line "We will never share or sell your personal data to third parties for marketing purposes" is gone with nothing in its place, and the new version says it may be amended at the company's sole discretion, according to a customer's comparison reported by PrivacyAffairs.
Dave & Buster's went further. A 2020 notice whose sharing section opened with "We do not sell" was replaced by a full rewrite effective November 4, as the tracker QuietlyChanged found. The new policy says the company sells or shares identifiers and online activity "with advertising networks, data brokers and other companies involved in digital advertising."
The same document prices what it collects. For its rewards programme it states: "We estimate the value of personal information as less than a dollar, based upon the value of bonus Game Chips."
Read both changes as a question of power, not only of privacy. A privacy policy change is an edit to an agreement where one party writes, revises and dates every version, and the other party finds out by email.
Why Most Privacy Policy Changes Are Allowed
None of this is a scandal on its own. Products change, laws change, and a notice written in 2020 cannot describe a 2026 business. Dave & Buster's rewrite even improves some things: it now commits to act on opt-outs within 15 business days and honours the Global Privacy Control signal from states whose privacy laws apply to it.
To be fair to Ohme, its new policy does not say it sells data. It simply no longer says it won't.
There are limits. In 2024 the FTC warned that quietly changing a privacy policy to allow broader data use, and telling users only through a retroactive amendment, may be an unfair or deceptive practice, as the law firm Crowell & Moring summarised it.
Pressure works too. Meta's proposed business terms, criticised for language that appeared to let it train AI on scraped publisher content, will not take effect on November 20, 2026, Meta now says on its website.
What the Pen Still Decides
Those limits govern how a change is announced. They do not move who makes it. Notices, consent screens and opt-out forms are all ways of asking you to react to a draft someone else wrote.
AtCoder, a programming contest site, shows the pattern at its most courteous. It announced it would license user-submitted source code to AI companies, including code submitted in the past, with an opt-out setting and a one-month grace period. That is honest notice. It still reaches back to work written under older terms, and anyone who misses the window is included by default.
Data already collected is the hardest case. Once records sit in a company's systems, its policy governs them, and in a bankruptcy they can be auctioned like furniture, which is how the Spirit Airlines data sale ended up with bidders and no seat for the people in it. This week Reuters reported that Google agreed to additional privacy protections for that purchase. A union won them, not the individuals.
Terms That Travel With the Data
The structural fix is to change where the terms live. If they sit in the company's document, the company can edit them. If they sit with the data, changing them takes the owner.
That is the design Elacity is building toward with Elacity dDRM. You package data or work into a Wealth Capsule with its terms written in: who may use it, for what, for how long, and on what royalty. We cover the packaging step in how to turn your data into capital.
- Who writes the terms: today the collector; in the Elacity design, the owner.
- How terms change: today by an email you may never open; in the Elacity design, only with the owner's agreement.
- Who sets the price: today the collector, sometimes at less than a dollar; in the Elacity design, the owner, and a buyer can accept or walk away.
Nothing here promises income. Royalties are a feature an asset can carry; whether anyone wants to use it is still up to the market. What changes is who gets to say yes.
Where This Stops
This is what we are building, not a product you can use today. It also has a hard limit: it covers what you choose to package. Camera footage of you in a store, or the purchase history a loyalty card builds, is created on someone else's systems, and only law reaches it.
So keep using the tools you already have: opt-out links, the Global Privacy Control, access requests. They are worth the effort. They are also all requests, made to the party holding the pen.
Before you trust any promise about your data, ask who can change it and whether they need you to. More on how platforms distribute power lives in Social Architecture. To follow the argument, Follow Elacity on X.