Is a Cookie-Free Fingerprint Script Still Caught by PECR?
A common belief goes: "we set no cookies, so PECR does not apply to us". It is wrong. Regulation 6 of the Privacy and Electronic Communications Regulations never mentions cookies. It is written around what you do to the user's device, and a fingerprinting script does plenty.
This is general information, not legal advice, and a few edges depend on the facts. I will mark where the law ends and my reading begins.
What regulation 6 actually says
The text, in regulation 6 of SI 2003/2426, says a person must not store information, or gain access to information stored, in the terminal equipment of a subscriber or user unless certain conditions are met. Those conditions are:
- the user gets clear and comprehensive information about the purposes; and
- the user has given consent.
There are exceptions: for transmitting a communication, and where the storage or access is strictly necessary for a service the user asked for. The Data (Use and Access) Act 2025 added further exceptions, including some for low-risk analytics, with conditions attached. Check the current text before relying on any of them.
Nothing there says "cookie". That is legislation, not interpretation.
What a fingerprint script does on the device
A fingerprinting script reads things from the browser and device, then combines them into an identifier. A typical sketch:
const parts = [
navigator.userAgent,
navigator.language,
screen.width + "x" + screen.height,
Intl.DateTimeFormat().resolvedOptions().timeZone,
];
const c = document.createElement("canvas");
const g = c.getContext("2d");
g.fillText("probe", 2, 2);
parts.push(c.toDataURL());
const id = await crypto.subtle.digest(
"SHA-256",
new TextEncoder().encode(parts.join("|"))
);
Each line reads something from the terminal equipment. No cookie, no localStorage, nothing written. The question is whether reading counts as "gain access to information stored" there.
Quick detour: why the canvas trick works
Hang on, why does drawing text tell you anything? Because the pixels depend on the GPU, driver, font rendering and anti-aliasing settings of that particular machine. Two identical-looking laptops can produce slightly different images, and the hash of that image becomes one more signal. It is a daft idea that works annoyingly well.
Is reading the browser's answers "access"?
The counter-argument is real. A script asks the browser, and the browser volunteers an answer. Is that "gaining access to information stored" on the device? Screen size and installed fonts are stored in some sense: they are properties of the device.
The regulator does not accept that reading. The ICO's guidance on storage and access technologies treats device fingerprinting as in scope, alongside cookies, pixels and local storage. That is regulator guidance, not a court ruling, and a tribunal could in theory read the words more narrowly. The EU regulators take the same view of the equivalent ePrivacy provision.
My own opinion: the technology-neutral wording is deliberate. A reading that exempts fingerprinting would let the identifier-by-another-route defeat the rule it sits beside.
Where the line is less clear
Not every fingerprint is a script on the device. Consider server-side fingerprinting, using only the IP address and headers the browser sent anyway. Nothing runs on the device and you read nothing from it.
- Active scripts (canvas, audio, font probing): clearly within regulation 6 on the ICO's approach.
- Passive header hashing at the server: arguable, and I would not bank on regulation 6 not applying.
- Either way, UK GDPR is likely to apply if the identifier singles out a person.
That last point matters. Regulation 6 consent and UK GDPR lawful basis sit side by side. A stable identifier that follows someone across visits is very likely personal data.
Can you rely on the "strictly necessary" exception?
Sometimes, for narrow uses. Fraud detection on a payment or login page is the usual candidate. The test is strictness: necessary for the service the user asked for, not necessary for your business model.
The weak point in the "this is covered" argument is the purpose. Fingerprinting to spot a stolen session on a login form is far easier to defend than fingerprinting every visitor to count them or build a profile. Using the same identifier for advertising or analytics undoes the exemption for that use.
A practical check
- List every script that reads device properties, including third-party ones you did not write.
- For each, write down its purpose in one sentence.
- If the purpose is not strictly necessary or within a statutory exception, get consent before it runs.
- Tell users what it does, in plain words.
"No cookies" makes a decent marketing line. As a legal position under PECR it does not hold up.