Cookie Policy
Last updated: September 2026
This Cookie Policy explains what cookies and similar technologies are used on the Clear Fire Compliance website (clearfirecompliance.co.uk), what they do, and how you can control them. It should be read alongside our Privacy Policy.
1. What cookies are
A cookie is a small text file that a website places on your device when you visit. Cookies let a site remember things about your visit — for example, whether you have already seen a notice — and they can also be used to measure how the site is being used.
This policy also covers ‘similar technologies’ such as local storage, session storage, and web beacons, which do broadly the same job as cookies but store information in slightly different ways.
2. How we categorise the cookies on this site
Under the Privacy and Electronic Communications Regulations 2003 (PECR) and the UK GDPR, we must get your consent before storing or reading anything on your device, unless an exception applies. Two exceptions matter here: things that are strictly necessary for the site to work, and statistics collected only to see how the site is used so we can improve it — which the law allows without consent, provided we tell you about it and give you a simple, free way to switch it off. We group cookies and similar technologies into three categories:
- Strictly necessary — required for the website to work and for security. Always on.
- Statistics — anonymous counts of how the site is used, so we can improve it. On unless you switch it off.
- Advertising — lets advertising platforms show our ads to people who have visited, and measure which ads led to a booking. Off unless you switch it on.
3. The cookies used on this site
Our website is a static site built with Astro and hosted on Vercel. It is deliberately lightweight and sets very few cookies. The tables below describe what you may encounter.
3.1 Strictly necessary (always active)
| Cookie / identifier | Set by | Purpose | Duration |
|---|---|---|---|
| cfc-consent | Clear Fire Compliance | Stores your choices for Statistics and Advertising so we don’t ask again on every page | 12 months |
| cfc_admin | Clear Fire Compliance | Keeps the site owner signed in to the admin area | 7 days |
| cfc-book-prefill, cfc-quote-prefill, cfc-pack-addon, cfc-check-handoff (session storage) | Clear Fire Compliance | Carries the answers you gave in the calculator or licence check into the booking or quote form | Until you close the tab |
| cfc_attr (session storage) | Clear Fire Compliance | Remembers how you reached the site for this visit, including an ad click reference if you arrived from an ad | Until you close the tab |
3.2 Statistics (on unless you switch it off)
We keep anonymous statistics about how the site is used — which pages are read, where visitors arrive from, which steps of our price calculator, licence check and booking form they reach, and which contact links they tap — so we can see which pages help and fix the ones that don’t. We rely on the statistics exception in PECR for this, so it runs without asking first; you can switch it off at any time with the Statistics switch under “Cookie settings” at the bottom of every page.
- First-seen month. One value in your browser’s local storage, the month of your first visit (for example “2026-09”), so we can count new and returning visitors. It holds nothing else, is never linked to a booking, enquiry or contact, and is removed when you switch Statistics off.
- Our own event counts. Each page sends a short record of what happened on it — the page, the site that referred you, your device type and browser family, and the steps and options chosen (never anything you type) — to our own server on Vercel. To group the pages of one visit, the server makes a key from your IP address and browser details with a secret that changes every day; the IP address and browser details are never stored, and each day’s secret is deleted at 03:00 the next morning, after which the key cannot be rebuilt by anyone, including us. With Statistics switched off, pages are still counted, but with no key and no first-seen month.
- Vercel Web Analytics counts page views. It sets no cookies, stores nothing on your device and does not identify you.
| Cookie / storage | Set by | Purpose | Duration |
|---|---|---|---|
cfc-first-seen (local storage) | Clear Fire Compliance | The month of your first visit, for new and returning visitor counts | Until you clear it or switch Statistics off |
cfc-internal | Clear Fire Compliance | Set only when the site owner turns it on for their own device; keeps their visits out of the statistics | 400 days |
3.3 Advertising (off unless you switch it on)
If you choose “Allow” in our cookie banner, or switch Advertising on in “Cookie settings”, we use Google Analytics, the Google Ads tag and the Meta Pixel. They let Google and Meta show our ads to people who have already visited the site, and tell us which ads led to a booking. None of these cookies are set until you allow them, and switching Advertising off removes them.
| Cookie | Set by | Purpose | Duration |
|---|---|---|---|
_ga | Google Analytics | Distinguishes one visitor from another | 13 months |
_ga_E0L51T2J5B | Google Analytics | Remembers the current visit (session) | 13 months |
_gcl_au | Google Ads | Links a visit to the Google ad that brought you here | 90 days |
_gcl_aw | Google Ads | Stores the click reference from a Google ad you arrived by | 90 days |
_gcl_gs | Google Ads | Stores the click reference from a Google ad you arrived by | 90 days |
_fbp | Meta | Links a visit to Meta’s advertising | 90 days |
_fbc | Meta | Stores the click reference from a Meta ad you arrived by | 90 days |
cfc-booked-<ref> (session storage) | Clear Fire Compliance | Stops Google Analytics counting the same booking twice if the confirmation page is reloaded | Until you close the tab |
If you don’t allow advertising, none of these are set. The site then sends Google Analytics only anonymous, cookieless signals that a page was viewed, which cannot identify you or your device (“consent mode”). When you book or send an enquiry, our server also records that it happened, with no name or contact details, in Google Analytics.
4. Third-party content and the enquiry form
Our enquiry form submits to a function on our hosting platform (Vercel) and does not require a third-party cookie to work. If we later embed third-party content that sets its own cookies — for example, an external video player for the trust-builder intro video — it will only load after you consent, and it will be listed here.
5. Managing your cookie choices
5.1 Using our cookie banner
When you first visit the site you will see a cookie banner. “Allow” turns Advertising on and “Decline” leaves it off; “Choose settings” lets you switch Statistics and Advertising on or off separately. You can revisit your choices at any time by clicking the ‘Cookie settings’ link in the website footer.
5.2 Controlling cookies in your browser
Most web browsers allow you to block cookies, delete existing cookies, or be notified when a cookie is set. How you do this depends on your browser:
- Google Chrome: support.google.com/chrome
- Mozilla Firefox: support.mozilla.org
- Apple Safari: support.apple.com
- Microsoft Edge: support.microsoft.com
If you block all cookies, some parts of the site may not work as expected. If you block only non-essential cookies, the site will continue to work normally.
6. ‘Do Not Track’ signals
Some browsers offer a ‘Do Not Track’ setting. There is currently no agreed standard for how websites should respond to it. We respect your choices through our cookie banner, which is the most reliable way to manage how cookies are used on this site.
7. Changes to this policy
We may update this Cookie Policy to reflect changes in the cookies we use or changes in the law. When we do, we will update the ‘Last updated’ date at the top of this page.
8. Questions
If you have any questions about this Cookie Policy or how we use cookies, please contact us at office@clearfirecompliance.co.uk.
This Cookie Policy has been prepared to meet the requirements of the Privacy and Electronic Communications Regulations 2003 (PECR) as amended, and the UK GDPR. It should be read alongside our Privacy Policy.