Cookie Notice

This notice lists the cookies, browser storage and scripts used on www.activeset.co, what each one does and when it runs. It describes how the site works today (checked 3 November 2026).

Where the law requires consent (if you visit from the EU, the EEA, the UK or Switzerland), nothing that measures or identifies you runs until you click Accept in the cookie banner. If you make no choice, only the items under “Always on” load. If you click Reject, the items under “Always on” load, and Ploy counts your page views in its cookieless mode (see Ploy below), without identifying you. Everywhere else, the analytics and marketing tools below run by default, and you can switch them off at any time by choosing Reject in Cookie settings.

You can change your choice at any time: click Cookie settings in the site footer.

Always on

Your cookie choice. We keep Accept or Reject in your browser's local storage under the key as-consent-v1, so the banner doesn't ask again on every page. It is not a cookie and is not sent to us or anyone else. Webflow also stores a few local storage keys that start with intellimize_ (such as intellimize_opt_out_…). They tell Webflow Analyze not to track you until you click Accept, and hold no visitor ID.

Your country. Our network provider, Cloudflare, sets a first-party cookie, as_geo, holding the two-letter code of the country you are visiting from, for one day. The site uses it only to decide whether to ask for your consent first. It holds no visitor ID.

Website delivery. Pages, images, fonts and code load from Webflow's servers (cdn.prod.website-files.com and d3e54v103j8qbb.cloudfront.net) and from an open-source code library (cdn.jsdelivr.net). Like any web request, these send your IP address and browser details to the server that answers. They set no tracking cookies.

Where an enquiry came from. When you arrive, we note the page you landed on, the site that referred you and any campaign tags in the link (utm_). If you follow a link to our contact page, we also note which link it was. These are kept in your browser under the keys as_first_touch and as_lead_ctx: in session storage, which clears when you close the tab, or in local storage once you click Accept. If you send one of our forms, these values are sent with it so we know which page or link the enquiry came from. They hold no name or contact details and are not shared with anyone. Analytics tools only receive them after you click Accept.

Analytics and marketing tools

Google Tag Manager and Google Analytics 4 (Google). Tag Manager loads the tools below; Google Analytics counts page views and shows how the site is used. Google Analytics sets the first-party cookies _ga and _ga_YFZJE7EN53.

Microsoft Clarity (Microsoft), loaded through Tag Manager. Records clicks, scrolling and session replays so we can see where pages are unclear. Sets cookies such as _clck and _clsk.

Factors.ai. Shows which companies visit the site, based on visit data such as your IP address. Sets the first-party cookie _fuid.

Vector, loaded through Tag Manager. Shows which companies, and in some cases which people, visit the site. Its code includes identity matching from LiveIntent and sets cookies such as _lc2_fpi and _li_ss.

Webflow Analyze (Webflow). Webflow's built-in analytics for page views and clicks. It keeps a visitor ID in local storage under keys that start with intellimize_.

Ploy (Ploy). Usage analytics: page views, visits, scroll depth, link and button clicks, form interactions and site searches, so we can see which pages and campaigns lead to enquiries. With your consent, it keeps a visitor ID in a first-party cookie and in local storage under ploy_anon_id, and a visit record in local storage under ploy_session. If you click Reject, Ploy still counts these events, but in a cookieless mode: it keeps no visitor ID on your device, only a cookie named ploy_consent (value “denied”, 180 days) that records your choice. Your visits are grouped by an anonymous ID that resets every day, so visits on different days are not linked, and no company or person identification runs. Ploy says it does not store your IP address in this mode. Where consent is required and you haven't chosen yet, nothing from Ploy loads. Its code and data go to ingest.ploy.ai. Ploy is based in the US and stores data there.

If you change your mind

Click Cookie settings in the footer and choose Reject. The page reloads without these tools, and we delete the first-party cookies they set on activeset.co (such as _ga, _clck, _fuid and _lc2_fpi). They stay off until you click Accept again. The one exception is Ploy, which keeps counting page views in its cookieless mode, as described above.

Cookies on other companies' domains

Some of these tools also use cookies on their own domains, for example Google, Microsoft or LiveIntent. We can't delete those from activeset.co. You can clear them in your browser settings, and the companies' own privacy notices explain how they use them.

Questions

If you have a question about this notice, send it through the contact form at activeset.co/contact-us.