GDPR for Law Firm Websites: Privacy, Cookies and Enquiry Form Review Workflow
GDPRCookie ConsentPrivacyEnquiry FormsCompliance Reviews

GDPR for Law Firm Websites: Privacy, Cookies and Enquiry Form Review Workflow

SSolicitor.live Editorial Team
2026-11-17
7 min read

A quarterly workflow for reviewing cookies, consent, analytics, enquiry forms, suppliers and privacy wording on solicitor websites.

A law firm website can collect personal data through enquiry forms, cookies, analytics, call tracking and advertising tools, often without the marketing team seeing the full picture. This practical GDPR for law firm websites review workflow helps solicitors identify what is collected, why it is used, who receives it, how consent is recorded and when privacy information needs updating. It is designed for recurring quarterly checks, with additional testing after website, analytics or campaign changes.

Overview

Privacy compliance is not a one-off website project. Scripts are added, analytics platforms change, forms are redesigned and suppliers introduce new processing features. A privacy notice that accurately described the website last year may no longer explain what happens to a prospective client’s information today.

A useful review should connect four elements:

  • What the website collects: including form fields, IP-related information, device data, call records, cookie identifiers and campaign interactions.
  • Why the firm collects it: such as responding to an enquiry, managing a prospective client relationship, measuring website performance or supporting advertising.
  • Who can access or receive it: including hosting providers, form platforms, CRM systems, analytics vendors, call-tracking suppliers and advertising platforms.
  • How the firm manages the data: including lawful basis, retention, security, individual rights and routes for privacy enquiries.

This article is operational guidance, not a substitute for advice on a firm’s particular processing activities. A solicitor’s obligations may depend on the services offered, the information handled, the firm’s role in processing and the suppliers it uses. Firms should obtain appropriate professional advice where the position is unclear and check current guidance from relevant regulators, including the Information Commissioner’s Office where applicable.

What to track

Start with a scan of the live website, then compare the results with the tag manager, content management system, hosting configuration and advertising accounts. Do not rely only on the list supplied by a consent platform. A deployment may contain scripts that were added outside the original cookie configuration.

Item to recordUseful review question
Cookie or script nameWhat is installed, and on which pages does it load?
Provider and purposeWhich organisation supplies it, and what does it do?
CategoryIs it strictly necessary, analytics, preference, advertising or another category used by the firm’s consent tool?
Consent behaviourDoes it load before consent, only after consent, or when an exception applies?
Duration and data flowHow long does it remain, and where is related information sent?
Owner and evidenceWho approved it, and where is the supplier or consent documentation stored?

Pay particular attention to analytics tags, social media pixels, embedded video, maps, chat tools, scheduling software, reCAPTCHA-style services, heatmapping tools and call-tracking numbers. A tool may collect information even when the visitor does not submit an enquiry.

Test the website as a new visitor using a clean browser session. Check whether non-essential cookies and scripts are blocked before consent, whether rejection is as easy to find as acceptance, and whether preferences can later be changed. Record the date, device, browser, page tested and result. Repeat the test on mobile, on the main landing pages and after significant deployments.

Review the consent record itself. The firm should know what was selected, when the choice was made, the relevant notice or banner version and how a withdrawal is handled. A banner that looks correct is not enough if the underlying record cannot be reconciled with the tools that actually load.

3. Map enquiry-form data

List every field on each form, including hidden fields and campaign parameters. For each field, ask whether it is necessary at the first contact stage. A prospective client may need to provide a name and contact route, but a detailed account of sensitive circumstances may not be necessary before conflict checks or an initial triage conversation.

Form elementRecord for the review
Field or data pointWhat is requested, including optional fields?
PurposeWhy does the firm need it at this stage?
Notice shownCan the person see concise privacy information before submitting?
DestinationWhere does the submission go: email, CRM, case-management system or supplier?
Access and retentionWho can view it, and how long is it retained if no client relationship follows?
Risk controlsDoes the form discourage unnecessary confidential or sensitive information?

Also review confirmation pages and automatic emails. They should not expose the full enquiry unnecessarily, and they should tell the person what happens next without promising a response time the firm cannot consistently meet.

