Cookie policy

The Privacy and Electronic Communications Regulations require a website to tell you what it stores on your device and, for anything beyond the strictly necessary, to get your permission first. This page is that disclosure for this site.

It runs alongside the privacy policy rather than repeating it. This document deals with what sits in your browser; that one deals with what happens to an enquiry after you send it.

A cookie is a small text file that a website asks your browser to keep and hand back on the next request. It is how a shop remembers a basket between pages, and how an analytics tool works out that two page views came from the same visit rather than two different people.

The label has stretched to cover other storage that behaves the same way: local storage, session storage, and identifiers held in a browser database. Where this policy says cookie, it means all of them.

Nothing. No cookie is written by this website, first party or third party. There is no consent banner on these pages because there is nothing to ask you about, and a banner that asked permission for cookies that do not exist would be theatre.

You can check rather than believe it. Open the storage panel in your browser’s developer tools on any page here, reload, and the cookie list for this domain stays empty.

Every page on this site is generated during the build and served as a static file. There is no session to keep, no login to remember, no basket to hold, and no personalisation that would need to know you have been here before.

A quote form is the one place a conventional site would reach for storage. This site has none: the quote buttons are links that open WhatsApp with the message already written, so there is nothing to store and nothing to recover on a reload.

Your browser caches images, stylesheets and fonts so pages after the first one load faster. That cache is your browser’s housekeeping, not a cookie, it carries no identifier, and it is cleared with the ordinary clear-cache control.

Your device also remembers its own settings: text size, reduced motion, forced colours, and any address or phone number saved in autofill. None of that is visible to us, and with no form on the site there is nothing here for it to fill in.

The three typefaces this site uses are downloaded at build time and served from the same domain as the pages, so your browser makes no request to a font provider and no third party learns that you opened this page. That is a deliberate choice; the default arrangement would have leaked a request to a font CDN on every visit.

Photography, icons and the stylesheet come from the same place. As you read this page, no request is going anywhere except to this site, which is the reason the cookie list above is short.

Three kinds of link leave this site. The WhatsApp buttons open wa.me, which is Meta’s domain and sets Meta’s cookies under Meta’s policy. The telephone links hand a number to your dialler. The email links hand a message to your mail application.

None of those requests happens until you press the link. Reading a page here, however far you scroll, tells WhatsApp nothing.

Analytics on this site is controlled by two identifiers held in one configuration file. While they are empty the tags are not written into the HTML, which is why the page is clean rather than merely quiet.

Enabling them would mean three things happening together: the tags loading only after consent has been given, this page being updated to name each cookie and its lifetime, and a way to change your mind appearing on every page. Analytics arriving without those three would be a defect, not a decision.

Every current browser lets you see what a site has stored, delete it, and block future storage per site or across the board.

• Chrome — Settings, Privacy and security, Third-party cookies, then Site settings for a single domain.
• Safari on macOS — Safari, Settings, Privacy, then Manage Website Data.
• Safari on iOS and iPadOS — Settings, Apps, Safari, then Clear History and Website Data.
• Edge — Settings, Cookies and site permissions, then Manage and delete cookies and site data.
• Firefox — Settings, Privacy and Security, then Cookies and Site Data.
• Any of them — a private or incognito window discards everything a site stored the moment you close the last window of that session.

Some people run a browser with storage blocked outright, or with an extension that strips trackers. Neither breaks this site. Every page renders, every table works, every link resolves, and the quote buttons open WhatsApp exactly the same way.

That is worth saying because it is unusual. Most sites degrade badly with cookies off; this one has nothing to lose.

Browsers can send a Do Not Track header or a Global Privacy Control signal announcing that you object to tracking. There is no tracking here to apply them to, so they change nothing about what this site does.

They are not ignored on principle. If measurement is ever added, a Global Privacy Control signal will be treated as a refusal of consent, without a banner needing to be dismissed first.

This page changes when what the site stores changes, and the effective date at the top moves with it. Because the text is generated from the same configuration that switches the tags on, the document cannot quietly fall out of step with the site.

A material change, such as measurement being introduced, is not something we would expect you to spot for yourself. Consent would be asked for before any new tag was loaded.

Questions go to info@firstclass-chauffeurs.co.uk. If you have found something in your browser you think this site put there, send us the cookie name and the page you were on, and we will either explain it or remove it.

A complaint about cookies is also a data protection complaint, and the route to the Information Commissioner’s Office is set out at the end of the privacy policy.