Component Sense Cookie Policy  

Last Updated: Oct 8, 2026  

1. About this policy 

This policy explains the cookies and similar technologies Component Sense uses on its websites, what each one does, and how you can control them. 

Component Sense is a company registered in Scotland (company number SC360076), with its office at Unit 1, R6, Queen Anne Drive, Newbridge, Edinburgh, EH28 8LH, United Kingdom. In this policy, “we”, “us” and “our” mean Component Sense. 

This policy covers: 

• www.componentsense.com, including our online shop 
• our blog 
• connect.componentsense.com and our other landing pages 

It should be read alongside our Privacy Policy, which explains how we handle personal data more generally, including your rights. 

2. What cookies and similar technologies are 

Cookies are small text files that a website saves on your device when you visit. They let the site, or a third party, recognise your device later. 

We also use similar technologies that work in the same way, including: 

• tags and scripts: small pieces of code that run in your browser and send information to us or a third party 
• pixels: tiny invisible images that record when a page has been viewed 
• browser storage: information saved in your browser, for example local storage or session storage 

In this policy, we use “cookies” to mean all of these. 

Cookies can be first-party (set by our own website) or third-party (set by another company whose service we use). They can last only until you close your browser (session cookies) or for a set period (persistent cookies). 

3. Your choices and how we ask for consent 

We only use strictly necessary cookies unless you agree to more. Analytics and advertising cookies stay off until you choose to switch them on. 

When you first visit our website, a cookie banner asks for your choice. You can: 

• Accept all: allow every category of cookie described in this policy 
• Reject non-essential: allow only strictly necessary cookies 
• Preferences: choose category by category. No optional category is switched on in advance. 

Rejecting is as easy as accepting, and rejecting cookies does not stop you from using our website. 

Changing your mind. You can change or withdraw your consent at any time by clicking the cookie icon in the bottom-left corner of any page. If you withdraw consent, we stop using those cookies from that point. Cookies already on your device can be deleted through your browser settings. 

Remembering your choice. We remember your choice so you are not asked on every page. We may ask you again from time to time, for example if we change the cookies we use. 

Browser settings. Most browsers also let you block or delete cookies. Blocking strictly necessary cookies may stop parts of the site, such as the shop basket, from working. 

4. Strictly necessary cookies 

These are needed for the website to work, to keep it secure, or to deliver what you have asked for, such as your shop basket. The law allows us to use them without consent, so they cannot be switched off in the banner. 

• Cookie choices (Silktide Consent Manager): remembers your cookie choices so we don’t ask on every page. Stored in your browser as silktideCookieChoice_* until you change your choice or clear your browser storage. 
• HubSpot cookie choices (on our blog and connect. pages): pass your cookie choices to HubSpot so it only tracks you if you agree. Cookies: __hs_cookie_cat_pref and __hs_opt_out (6 months), __hs_initial_opt_in (7 days). 
• Shop and basket: keep items in your basket and process your order. They last for your shopping session. 
• Account login: keep you signed in to your account. They last until you sign out or close your browser. 
• Cloudflare (on our blog and connect pages): protects against bots and excessive requests. Cookies: __cf_bm (30 minutes), __cfruid and _cfuvid (end of session). 
• Google reCAPTCHA (on our forms): protects our forms from spam and abuse. Cookie: _GRECAPTCHA (6 months), plus _grecaptcha in browser storage. 
• Front live chat (on the shop): lets you chat with our team. Stores chat settings in your browser (frontChat:*). The chat widget includes Front’s own error monitoring from Datadog (cookie _dd_s, which extends by 15 minutes each time you interact, up to 4 hours) and Bugsnag (bugsnag-anonymous-id in browser storage). 

https://knowledge.hubspot.com/privacy-and-consent/what-cookies-does-hubspot-set-in-a-visitor-s-browserhttps://docs.datadoghq.com/real_user_monitoring/browser/troubleshooting

5. Analytics cookies (only with your consent) 

These help us understand how visitors use our websites, such as which pages are popular and where people leave so that we can improve them. They are only set if you accept analytics cookies. 

The companies that provide these tools receive information about your visit, including your IP address and device details. Some may also use it for their own purposes, as explained in their privacy policies linked below. 

