Necessary enquiry and work-order functionality
The bcpweb_session cookie supports the enquiry form’s security checks, validation messages and submission confirmation. It also supports business work-order email verification, signing and access to the signed receipt in the session used to sign. The secure credential page uses it for its security check and submission confirmation. Its protected administration area uses the session for short-lived email-code login, with a 20-minute inactivity limit and a one-hour maximum authenticated session. The cookie contains a random session identifier, never submitted passwords. It is used on the relevant form and private pages and is a session cookie, normally removed when your browser session ends.
Blocking this cookie can prevent the form from working. You can still contact Tom by email or telephone, and you do not need to accept analytics to submit an enquiry.
Enquiry-form security check
Cloudflare Turnstile checks enquiry submissions for automated spam. It processes technical browser and connection signals for website security and is separate from visit measurement and interaction recordings. Refusing optional analytics does not disable this check.
This site does not enable Turnstile pre-clearance, which would issue a Cloudflare clearance cookie. The security check requires JavaScript; if it cannot run, you can contact Tom by email, telephone or live chat instead.
Necessary chat functionality
The bcpweb_chat_guest cookie is created only when you open chat. It identifies your conversation on this browser and supports chat security checks. It lasts up to 30 days, allowing you to reopen the same conversation. The cookie does not contain your name, business or message text.
Chat does not save visitor messages in browser local or session storage. Blocking or removing the chat cookie can prevent chat from working or stop this browser reopening an earlier conversation. You can still contact Tom using the enquiry form, email or telephone. Chat works without optional analytics consent and does not ask visitors for push-notification permission.
Private inbox login and notifications
The private inbox uses bcpweb_chat_owner to keep Tom signed in for up to 30 days. It also uses bcpweb_chat_login for login security checks, with a lifetime of up to one hour. These cookies are used for the private inbox, not to track public website visits. Signing out removes the owner login cookie.
Tom can install the inbox as a web app and allow notifications on his own devices. This registers a service worker and a browser push subscription; the subscription is stored in the encrypted private chat records. Alerts contain a generic waiting-message notice and a link to the private inbox, without visitors’ names, business details or message text. Visitors are not prompted to register for notifications. The private inbox does not load Google Analytics or Contentsquare.
Your optional choices
Visit measurement uses Google Analytics 4 when it is configured. Interaction recordings use Contentsquare when it is configured. Each category is optional: you can allow either, allow both or refuse both. No requests to either provider are made before a choice permits that provider to load.
Your preferences are remembered for up to 180 days in browser local storage named bcpweb_privacy_v2. The stored choice includes a record of the provider setup so the site can ask again if that setup changes. If storage is blocked, optional tools stay off until you choose for the current page.
You can change the choices using Privacy choices in the footer of public pages where measurement is available. Refusing optional tools leaves the site, enquiry form and chat working. Search, error and private routes do not load these measurement integrations.
Visit measurement: Google Analytics
When allowed and configured, Google Analytics measures page views, audit-link engagement, email, telephone and WhatsApp clicks, chat openings, accepted new chats and accepted form enquiries. The form-enquiry event follows successful storage of the submission and can identify the selected service and known source page. Chat events identify only the known website page and the action taken. A click or enquiry does not establish that a meeting happened or work was purchased.
Google Analytics may set _ga and property-specific _ga cookies. This site requests a 180-day cookie lifetime and disables Google signals and advertising personalisation. Withdrawing permission stops further events from this implementation and attempts to remove its first-party analytics cookies.
The page address excludes arbitrary URL parameters and search terms. It retains only recognised website paths, service and source markers, and restricted campaign source, medium, campaign and content labels. The referring website is recorded only as its origin, without a page path or query string.
Interaction recordings: Contentsquare
When allowed and configured, Contentsquare collects pseudonymous visit, device and interaction information to produce heatmaps and session replays. Replays reconstruct activity within this website, such as navigation, clicks and scrolling, to help identify problems with the journey.
The site masks form fields and their contents, the entire chat panel and its messages, tokens, validation echoes, enquiry references and marked personal-information areas. It does not deliberately send enquiry names, business names, email addresses, messages or reference numbers to either measurement provider.
Contentsquare can use first-party cookies such as _cs_id, _cs_s and _cs_c for visitor, session and consent information, and _cs_optout to record refusal. Cookie and storage durations are defined by the provider; its current cookie documentation explains each item. The site supplies a restricted page path and allowlisted labels, and removes query strings from referrer information.
Withdrawing permission tells Contentsquare to stop collection and attempts to remove its first-party measurement cookies. If you allow it again after stopping it on the current page, recording may resume when you next navigate to a page. Your enquiry form is not reloaded to apply that choice.
Campaign information during your visit
After you allow either optional category, browser session storage named bcpweb_campaign_v1 can remember your landing page and restricted campaign labels: utm_source, utm_medium, utm_campaign and utm_content. Labels must be short and use only letters, numbers, underscores or hyphens. This storage is cleared if you refuse both categories and normally ends with the browser session.
If you submit the enquiry form while an optional category is allowed, these labels and the landing page can be stored with the encrypted form enquiry and included in its notification email. This connects promotion sources with actual enquiries. Refusing both categories leaves this campaign attribution out of the form enquiry. The chat conversation record does not store these campaign labels.
Managing your browser
Your browser can block or remove cookies and local storage. Removing your stored choice may show the analytics question again where analytics is configured. Blocking necessary cookies may prevent the enquiry form, chat or private inbox from working.
The privacy notice explains how enquiry details and other personal information are used.