Cookie policy

Cookies are small text files a website stores in your browser. Similar technologies include your browser's local storage and session storage, and "pixels": small scripts that tell an analytics or ad platform that a page was viewed or a form was sent. In this policy "cookies" covers all of them.

This policy is part of our privacy policy, which explains how we use the data these tools collect.

• Cookie settings: the link in the footer of every page opens our cookie banner, where you can accept or decline analytics and advertising cookies. Your choice is saved in your browser.
• EU, EEA, UK and Switzerland: if your browser's time zone is in one of these regions, Google's analytics and advertising storage starts as denied and the Meta pixel stays off until you click Accept.
• Everywhere else: these tools are on by default, and you can decline them with Cookie settings.
• Your browser: you can block or delete cookies in your browser settings. Google offers an opt-out add-on for Google Analytics, and you can manage ad personalisation in your Google and Meta settings.

Declining does not stop the site from working. It does mean we can't tell which of our ads brought you here.

Set by gethelium.co. They don't need consent, and they never leave your browser except as noted.

• helium_consent (local storage, until you clear it): your cookie banner choice
• helium_market (cookie and local storage, 1 year): whether you see Indian (₹, WhatsApp) or international ($/£, booking) prices and contact options
• helium_touch (session storage, this visit) and helium_first_touch (local storage, until you clear it): the page, referrer and campaign tags of this visit and of your first visit. They are attached to a form only when you submit one, so we know which channel brought you
• helium_ad_lead (session storage, this visit): stops a single enquiry being counted twice by our ad platforms

• PostHog (ph_<project>_posthog cookie, about 1 year): an anonymous ID and session details, so we can count visits and see which pages and forms work. We use PostHog for all visitors as basic site measurement, including session recordings and heatmaps; text typed into forms is masked.
• Google Analytics 4 (_ga and _ga_<id> cookies, up to 2 years): counts visits, pages and enquiries across visits. Runs only with consent where consent is required.

These run only with consent where consent is required, and you can decline them anywhere with Cookie settings.

• Google Ads (_gcl_au, and _gcl_aw after an ad click, about 90 days): tells Google Ads which ad clicks led to an enquiry, and lets us show ads to past visitors
• Meta pixel (_fbp, and _fbc after an ad click, about 90 days): tells Meta which Facebook and Instagram ads led to an enquiry or a booked call, and lets us build ad audiences

The tools above are loaded only after you interact with the page or it finishes loading, and not at all if we haven't switched them on.

When you open the booking calendar on gethelium.co, Cal.com or Calendly may set their own cookies to run the calendar. YouTube or other embedded media may do the same when you play them. These are controlled by those companies under their own policies.

Our Shopify app, Helium AI: Analytics & CRO, runs on merchants' stores, not on gethelium.co. It uses a client ID cookie and Shopify's web pixel to understand browsing on that store. The merchant is responsible for telling their shoppers about it and collecting consent where required, through their own cookie banner and Shopify's customer privacy settings. The app's web pixel is registered with Shopify's customer privacy settings, so it only runs when the shopper has given the analytics and marketing consent Shopify asks for.

We update this list when we add or remove a tool. The date at the top shows the last change. Questions: hello@gethelium.co.