Key takeaways
- PECR still requires consent for cookies and similar tracking, with exceptions set out in Schedule A1 since February 2026.
- Simple statistics and site-function cookies can now run without consent if you explain them clearly and offer an easy, free way to object.
- Advertising pixels, social plug-ins and most third-party embeds still need opt-in consent before they load.
- Health websites carry extra risk: a tracker on a page about a condition can reveal special category data.
Why your website deserves a proper look
The practice website has become a front door. In the 2026 GP Patient Survey, 57.6% of patients said it was easy to contact their practice using its website, up from 47.9% in 2024[1]. Dental and private clinic sites carry booking widgets, enquiry forms, chat tools and payment pages. Each one may set cookies or load scripts that send data to someone else.
Source: Ipsos (GP Patient Survey provider for NHS England), 2026[1]
Show the data
| Item | Value |
|---|---|
| 2024 | 47.9% |
| 2026 | 57.6% |
Regulation 6 of PECR says a person must not store information, or gain access to information stored, in a user's device, subject to the exceptions in Schedule A1[2]. That covers cookies, local storage, pixels, device fingerprinting and similar techniques, not just files called cookies. The version in force since 5 February 2026 was substituted by the Data (Use and Access) Act 2025 and moved the exceptions into a schedule.
What can run without consent
Schedule A1 sets out the cases where you do not need consent[3]. In practice, four matter for a practice website.
- Strictly necessary: storage needed to provide a service the user asked for, such as keeping a booking form's progress, security and fraud prevention, or remembering what the user chose on the site.
- Statistics: storage whose sole purpose is to collect statistics to improve your website or service, provided users get clear and comprehensive information about it and a simple, free way to object, and have not objected.
- Appearance and functionality: storage whose sole purpose is to make the site appear or work in a particular way, or adapt to the user's preferences, with the same information and objection conditions.
- Transmission: storage needed only to carry a communication over the network.
The statistics and appearance exceptions are not a free pass. They apply only where that is the sole purpose. If your analytics provider also uses the data for its own advertising, or you link it to an advertising account, you are back to needing consent.
Common practice website tools, sorted
| Tool | Typical purpose | Consent needed? | What to check |
|---|---|---|---|
| Session and security cookies | Logins, forms, fraud protection | No (strictly necessary) | That they are not reused for tracking |
| Cookie preference cookie | Remembers the user's choice | No | Short lifetime |
| First-party visit statistics | Counting visits to improve pages | Not if the statistics conditions are met | Clear explanation and an easy objection link |
| Third-party analytics with advertising features | Statistics plus ad profiling | Yes | Turn off advertising features or ask consent |
| Advertising and social pixels | Measuring ads, building audiences | Yes | Do not load before opt-in; avoid on health pages |
| Embedded video | Showing a video | Usually yes | Use privacy-enhanced embeds or a click-to-load placeholder |
| Online booking or chat widget | Service the patient asks for | Often no for its core function | Ask the supplier what else the widget sets |
| Map embed | Showing the practice location | Usually yes for third-party maps | A static map image avoids the question |
Health pages raise the stakes
On most websites a pixel recording which pages a visitor viewed is a privacy issue. On a health website it can be more serious. A visit to a page about a sexual health clinic, a menopause service or a mental health referral, linked to an identifiable person by an advertising platform, can amount to processing data concerning health, which is special category data under Article 9 of UK GDPR[4]. Serious UK GDPR infringements can attract fines of up to £17.5 million or 4% of worldwide annual turnover[5].
The practical rule for practices and clinics is simple: no advertising or social tracking on condition, service or booking pages, even with consent, unless someone has assessed the risk properly. Keep any marketing measurement to general landing pages.
How to audit and fix your site
List what loads
Open the site in a private browser window with developer tools, clear storage and load the home page, a service page, the booking page and the contact form. Note every cookie, local storage item and third-party domain that appears before you touch the banner.
Ask your web supplier
Request a written list of every script, plug-in and tag on the site, who owns it and why it is there. Remove anything nobody can explain.
Classify each item
Use the table above: strictly necessary, statistics, appearance, or needs consent. Record the reasoning, especially where you rely on the statistics exception.
Block consent-based tags until opt-in
Configure the banner or tag manager so advertising pixels, social plug-ins and embeds do not load until the user agrees. Test again in a clean browser to prove it.
Write the cookie notice
Explain each category in plain words, name third parties, give lifetimes and provide the objection route for statistics in a place users can find.
Recheck after every change
New plug-ins and redesigns are where tracking creeps back. Make the audit part of the sign-off for any website change.
What a fair banner looks like
- Accept and reject buttons with equal prominence on the first layer; no reject hidden behind a settings link.
- No pre-ticked boxes and no tracking before a choice is made.
- Plain wording: ‘We use some cookies to make this site work and to count visits. With your permission we would also use cookies from video and social media sites.’
- A permanent link, such as ‘Cookie settings’ in the footer, so users can change their mind as easily as they agreed.
- A clear note on how to object to statistics cookies if you rely on that exception.
Example: Castle Lane Clinic, a fictional private physiotherapy clinic, finds that its site loads a social pixel and a third-party video player before the banner appears. The manager has the pixel removed from booking and condition pages, sets the video to a click-to-load placeholder, and keeps a first-party visit counter under the statistics exception with an objection link in the footer. The banner now asks only about video and social cookies.
Questions to ask your web, booking and chat suppliers
Most practice websites are built and hosted by a supplier, and many tracking tools arrive bundled inside a theme, a booking widget or a chat plug-in. You remain responsible for what your site does to visitors' devices, so put these questions in writing and keep the answers.
- Which cookies, local storage items and pixels does your product set, on which pages, and for how long?
- Which of them are needed for the service the patient asked for, and which are for analytics, advertising or your own product improvement?
- Can the non-essential ones be switched off, or held back until the visitor gives consent through our banner?
- Do you, or any third party you use, use data from our visitors for your own purposes, including advertising?
- Where is the data stored, and who are your sub-processors?
- Will you tell us before an update adds new cookies or scripts to our site?
- Can you give us a written processing contract that covers the patient data your widget collects?
If a supplier cannot answer, treat the tool as needing consent until it can. A booking or chat widget that cannot be configured to respect a patient's choice is a reason to change supplier, not to accept the risk.
Mistakes that turn up again and again
- A banner that looks compliant while tags fire on page load regardless of the visitor's choice.
- A reject option that sets the same cookies as accept, because the tag manager was never connected to the banner.
- A cookie notice copied from another site, naming tools the practice does not use and missing the ones it does.
- Advertising features left switched on in an analytics account after a one-off campaign ended.
- Old landing pages from past campaigns still live, still carrying pixels, and still indexed by search engines.
- Staff testing the site while logged in to admin tools, so they never see what a patient's browser actually receives.
Each of these is easy to fix once found, which is why the clean-browser test after every change matters more than the wording of the banner.
Keep the evidence
If a patient complains, you will want to show what your site did and when. Keep the audit list with dates, the supplier's tag list, screenshots of the banner, and a note of any change. Consent records held by your banner tool should show when a choice was made and which version of the notice the user saw.
Websites are one part of a wider set of patient communications rules. For messages sent after a visitor books, see service messages versus marketing and PECR for private clinics. Records generated through website forms still follow records retention rules, and forms that capture requests from solicitors or insurers should route them to the process in third-party records requests.
Frequently asked questions
Do we still need a cookie banner?
Yes, if your site uses any storage or tracking that needs consent, such as advertising pixels, social plug-ins or most third-party embeds. A site using only strictly necessary storage and compliant statistics may not need a consent banner, but still needs a clear cookie notice[3].
Can we use analytics without consent now?
Only where the sole purpose is statistics to improve your site or service, you explain it clearly and users have a simple, free way to object[3]. Analytics tied to advertising still needs consent.
Is a booking widget a strictly necessary cookie?
Its core function usually is, because the patient asked to book. Ask the supplier whether it also sets analytics or marketing storage, which may need consent.
Can we use a social media pixel on our treatment pages?
Avoid it. On health pages a pixel can reveal information about a person's health to an advertising platform, which is special category data[4].
References
Ipsos (GP Patient Survey provider for NHS England) (2026). 2026 GP Patient Survey results released (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). Privacy and Electronic Communications Regulations 2003, regulation 6 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). Privacy and Electronic Communications Regulations 2003, Schedule A1 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2026). UK GDPR Article 83: General conditions for imposing administrative fines (opens in a new tab) ↑