Privacy Policy Statistics 2026: Length, Reading Time & Who Reads Them
The average privacy policy today runs close to 7,000 words (6,938, to be exact) and takes close to half an hour to read. If you read every policy you actually agreed to this year, that's roughly 70 eight-hour workdays, and only about one in three websites has a working privacy policy for you to open in the first place. Here's where each of those numbers comes from.
Last updated: September 2026
Key findings
- Privacy policies have nearly tripled in length since 2008: the median policy was 2,514 words then (F1) versus 6,938 words for a top US site today (F5).
- Reading every policy you agree to in a year would take about 70 eight-hour workdays by current numbers (F7), close to the widely-repeated "76 workdays" figure, but for a completely different, unrelated reason (see below).
- The oft-cited "76 workdays" claim doesn't actually match the math of the 2008 study it's credited to, whose own number works out to about 30.5 workdays (F3, F4).
- Two independent surveys, four years apart, found the exact same figure: 56% of US adults routinely accept privacy policies without reading them, in both 2019 and 2023 (F8, F9).
- Only about 34% of websites have an accessible privacy policy at all, per a 2023 academic scan of 7 million sites (F10).
How long is a privacy policy, and how long does it take to read one
The most-cited figure for privacy policy length comes from a 2008 Carnegie Mellon study by Aleecia McDonald and Lorrie Faith Cranor, "The Cost of Reading Privacy Policies": a median length of 2,514 words (F1), taking about 10 minutes to read (F2). It's still the number Wikipedia's own "Privacy policy" article cites today, 18 years later.
A 2023 NordVPN study, which measured the actual policies of the top 20 most-visited websites in 19 countries, found something very different: an average of 6,938 words for the US sample (F5), nearly three times the 2008 median. The longest single policy they measured, Meta's, ran 19,434 words and took nearly 82 minutes to read on its own.
How long would it take to read every policy you agree to in a year
McDonald and Cranor didn't stop at one policy. They estimated that an average internet user encounters about 1,462 unique websites a year, and calculated that reading a privacy policy for every one of them would take roughly 244 hours a year (F3), or about 30.5 eight-hour workdays.
That's not the number most people have heard, though. A March 2012 TIME/Techland article turned this into a much bigger, catchier claim: "You'd Need 76 Work Days to Read All Your Privacy Policies Each Year" (F4). It's been repeated on blogs, forums, and "fun fact" sites ever since. The trouble is the arithmetic: 244 hours divided by an 8-hour workday is 30.5 days, not 76. TIME's own piece states the 76-day figure without showing how it got there, and I couldn't find a source that shows the working or checks it against the study it's credited to.
Here's the twist: using 2023 data instead of 2008 data, a modern equivalent lands in the same neighborhood, just for an unrelated reason. NordVPN's 2023 study found that reading the privacy policies of the 96 sites an average person visits monthly would take 46.6 hours a month in the US (F6). Annualized, that's 559.2 hours a year, or about 70 eight-hour workdays (F7). That isn't because the old "76 days" claim was right. Privacy policies have simply grown long enough since 2008 that a version of the old claim is closer to true today than it was when it was first published.
Does anyone actually read them
Two nationally representative US surveys, four years apart and run by different organizations, arrived at the same number. In February 2019, an Axios/SurveyMonkey poll of 4,048 US adults found 56% said they "always" or "usually" accept privacy policies without reading them, including 46% of 18-24-year-olds who said they skip every time, against just 15% of adults 65 and older (F9). In a 2023 survey of 5,101 US adults, 56% again said they accept privacy policies without reading them "always, almost always, or often" (F8).
A frequently-repeated older claim, that only 3% of consumers read privacy policies carefully, traces to a 2001 Privacy Leadership Initiative study. We looked for the original report to verify it and couldn't find a working copy anywhere, including in Wikipedia's own citation for it, which only points to a secondary blog post. We've left that one out rather than repeat a number we couldn't check ourselves. The two surveys above are the current, verifiable version of the same point.
How many websites even have a working privacy policy
A 2023 study out of Penn State, presented at the ACM Symposium on Document Engineering, scanned 7 million organization websites and found privacy policy URLs were only accessible on 34% of them (F10). That means roughly two-thirds had no working privacy policy a visitor could find. As of this writing, that finding has been reported by exactly one general-interest outlet, with no link back to the paper itself.
Annual reading burden: three competing numbers
Eight-hour workdays per year to read every privacy policy an average person agrees to. The 2012 media figure and the 2023 recompute land close together by coincidence, not because the old figure was correct.
The full data table
Every figure above, with its source. Link to a single row with #F1 through #F10.
| ID | Figure | Value | Source | Date |
|---|---|---|---|---|
| F1 | Median privacy policy length, 2008 | 2,514 words | McDonald & Cranor, I/S Journal | Jul 2008 |
| F2 | Average reading time per policy, 2008 | 10 minutes | McDonald & Cranor, I/S Journal | Jul 2008 |
| F3 | Annual reading burden, 2008 estimate | 244 hours/year (~30.5 workdays) | McDonald & Cranor, I/S Journal | Jul 2008 |
| F4 | Widely-repeated media claim | 76 workdays/year | TIME/Techland | Mar 2012 |
| F5 | Average policy length, top 20 US sites, 2023 | 6,938 words | NordVPN | Oct 2023 |
| F6 | Monthly reading burden, 2023 (96 sites/month) | 46.6 hours/month | NordVPN | Oct 2023 |
| F7 | Annualized reading burden today (computed) | ~70 workdays/year | Computed from F6 (46.6 × 12 ÷ 8) | 2023 data |
| F8 | Accept without reading, "always/often" (2023, n=5,101) | 56% | 2023 US survey | May 2023 |
| F9 | Accept without reading, "always/usually" (2019, n=4,048) | 56% | Axios/SurveyMonkey | Feb 2019 |
| F10 | Websites with an accessible privacy policy URL (of 7M) | 34% | Srinath et al., ACM DocEng 2023 | Aug 2023 |
Methodology
Every figure on this page comes from a named, dated, primary source: peer-reviewed research, an author's own published draft, or a survey report, opened and checked directly rather than taken from another blog's summary. Two figures are computed rather than directly stated in a source, and both show their formula: F7 annualizes NordVPN's own monthly reading-time estimate (46.6 hours × 12 months ÷ 8-hour workday), and F5's "F3 + F5" comparison is simple arithmetic between two separately-sourced figures, not a new study. One commonly-cited figure (a 2001 claim that only 3% of consumers read privacy policies carefully) was deliberately left out because its original source couldn't be independently verified.
Sources
- Aleecia M. McDonald & Lorrie Faith Cranor, "The Cost of Reading Privacy Policies," I/S: A Journal of Law and Policy for the Information Society, July 2008
- TIME/Techland, "You'd Need 76 Work Days to Read All Your Privacy Policies Each Year," March 6, 2012
- NordVPN, "Privacy Policy Study," October 23, 2023
- "Frequency of accepting privacy policies without reading them, US," survey fielded May 2023
- Axios/SurveyMonkey, "Privacy policies are read by an aging few," February 28, 2019
- Srinath, Sundareswara, Venkit, Giles & Wilson, "Privacy Lost and Found: An Investigation at Scale of Web Privacy Policy Availability," ACM DocEng 2023
Sources accessed and figures re-checked September 25, 2026.
How to cite this page
Frequently asked questions
Is the "76 workdays" figure fake?
Not fake, exactly, but unverified. It comes from a real 2012 TIME article, but that article's own number doesn't match the math of the 2008 academic study it credits, which works out to about 30.5 workdays. Nobody seems to have checked it before recirculating it. Coincidentally, using current 2023 data, a real recomputed figure lands close to 76 anyway, for unrelated reasons; see the "How long would it take" section above.
Why doesn't this page cite the "only 3% read privacy policies carefully" statistic?
We tried to verify it and couldn't. It's widely attributed to a 2001 Privacy Leadership Initiative study, but every citation we found, including Wikipedia's, traces back to a secondary source rather than the original report. Rather than repeat an unverifiable number, we used two real, checkable, more recent surveys instead (F8 and F9).
Why has the average privacy policy gotten so much longer since 2008?
This page doesn't have a sourced answer to that specific question, so we're not guessing at one. What the data shows is the change itself: a median of 2,514 words in 2008 versus 6,938 words for a major US site in 2023.
Does a shorter privacy policy mean better privacy protection?
Not automatically, length and clarity aren't the same thing, but a policy nobody can realistically finish reading also isn't doing its job of actually informing anyone. See how to write a privacy policy for what a policy needs to cover regardless of length.
This page was compiled by Cedrick Reese from six named, dated primary sources, two academic papers, one marketing-research study, and two consumer surveys, opened and checked directly rather than copied from other stat roundups. The two computed figures (F5 and F7) show their formula rather than presenting a calculation as a quoted fact. It's checked periodically as newer studies come out and updated when a figure changes or a better source appears.