Chrome again exempts Google from user site data settings

TEXT START: You can probably guess why I’m writing about the bug again: I’ve noticed Chrome doing something similar now.

The Dissection

This is a credible symptom report: the author changes relevant settings, avoids Chrome sign-in, verifies the deletion policy, observes Google site data persist, deletes it, and reproduces the result. The text then makes three moves: it documents a product-policy mismatch, attributes it primarily to incompetence, and calls for better QA and antitrust action.

What it is really doing is translating a power asymmetry into a software defect. Google controls the browser, the search path, and the technical meaning of “delete.” The user controls a preference panel whose promises may not bind the platform.

The Core Fallacy

The main error is reducing structural control to a quality-control failure. Whether the exemption is accidental or deliberate is secondary. The material fact is that an integrated platform can make itself the exception to rules presented as user-controlled.

A unit test could fix this particular behavior. It would not fix the architecture that lets the platform define, implement, and police its own privacy boundary. A breakup might change ownership and incentives, but competition alone does not guarantee user sovereignty. It can merely produce several competing sovereigns offering the same cage.

Hidden Assumptions

• The visible deletion setting accurately represents all relevant data retention.
• Choosing DuckDuckGo and refusing Chrome sign-in meaningfully removes Google’s influence from the transaction.
• The observed local data is an isolated bug rather than evidence of a broader control asymmetry.
• Better QA will correct the incentive, not merely the visible failure.
• Government intervention will arrive before platform adaptation neutralizes it.
• Opaque Google redirect URLs are merely a usability defect rather than another mechanism of platform observability and control.

The article establishes the behavior it observed. It does not establish motive, full data flows, or whether the exemption is intentional.

Social Function

Partial truth functioning as ideological anesthetic. The technical evidence is useful and the monopoly criticism is legitimate. But the diagnosis relocates the problem into careless engineers and a slow regulator, which makes the system appear repairable through QA and procedural enforcement.

That framing protects the deeper assumption that users remain sovereign consumers who merely need accurate settings and better competition. Under the Discontinuity lens, they are already operating inside infrastructure owned by a private information sovereign. The toggle is a concession, not a transfer of power.

The Verdict

If reproduced as described, Chrome’s behavior is not proof of conspiracy. It is proof of control. The article catches Google violating the boundary users thought they governed, then mislabels the breach as mere incompetence.

QA can cauterize this wound. Antitrust can rearrange the ownership chart. Neither automatically restores control to the user. The platform still decides what is retained, what is opaque, and what the consumer is allowed to believe has been deleted.