Skip to content

PECR Compliance: Cookie Consent and Electronic Marketing Rules for UK Businesses

PECR in Brief

PECR sets the UK rules for cookies and similar technologies on websites and apps, and for marketing by email, text and phone. It works alongside the UK GDPR, and the ICO enforces both.

Cookies and Electronic Marketing under PECR

In the UK, the Privacy and Electronic Communications Regulations 2003 (PECR) cover two things most organisations do every day: storing or reading information on a visitor's device, which is what cookies and similar technologies do, and sending marketing by email, text message or phone. Organisations outside the UK will usually find comparable rules in their own law, but the detail below is the UK position.

PECR works alongside the UK GDPR and the Data Protection Act 2018. PECR decides when consent is needed for a cookie or a marketing message, and the UK GDPR sets the standard that consent has to meet. Cookies and marketing lists usually involve personal data, so in practice both apply at the same time. Both are enforced by the Information Commission, which operates as the Information Commission's Office (ICO).

The PECR Cookie Rule

The core rule is short. Nothing may be stored on a user's device, or read from it, without their consent unless an exception applies. The rule is about what a technology does rather than what it is called, so it covers tracking pixels, local storage, device fingerprinting and scripts that read information from the device as well as cookies. The ICO groups these together as storage and access technologies.

The rule also covers storage and access that an organisation instigates, not only what its own code does. A site owner answers for the tags its marketing agency adds, the analytics and advertising tools a plugin loads, and embedded videos, maps or social media feeds that set their own cookies when the page opens. Knowing what the site actually sets, who sets it and why is the starting point for everything else.

Visitors also have to be told clearly what is used and what for: the technologies, their purposes, any third parties that store or read information, and how long it lasts. Most websites do this in a cookie policy, linked from the website privacy notice and from the cookie banner.

We had a cookie banner for years and assumed it was doing its job. When our web agency rebuilt the site we asked them for a list of everything it set, and it ran to three pages. A heatmap tool, two advertising pixels from a campaign that had finished long before, a chat widget and a video player that dropped cookies the moment the page opened.

None of it was in our cookie policy. Since then, any new tag or plugin goes through the same change request as anything else on the website, and the cookie list is checked before it goes live.

PECR Exceptions to Cookie Consent

PECR sets out five exceptions where storage or access needs no consent. Each one depends on the purpose, not on the technology used:

  • Strictly necessary - essential to provide the online service the user has asked for, such as a shopping basket, a login, security, or remembering the user's cookie choices
  • Statistical purposes - collecting statistics about how the website or service is used, with a view to improving it
  • Appearance - remembering a user's preferences for how the site looks or works, such as language, text size or layout
  • Emergency assistance - identifying the location of a device so that emergency help can be given
  • Communication - storage or access whose only job is carrying a communication over a network, such as directing traffic to the right server

The statistical purposes and appearance exceptions come with conditions. Users have to be given clear information about the storage or access, and a simple way to object to it that costs them nothing. A switch in the cookie settings that is on by default and can be turned off at any time is a common way of doing this. Once someone objects, the storage or access has to stop.

The statistical purposes, appearance and emergency assistance exceptions each apply only where that is the sole purpose. An analytics tool that also feeds advertising, builds profiles of visitors or passes data to its provider for the provider's own use is not used solely for statistics, so it needs consent. Advertising, and tracking for advertising, is not covered by any of the exceptions and always needs consent.

Valid Cookie Consent and Cookie Banners under PECR

Where consent is needed, it has to meet the UK GDPR standard: freely given, specific, informed, and given by a clear positive action. For a cookie banner, that comes down to a few practical checks:

  • nothing that needs consent is set or read before the visitor has made a choice
  • rejecting takes no more effort than accepting, with a reject option as easy to find as the accept button
  • no boxes are pre-ticked, and no switches are already turned on, for anything that needs consent
  • nothing that needs consent is set after a visitor refuses
  • visitors can change or withdraw their choice later, for example through a cookie settings link in the website footer

Carrying on browsing a site is not consent, and neither is a notice saying cookies are used without offering a choice. The consent request also has to name the third parties whose cookies the visitor is being asked to accept, including those that appear to come from the site's own domain.

Open your own website in a private browser window, press reject, then have a look at what the browser has stored. If advertising or analytics cookies turn up anyway, the banner is not doing its job, however good it looks. Ten minutes, no specialist tools, and you will know where you stand.

PECR Rules for Email, Text and Phone Marketing

PECR also governs direct marketing sent by electronic means. For email and text messages to individuals, the starting point is consent: a specific opt-in to that kind of message from that sender. Consent given to someone else does not usually carry across, which is why bought-in lists so often cause problems.

