Airbrix Bespoke
Home  /  Cookie Policy

Cookie Policy.

We use as few cookies as possible. Here are the ones we do use, what each one does, and how to change your mind.

Last updated 27 May 2026.

What a cookie is, briefly

A small text file your browser keeps on your device when you visit a site. It lets the site remember things between page loads — your preferences, whether you're logged in, or that you've already seen the cookie banner.

The cookies we set

Strictly necessary

These cookies keep the site working. We cannot do without them.

  • PHPSESSID — keeps your enquiry form filled in if you navigate away and back. Expires when you close your browser.
  • cc_cookie — remembers which cookie categories you've accepted so we don't ask again. Lasts six months.

Analytics (optional)

Only set if you accept the optional category in our banner. These help us understand which collection pages are most popular and where visitors get stuck.

  • _abv_pv — aggregated, anonymised page-view counter. Lasts 13 months.
  • _abv_ses — session counter for de-duplicating page views. Expires after 30 minutes of inactivity.

What we do not use

No advertising cookies. No third-party retargeting pixels. No Facebook Pixel, no Google Ads conversion tags, no LinkedIn Insight tag. We have never run paid digital advertising and we don't plan to.

Changing your mind

At any time, click "Cookie preferences" in the footer of any page. The same banner you saw on first visit will reopen and you can change your category choices. The change takes effect on the next page load.

Browser-level controls

You can also block cookies entirely at the browser level. Chrome, Safari, Firefox and Edge all expose a cookie-blocking setting in their preferences. Note that if you block strictly necessary cookies the contact form will lose its in-progress text if you navigate away.

Third-party fonts

We load typefaces from Google Fonts (Mulish and Marcellus). Google may log the IP address that requests the font file. We have minimised this by preconnecting once and caching aggressively, but there is no way to fully eliminate the request without self-hosting the fonts. If you'd rather we self-hosted, write to us — we're considering the change.