Cookie Policy

Last updated: 12 June 2026

This Cookie Policy explains how imperial.events handles tracking on your visit. We default to cookieless, anonymous analytics — no cookies and no stored identifiers — and only set persistent cookies if you accept them. This policy describes both modes, every cookie we may set, and how to control them.

Our default: cookieless anonymous analytics

By default, before you make any choice in the cookie banner, we count anonymous page visits using cookieless analytics. We do this to know which experiences land, where visitors come in, and where the site needs work.

In this default mode:

No cookies are set.
No localStorage, sessionStorage, or IndexedDB entries are written.
No identifier is stored on your device.
Each pageview is sent to PostHog (our EU-hosted analytics provider) as a fresh anonymous event with no way to link it to your previous visits or to you personally.

The same applies to enquiry attribution. We note which channel a visit arrived from (a Google search, an email link) so that an enquiry sent later can be credited to it. Before you make a choice in the banner, nothing is stored on your device: the channel note is kept briefly on our servers against a temporary reference that disappears when you close or reload the page. If you decline, we stop recording it entirely.

We rely on this under the legitimate-interest legal basis (UK GDPR Article 6(1)(f); EU GDPR equivalent). You can object at any time by clicking Decline in the cookie banner or Reject all in the Cookie Preferences panel in our footer, which switches analytics off completely.

We also respect the Do Not Track browser signal. If your browser sends DNT, no analytics events are sent regardless of your cookie choice.

What are cookies?

Cookies are small text files stored on your device when you visit a website. They let the site remember your preferences and stitch repeat visits together. Some cookies are essential for the site to work; others are optional and only set after you consent.

What we use cookies for

When you click Accept in the cookie banner or turn Analytics on in Cookie Preferences, we set cookies for these purposes:

Remembering your cookie preference. When you accept or decline analytics, we save that decision so we do not ask again on every visit.
Persistent analytics. A randomly generated anonymous identifier so we can stitch pageviews from the same browser together. This lets us measure return visits, attribution, funnels, and run product experiments. It does not contain your name, email, IP address, or any data that could identify you personally.
Session recording. An anonymised replay of how you interact with the page — mouse movements, scrolls, clicks. Every form field, text input, and editable region is masked before the recording leaves your browser. We use this to spot UX issues we cannot see from analytics alone.
Enquiry attribution. A randomly generated identifier (ice_attr_sid) that links an enquiry you send, even weeks later, to the marketing channel that first brought you here and the one that brought you back. The channel history itself lives on our servers; only the identifier is stored on your device.
Sales follow-up and advertising measurement. Accepting also loads HubSpot, the system our sales team works in. HubSpot sets its own cookies to connect your enquiry to your visit, and loads a Google Ads measurement tag that sets cookies so we can tell which of our own adverts lead to enquiries.

We do not sell or share your data with advertisers, and we do not use cross-site tracking pixels. The only advertising-related cookies on this site are the Google Ads measurement cookies described above; they measure our own campaigns, nothing else, and are set only after you accept.

Cookies we set

The list below covers every cookie imperial.events sets directly. Third-party cookies set by PostHog (our analytics provider) are listed in the next section.

Strictly necessary

These cookies are required for the site to work. They are set whether or not you accept analytics and cannot be disabled.

consent — 1 year — Records whether you accepted or declined analytics cookies. Without this cookie we would have to show the consent banner on every page load.

Analytics (set only after you accept)

These cookies are only set after you accept analytics in the cookie banner or in the Cookie Preferences panel. If you later decline, we delete them and stop reading anything that remains.

ph_*_posthog — 1 year — Set by PostHog. Holds a randomly generated anonymous identifier so we can stitch together pageviews from the same browser session. It does not contain your name, email, IP address, or any data that could identify you personally.
ice_attr_sid — 2 years — Set by us. A randomly generated identifier linking your enquiry to the marketing channels that brought you here. The channel details live on our servers; only the identifier sits on your device.
hubspotutk, __hstc, __hssc, __hssrc — 6 months or less — Set by HubSpot, our sales system, to connect your enquiry to your visits so the team has context when they pick up the phone.
_gcl_au and other _gcl_* cookies — 3 months — Set by Google Ads via HubSpot. They measure which of our adverts lead to enquiries.

Managing your cookies

You have three ways to control cookies on imperial.events:

The Cookie Preferences panel. Open it from the footer. You can flip Analytics on or off at any time; your choice is saved immediately.
The consent banner. First-time visitors see a banner in the bottom-right of the screen. Accept turns persistent analytics on; Decline switches all analytics off.
Your browser settings. Every modern browser lets you block or delete cookies for a specific site. Doing so will not break imperial.events, though you may see the consent banner again on your next visit.

We also respect the Do Not Track browser signal. If your browser sends DNT, we will not load analytics even if you previously accepted.

Third-party services

We use one third-party service for analytics: PostHog, a privacy-focused analytics platform hosted in the European Union. PostHog's own cookie and privacy documentation is at posthog.com/privacy.

We do not use Google Analytics, Facebook Pixel, Hotjar, LinkedIn Insight, or any cross-site advertising network. Two further services run only after you accept: HubSpot, which our sales team uses to attribute enquiries to their original referrer, and a Google Ads measurement tag loaded by HubSpot that measures our own ad campaigns and nothing else.

Server-side data

Some of our integrations (HubSpot for sales enquiries, Resend for transactional email, Supabase for our database) run on our servers and do not set cookies in your browser. They process data you submit through forms in line with our Privacy Policy.

Changes to this policy

We may update this Cookie Policy if we add or remove a tool that uses cookies. The "Last updated" date at the top tells you when the policy last changed.

Contact

Questions about cookies on imperial.events? Email info@imperial.events or write to:

Imperial Corporate Events Ltd, Mercury Place, 11 St. George St., Leicester, Leicestershire, LE1 1QG.