<!doctype html>
<html lang="en">
	<head>
		<meta charset="utf-8">
		<meta name="viewport" content="width=device-width, initial-scale=1.0">
		<meta name="copyright" content="Copyright © 2026 NoHoops">
		<meta name="description" content="We're building a Personal Data Rights application designed to record personal data events and help data subjects and data controllers navigate the ever changing landscape of personal data management.">
		<title>NoHoops - The Privacy Policy Paradox</title>
		<link href="/f.png" rel="icon">
		<link href="/s.css" rel="stylesheet" type="text/css">
	</head>
	<body>
		<header>
			<section>
				<section class="logo"><a href="/" title="Home"><s></s><s></s><s></s><s></s></a></section>
				<nav>
					<button type="button" aria-label="Show the navigation menu"><span></span></button>
					<ul>
						<li><a href="/">Home</a></li>
						<li><a href="/articles">Latest Articles</a></li>
						<li><a href="/about-your-data">About Your Data</a></li>
						<li><a href="/about-us">About Us</a></li>
					</ul>
				</nav>
			</section>
		</header>
		<main>
			<article>
				<header>
					<h1>The Privacy Policy Paradox</h1>
					<p>Playing a staring role in consent theatre</p>
					<ul>
						<li>Chris Chapman</p>
						<li>25 January 2022</p>
					</ul>
					<p>
						For a data controller, the privacy policy is a legal document produced by a legal professional to provide the legal basis for processing personal data. So why is it starting to look like a legal hazard?
					</p>
					<p class="md">···</p>
				</header>
				<section>
					<p>The privacy policy has a dual purpose. The first is to inform the website visitor about the facts and risks related to processing their personal data. The second is to defend the legal interests of a data controller in court. When it comes to legal documents, the need to be effective in court will always override the need to be understood by non-lawyers (website visitors). This leads to a contradiction, namely, that a document that requires legal expertise to be understood is intended to be understood by someone <i>without</i> that legal expertise. We call this contradiction the <i>privacy policy paradox</i> and it has a direct impact on the utility of the cookie banner.</p>
					<p>The purpose of a cookie banner is to obtain a website visitors <i>lawful</i> consent to process their personal data.</p>
					<blockquote><p>Lawful consent is consent that is <em>informed</em> and <em>freely given</em>.</p></blockquote>
					<p>In order to be <i>freely given</i>, the website visitor must <i>willingly</i> click the Accept All button and, in order to be <i>informed</i>, the visitor must <i>read and understand the privacy policy</i>.</p>
					<p>As almost everyone clicks the Accept All button <i>without</i> reading the privacy policy, consent is hardly ever <i>informed</i> and thus, almost always <i>unlawful</i>. This not only has the effect of rendering the cookie banner almost entirely useless at obtaining <i>lawful</i> consent, it also raises the very real possibility that most personal data obtained in this manner has been obtained <i>unlawfully</i>. As legislators and law enforcement continue to tighten their grip on this situation, the risk to data controllers increases significantly and, in the end, it may be more cost effective to delete the data rather than face the consequences of retaining it.</p>
					<p>The dark pattern of the 'privacy policy/accept all' mechanism is the mainstay of the cookie banner. It is also the shovel that dug the hole that data controllers now find themselves in. The way out of that hole will involve new concepts and a new approach to consent.</p>
					<p>It may have started out with the best of intentions but in the end, the privacy policy has not only <i>inhibited</i> the lawful processing of personal data, it appears to have actively enabled the <i>unlawful</i> processing of it. That's why we believe it is a legal hazard.</p>
				</section><footer></footer>
			</article>
		</main>
		<footer>Copyright © 2026 NoHoops</footer>
	</body>
</html>