4. Review privacy wording and supplier relationships

The solicitor website privacy policy should describe the website’s real activities in plain language. Check its purposes, lawful bases, categories of data, recipients, retention approach, individual rights and privacy contact route. Make sure the wording distinguishes website enquiries from formal client files where the firm’s processing arrangements differ.

Maintain a supplier list covering hosting, form delivery, CRM, analytics, call tracking, email marketing, live chat, advertising and consent management. Confirm the relevant contractual relationship and responsibilities rather than assuming every supplier handles data in the same way. Record any changes that require a privacy notice update, risk assessment or internal approval.

Cadence and checkpoints

A quarterly review is a practical minimum for a firm that actively changes its website or marketing. Use a monthly light-touch check for critical pages and a full review each quarter.

  • Monthly: check the enquiry forms, privacy-policy link, consent controls and key conversion pages; investigate unexpected scripts or supplier alerts.
  • Quarterly: rescan the website, reconcile scripts with the cookie inventory, review form fields and suppliers, test withdrawal of consent, and confirm the privacy contact route works.
  • After every deployment: test affected pages on desktop and mobile, confirm tags behave as intended and record the result before closing the release.
  • When a tool changes: reassess its purpose, data flows, consent category, contract and privacy wording before or promptly after implementation.

Use a remediation log with columns for issue, risk, owner, action, deadline, status, evidence and approval. Give urgent issues a clear escalation route rather than allowing them to remain as general website tasks.

Quarterly sign-off template

Review period: [date to date] | Reviewer: [name] | Approver: [name]

  1. Website and script scan completed: [yes/no]
  2. Cookie inventory reconciled with installed tags: [yes/no]
  3. Consent acceptance, rejection and withdrawal tested: [yes/no]
  4. Enquiry forms and hidden fields reviewed: [yes/no]
  5. Privacy notice and contact route checked: [yes/no]
  6. Supplier and processor list reviewed: [yes/no]
  7. Open actions, owners and deadlines recorded: [link or reference]
  8. Next scheduled review: [date]

How to interpret changes

A change in website activity is not automatically a compliance failure, but it is a reason to ask what has changed and whether the existing controls still match it. A new advertising pixel may alter consent requirements. A redesigned form may collect more information than before. A drop in recorded analytics may reflect a consent configuration change rather than lower demand.

Separate technical symptoms from legal and operational questions:

  • If a script appears before consent, pause or correct its deployment while the issue is assessed.
  • If a supplier has been added without appearing in the privacy notice or supplier register, document the data flow and obtain appropriate review.
  • If forms collect detailed case narratives, consider whether the fields are necessary and whether visitors are being directed to send information through a suitable channel.
  • If consent records do not match the banner or tag behaviour, preserve evidence, identify affected dates and prioritise remediation.
  • If enquiry volume changes after a consent update, compare compliant measurement with other indicators such as call records and qualified enquiries rather than treating raw analytics as a complete picture.

Keep evidence of tests, screenshots, scan reports, approvals and completed fixes. This makes the next review faster and helps the firm explain how it manages recurring website risks.

When to revisit

Revisit this workflow quarterly and whenever recurring data points change. Trigger an additional review after a website redesign, new landing page, analytics migration, advertising campaign, CRM integration, call-tracking change, consent-platform update or change to the firm’s enquiry process. Also review promptly if a supplier changes its terms or functionality, a visitor raises a privacy concern, or a test shows that a setting is not working as expected.

At the end of each review, schedule the next date rather than leaving it as an informal reminder. Assign one operational owner, one person able to approve privacy changes and a route for obtaining specialist advice. For related measurement and lead-quality work, see the solicitor website analytics guide, the law firm website conversion audit and the lead-source attribution template. A short, evidenced review repeated consistently is more useful than a detailed policy that no one checks against the live website.

Related Topics

#GDPR#Cookie Consent#Privacy#Enquiry Forms#Compliance Reviews
S

Solicitor.live Editorial Team

Legal Marketing and Compliance Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.