Are you protected because a company published a privacy policy? No. You are protected because they fear a regulator with actual teeth, and those are rarer than you think.
That’s the whole thing. That’s the post. But let’s make it useful anyway.
The Document Is Not the Point
Privacy policies exist for legal cover, not consumer protection. That distinction matters more than most people are willing to sit with.
When a company writes a privacy policy, the audience is not you. It’s their legal team, potential regulators, and the judge in a hypothetical future lawsuit. You are an afterthought dressed up as the intended recipient. The document says “we may share your information with third-party partners” and that phrase is doing an enormous amount of quiet work. “May” means will. “Partners” means buyers. “Share” means sell.
I judge systems by their error messages. A bad error message tells you something went wrong. A good one tells you exactly what, where, and why, so you can fix it. Privacy policies read like the worst error messages ever written. All consequence, no specificity, no path to resolution.
Length Is the Tell
Here’s the thing nobody says out loud: privacy policy length correlates almost perfectly with how much the company is doing to your data. Not against correlation, by design.
A company with nothing to hide writes something short. A company doing fourteen categories of behavioral profiling across seventeen data broker partnerships writes something that takes forty-five minutes to read and requires a law degree to interpret. The length is not thoroughness. It’s camouflage. The sheer volume of text functions as a wall that reasonable people bounce off, which is exactly what it was built to do.
Somewhere around 2010, the average privacy policy crossed 2,500 words. By 2020, some of them were clearing 10,000. What changed? The data collection got more aggressive. The policy got longer to cover the new collection. That is not a coincidence with an innocent explanation.
Consent Theater Has Specific Mechanics
The consent model the whole industry is built on assumes that publishing a document equals informed agreement. That assumption has never been true, and everyone involved knows it.
A Carnegie Mellon study estimated that if Americans actually read every privacy policy for every service they used in a year, it would take roughly 76 work days. Per person. Per year. The entire framework is built on a foundation of practical impossibility and then treated as meaningful consent in court.
The cookie banner is the purest expression of this. It pops up. You click accept because the decline button is gray and small and buried. The company logs that click as your informed consent. The data flows. Everyone moves on. The ritual was performed. The protection was not provided.
What Longer Policies Actually Added
The GDPR came along and forced more disclosure. Privacy policies got longer to accommodate the new required language. The data collection did not proportionally shrink. Companies added the disclosure sections and kept the practices. In some cases they formalized collection pipelines that had previously been informal, which made the practices more systematic, not less invasive.
The policy grew. The privacy shrank. The documentation of the shrinkage grew even more. It’s a strange kind of honesty where they tell you exactly what they’re doing to you in language designed to ensure you won’t understand it.
CCPA hit California. More disclosure requirements. Policies expanded again. “Do Not Sell My Personal Information” links appeared, often buried in footers, often leading to forms that applied only to direct sales and exempted the other twelve ways your data was moving.
Pattern recognition across enough of these documents produces a clear inference: the regulatory response and the industry response have been in an arms race, and the industry is better funded and more motivated.
The Error Message You Actually Got
If a system fails and the error message just says “An unexpected error occurred,” that tells you the system is not designed for you to understand what happened. It’s designed to present the appearance of communication while withholding the content.
That’s a privacy policy. It is an error message for a system that already failed, written by the people who broke it, optimized to prevent you from knowing exactly what broke.
The document is long now. Longer than ever. It covers more categories of data, more partner relationships, more retention periods, more jurisdictions. That growth is not protection. It’s the invoice for what was taken, written in a language you didn’t agree to learn.
The wall of text is the product. Your confusion is the feature.