Cookies policy for Birmingham Airport

This is the cookies policy for birminghamairport-info.co.uk, in force from the date in the footer above. It sits alongside the privacy policy, which covers the wider data picture, and the legal notice, which covers the rest of the terms. All three are linked from the footer of every page.

Four cookies, from two sources, plus a clear statement of what is not here.

Google Analytics: two first-party cookies

The site uses Google Analytics 4 to count visits and see which pages are used. It is configured for measurement only: IP addresses are anonymised, and Google's advertising features and cross-site signals are switched off, so it sets no advertising cookies. It does set two first-party analytics cookies:

Cloudflare: two strictly-necessary cookies

The site is served through Cloudflare, so every request passes through its security layer, which sets a small number of strictly-necessary cookies to keep the site safe from automated abuse:

Both Cloudflare cookies are first-party, encrypted, and carry no profiling or marketing data. The __cf_bm cookie is the only one most visitors will see; cf_clearance appears only if a challenge has been issued.

Advertising and social trackers: none

The site sets no advertising cookies and embeds no third-party trackers. There is no Google Ads or DoubleClick tag, no Facebook Pixel, no X (Twitter), LinkedIn, TikTok or Pinterest tracking, no marketing-automation tag, and no social-share widget or embedded video player that loads a tracking script. If an embed is ever added that changes this, the policy is updated in the same change.

UK cookie rules sit under Regulation 6 of the Privacy and Electronic Communications Regulations 2003 (PECR), as amended by the Data (Use and Access) Act 2025, which came into force on 5 February 2026 and added a set of exemptions including "strictly necessary" and "statistical purposes". The Information Commissioner's Office finalised its guidance on storage and access technologies on 29 April 2026.

Applied to this site: the Cloudflare __cf_bm and cf_clearance cookies fall under the strictly necessary exemption, because the site cannot be served safely without bot protection at the network layer. The Google Analytics _ga cookies are not strictly necessary; the site relies on the statistical purposes basis for them, because the analytics here is first-party, aggregate, IP-anonymised measurement used only to improve the site, with advertising features off. In keeping with that basis, the site gives you clear information here and an easy way to opt out, set out below, rather than a pop-up. If you would rather not be counted at all, the opt-out takes effect straight away.

You have two direct ways to switch off the analytics. The Google Analytics Opt-out Browser Add-on stops Google Analytics on every site you visit. Blocking or deleting cookies in your browser removes the _ga cookies and stops GA4 recognising a return visit; many browsers and privacy extensions also block analytics scripts outright. Either way, the site itself loads and works exactly the same.

Blocking the Cloudflare cookies is possible too, but they are there to serve the site safely, so the main effect is that you may see a Cloudflare verification step on some visits before the page loads. The major browsers publish their own cookie controls:

• Google Chrome cookie controls
• Apple Safari cookie controls
• Mozilla Firefox cookie controls
• Microsoft Edge cookie controls

For a question about any cookie described here, use the route on the contact page.

The date at the foot of this page is the effective date of the current version. The policy is updated whenever the cookies the site actually sets change, or whenever the UK legal position moves. The post-DUAA rules are recent and the ICO has signalled further guidance, so this page tracks them alongside the privacy policy.