The soft opt-in is the main exception. An organisation can email or text its existing customers about its own similar products or services without consent, provided it obtained their details during a sale or negotiations for a sale, gave them a clear chance to opt out when it collected those details, and offers the opt-out again in every message. Charities can use a similar soft opt-in for people who have supported or expressed an interest in their work, to promote their charitable purposes, but not to sell goods or services.

Business contacts are treated differently. Emails and texts to corporate subscribers, such as limited companies, limited liability partnerships and Scottish partnerships, do not need consent under PECR. Sole traders and some other partnerships count as individuals, so the consent and soft opt-in rules apply to them. Where a business contact is a named person, the UK GDPR still applies to their details, and an objection to marketing has to be respected.

Every marketing email or text has to say who it is from and give a valid way to opt out, such as an unsubscribe link or a reply address, whether or not consent was needed to send it.

Live marketing calls do not usually need consent, but numbers have to be screened against the Telephone Preference Service (TPS) and the Corporate Telephone Preference Service (CTPS), and against the organisation's own list of people who have asked not to be called. Automated calls that play a recorded message need specific consent to that type of call. Callers have to say who they are and allow their number to be displayed.

PECR Enforcement and Fines

The ICO can fine an organisation up to £17.5 million or 4% of its global annual turnover, whichever is higher, for breaching PECR. That is the same maximum as under the UK GDPR.

A breach does not have to be serious, or to cause substantial damage or distress, before a fine can be considered. Any contravention of the cookie rules can be fined, as can breaches of the marketing rules. The ICO often starts by writing to organisations and asking them to put things right, with enforcement notices and fines following where they do not.

The organisation running the website or sending the marketing is the one held responsible. Contracts with web agencies, platform providers and marketing services can share out the practical work, but they do not move that responsibility to someone else.

Practical Compliance Guidance

For a website, PECR compliance comes down to knowing what the site sets, describing it accurately to visitors, and a consent mechanism that works the way it says it does. For marketing, it rests on knowing how each contact was obtained and what they agreed to, with an opt-out in every message and a suppression list that is actually used.

Within a management system, PECR sits on the legal register alongside the UK GDPR, and a periodic check of the website and the marketing lists is a practical way to evaluate compliance with it. The documents below cover the website policies and that periodic check.

alphaZ document How to use it
GDPR / Data Protection Toolkit The full set of data protection documents, including the personal data register, the main and website privacy notices, the data protection procedure and the compliance checklist.
P-85 Website Cookies Policy The cookie policy for the website, explaining the cookies set, the third parties involved and how visitors change or withdraw their consent. Replace its guidance line with the site's own cookie list.
P-84 Website Privacy Policy The website privacy notice, covering what the site collects, cookies, third parties and any chatbot. Check its cookie wording against what the site actually sets before publishing.
F-Q106 GDPR Compliance Checklist A periodic check of data protection arrangements against the legislation on the legal register, recording what is in place and any actions needed.

Note - all the above files can be downloaded with an alphaZ subscription.

Frequently Asked Questions

Do analytics cookies need consent?

Not always. Analytics used only to produce statistics about how a website is used, with a view to improving it, can fall under the statistical purposes exception, as long as visitors are told about it and can object simply and free of charge. If the same tool also supports advertising, profiling or the provider's own purposes, the exception does not apply and consent is needed. How the tool is set up matters as much as which tool it is.

Do we need a cookie banner if our website only uses strictly necessary cookies?

No consent request is needed for cookies that are strictly necessary to provide the service the visitor has asked for. Visitors still have to be told what is used and why, which is usually done in a cookie policy linked from every page. Once anything else is added, such as analytics, embedded videos or advertising tags, the position changes.

Who is responsible for cookies set by third-party tools on our website?

The organisation running the website. PECR covers storage and access that the site owner instigates, so cookies set by an agency's tags, a plugin or embedded content from another platform are the site owner's responsibility as well as the third party's. A contract can share out the practical work, but it does not take that responsibility away.

Can we send marketing emails to business contacts without consent?

For limited companies, limited liability partnerships and other corporate subscribers, PECR does not require consent, but each email must identify the sender and give a way to opt out. Sole traders and some partnerships are treated as individuals, so consent or the soft opt-in is needed for them. The UK GDPR still applies to the personal details of named contacts.

UK Legislation

The following UK legislation is directly relevant to cookies and electronic marketing. Organisations outside the UK should identify the equivalent legislation applicable in their jurisdiction.

Further Resources