Cookie Policy

3.1 Necessary and functional cookies

• cookie_consent (first-party) – stores your cookie preferences (for example, whether analytics and marketing cookies are allowed). This cookie is used by our consent system and analytics/marketing tools to decide which technologies may run. It is categorised as necessary/functional. It is usually stored for up to 365 days when you accept or customise cookies, and for a shorter period (for example 7 days) when you reject non-essential cookies.
• sidebar_state (first-party) – remembers whether certain interface elements (such as sidebars on internal/admin screens) are collapsed or expanded. This is a purely functional preference cookie, typically kept for up to 7 days.
• Authentication and security cookies – where applicable, we may use secure cookies provided by our authentication and infrastructure providers to keep you logged in, maintain security, and prevent fraud. These are necessary for the service to operate.

3.2 Analytics cookies and identifiers

• ga_cid (first-party cookie and local storage) – a pseudonymous "client ID" which allows us to understand returning visits to the website. It is used with Google Analytics 4, which we run via our own server-side endpoint instead of loading Google's tracking scripts on every page. This identifier may also be used as a stable pseudonymous identifier for marketing measurement where permitted. Category: analytics (and, where used for campaign measurement, also marketing). Typical duration: up to 12 months.
• cl_sid (first-party session cookie) – a short-lived session cookie that stores a session identifier and session count so we can understand how visits to the website are grouped into sessions. Category: analytics. Typical duration: around 30 minutes from your last activity.
• Local storage keys (cl_session_meta, cl_session_count) – used to maintain metadata about your sessions (such as how many sessions have occurred from a particular browser). Category: analytics.

3.3 Meta (Facebook) Conversions API

We use the Meta Conversions API ("Meta CAPI") to send certain events to Meta, such as when you view quotes, start checkout, or complete a booking. This integration is server-side only – we do not load the Meta pixel in your browser.

Meta CAPI uses the cookie_consent value from your browser to decide whether events are allowed. If there is no consent cookie, our system may treat this as implied consent. If you have explicitly set both analytics and marketing preferences to "off", these events are not sent.

When allowed, Meta CAPI may receive hashed versions of your email address and phone number, your IP address and user agent, and the ga_cid client ID as a pseudonymous external identifier. Category: marketing and measurement, controlled by your cookie preferences.

3.4 Google Analytics and Google Ads

We use Google Analytics 4 ("GA4") to understand how visitors use the Compare Locals website and platform. GA4 events are sent from our servers using the GA4 Measurement Protocol, and use identifiers such as the ga_cid client ID and short-lived session identifiers.

We may also use Google Ads and related tools to run and measure advertising campaigns that lead people to Compare Locals. Where we do so, Google may use analytics data or similar identifiers to measure ad performance and prevent fraud. Any additional Google Ads tags or cookies we introduce will be categorised as marketing cookies and will be controlled by your cookie preferences.

3.5 Intercom chat and support

We use the Intercom Messenger to provide in-app support and, where appropriate, product guidance. Intercom may store cookies and/or local storage identifiers to remember you between visits, show chat history, and provide support context.

These technologies are primarily functional and analytics-related, and may also support customer engagement and product communication.