• Google Analytics: shows us how visitors use our site, such as which pages are viewed. Cookies: _ga (tells visitors apart) and _ga_<ID> (keeps track of your visit), both lasting 2 years. 
• Microsoft Clarity: shows us where visitors click and scroll, using heatmaps and session recordings. Cookies: _clck (up to 1 year) and _clsk (1 day). Microsoft also sets CLID, MUID, MR, SM, SRM_B, and ANONCHK to recognise your browser across sites that use its services (for up to 13 months). 
• HubSpot: tracks your visits and links them to any form you submit. Cookies: __hstc and hubspotutk (6 months), __hssc (30 minutes) and __hssrc (end of session). 

Session recordings. Microsoft Clarity records how you scroll, click and move around our pages so we can spot problems. We configure Clarity to mask text you type into forms. 

Forms. If you accept analytics cookies and then fill in one of our forms, HubSpot links your earlier browsing on our site to the details you submit. This helps us understand what you were interested in before contacting us. 

6. Advertising cookies (only with your consent) 

These help us measure whether our adverts on Google and LinkedIn lead to enquiries, and show our adverts to people who have visited our website. They are only set if you accept advertising cookies. 

Google and LinkedIn operate as separate companies, each responsible for its own use of this information. They may combine it with what they already know about you, for example, if you are signed in to a Google or LinkedIn account, as explained in their own policies: Google advertising cookies and LinkedIn cookie policy. 

• Google Ads: measures whether our Google adverts lead to enquiries, and shows our adverts to people who have visited our site. Cookies: _gcl_au and _gcl_aw (90 days), IDE (13 months in the UK and EEA) and test_cookie (15 minutes). 
• LinkedIn: measures whether our LinkedIn adverts lead to enquiries, and shows our adverts to people who have visited our site. Cookies: bcookie (1 year), li_gc (6 months, remembers your LinkedIn consent choice), li_sugr (up to 90 days), UserMatchHistory, AnalyticsSyncHistory and li_fat_id (30 days), and lidc (1 day). 

You can also manage how Google and LinkedIn personalise adverts in your Google ad settings and your LinkedIn account settings. 

Social media embeds. Some blog posts include share buttons and posts from Facebook and X (Twitter). These load content from those companies, which can set their own cookies, so we only load them if you accept advertising cookies. 

7. Business visitor identification (Lead Forensics) 

We use Lead Forensics to find out which businesses visit our website. It runs on every visit, regardless of what you choose in the cookie banner. 

How it works. A script on our pages sends your IP address and basic technical details of your visit, such as the pages you view, to Lead Forensics. Lead Forensics compares the IP address with its database of business networks. If it matches a business, it tells us the company’s name and details, as well as which pages were viewed. It does not aim to identify private individuals or home internet connections, and it discards IP addresses it cannot match (Lead Forensics data compliance). For visitors from the United States, Lead Forensics may also use a cookie called lfuuid (lasting 1 year) and share limited identifiers with its data partners to improve matching. 

Why we use it: it helps our sales team understand which companies are interested in our services so we can follow up with relevant information. Lead Forensics acts on our behalf under a data processing agreement. 

Your right to object. If you do not want your visits included, please contact us, and we will work with Lead Forensics to handle your request. You can also use a browser extension that blocks tracking scripts. 

8. What happens if you reject cookies 

If you reject analytics and advertising cookies, Microsoft Clarity, HubSpot, LinkedIn, and Google Ads remarketing will not run, and none of their cookies will be set. 

Google Analytics and Google Ads use Google’s consent mode. When you reject cookies, they do not set or read any cookies. Instead, they send Google limited messages without a cookie ID, sometimes called cookieless pings. These record whether a page was viewed or a form was submitted, along with the technical details your browser always sends, such as your IP address, browser type, and screen size (Google consent mode). Google uses them to estimate overall visit and enquiry numbers without identifying you. 

Lead Forensics also continues to run, as described in section 7. 

9. Your rights, international transfers and contact 

Your rights. Where cookies collect personal data, you have rights under UK data protection law, including the right to access it, object to its use, and withdraw consent at any time. Our Privacy Policy explains these rights and how to use them. 

Visitors outside the UK. We apply the same choices to all visitors. Non-essential cookies are off until you agree, wherever you are. 

International transfers. Some providers in this policy, including Google, Microsoft, LinkedIn, HubSpot, Front, Datadog and Bugsnag, may process information outside the UK, including in the United States. Where they do, we rely on legal safeguards such as the UK-US Data Bridge or the UK’s approved contract terms. 

Changes to this policy. We review this policy whenever we add or remove a cookie, and at least once a year. We will update the “Last updated” date at the top and, if the change is significant, ask for your consent again. 

Questions. If you have any questions about this policy or how we use cookies, please contact us.