Cookie Policy
This policy explains the way cookies work and what they are used for on our Internet websites.
Introduction
Cookies are small text files that are stored on your device when you visit a website. They help improve your browsing experience, remember preferences, and provide analytics or targeted advertising.
Cookies can be persistent, remaining on your device for a set period, or session-based, deleted when you close your browser.
First-party cookies are created by the website you are currently visiting and can only be read by that website. In addition, a website might potentially use external services, which also set their own cookies, known as Third-party cookies.
Cookie Types
Essential Cookies: Strictly necessary for basic website functionality, such as login sessions or shopping cart management. These do not require consent.
Performance Cookies: Track user interactions anonymously to improve website performance, such as page views and bounce rates.
Functionality Cookies: Enable enhanced features, like remembering user preferences or login status.
Analytics Cookies: Track user behaviour to analyse trends, monitor navigation, and gather demographic information.
Advertising Cookies: Used to deliver relevant ads, measure campaign performance, and avoid showing repeated ads.
How do we use cookies?
Our website is hosted by HubSpot, and this uses the following cookies: -
HubSpot Essential Cookies
| Name | Purpose | Typical duration | First or third party |
|---|---|---|---|
| __cfruid | Necessary to support Cloudflare Rate Limiting products. | Expires at end of session | Third party |
| __cfuvid | Used to distinguish individual users who share the same IP address, such as traffic behind a NAT. | Expires at end of session | Third party |
| __cf_bm | Used to identify and mitigate automated traffic to protect website from bad bots. | expires in 30 minutes | Third party |
| __hs_opt_out | Used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. It contains the string "yes" or "no". | expires in 6 months. | First party |
| __hs_do_not_track | Used to prevent the tracking code from sending any information to HubSpot. It contains the string "yes" or "no". | expires in 6 months. | First party |
| __hs_initial_opt_in | Used to prevent the banner from always displaying when visitors are browsing in strict mode. It contains the string "yes" or "no". | expires in seven days | First party |
| __hs_cookie_cat_pref | Used to record the categories a visitor consented to. It contains data on the consented categories. It contains the string "yes" or "no". | expires in 6 months | First party |
| __hs_gpc_banner_dismiss | Used when the Global Privacy Control banner is dismissed. It contains the string "yes" or "no". | expires in 180 days | First party |
| __hs_notify_banner_dismiss | Used when the website uses a Notify consent banner type. It contains a boolean value of True. | expires in 180 days | First party |
| hs_ab_test | Used to consistently serve visitors the same version of an A/B test page they've seen before. It contains the id of the A/B test page and the id of the variation that was chosen for the visitor. | Expires at end of session | First party |
| hs-messages-is-open | Used to determine and save whether the chat widget is open for future visits. It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity. If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes. | expires in 30 minutes | First party |
| hs-messages-hide-welcome-message | Used to prevent the chat widget welcome message from appearing again for one day after it is dismissed. It contains a boolean value of True or False. | expires in one day | First party |
| __hsmem | Is set when visitors log in to a HubSpot-hosted site. It contains encrypted data that identifies the membership user when they are currently logged in. | expires in seven days | First party |
| hs-membership-csrf | Used to ensure that content membership logins cannot be forged. It contains a random string of letters and numbers used to verify that a membership login is authentic. | Expires at end of session | First party |
| hs-membership-logout-referer | Is set when visitors log out of HubSpot-hosted sites. It contains the value of the Referer header in the visitor's browser at the time of logout. This is the URL of the page the visitor was previously on before they logged out. | expires in one hour or when the visitor logs in to a HubSpot-hosted site | First party |
| hs.superstore.laboratory.<id> | Contains an offline cache of cohorts that a user got assigned for HubSpot Product experiments. It doesn't contain personal identifiable information or information that can identify your device or hardware. HubSpot experiments are anonymous and aren't attached to user sessions. However, if tracking consent is given, specific experiments might be tied to identifiable user sessions. | 48 hours | First party |
| <id>_key | When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again. The cookie name is unique for each password-protected page. It contains an encrypted version of the password so future visits to the page will not require the password again. | expires in 14 days | First party |
HubSpot Functional Cookies
| Name | Purpose | Typical duration | First or third party |
|---|---|---|---|
| messagesUtk | This is the cookie used for the chatflows tool, providing website visitors the ability to initiate a live chat with someone on our team. It contains chat history. | expires in 6 months | First Party |
HubSpot Analytics Cookies
| Name | Purpose | Typical duration | First or third party |
|---|---|---|---|
| __hmpl | Contains metadata regarding tracking events that HubSpot collects throughout the user's journey at HubSpot. It's stored either on the Browser's Session Storage or Local Storage based on the presence or lack of tracking consent. It doesn't contain personal identifiable information or information that can identify your device or hardware. | can't be manually removed and is automatically created whenever conditions are met | First Party |
| hublytics_events_53 | Used by HubSpot Product to temporarily store tracking events created by HubSpot Product until they get dispatched over the network. It's stored either on the Browser's Session Storage or Local Storage based on the presence or lack of tracking consent. It doesn't contain personal identifiable information or information that can identify your device or hardware. | can't be manually removed and is automatically created whenever conditions are met | First Party |
| __hstc | Main cookie for tracking visitors. It contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | expires in 6 months | First Party |
| hubspotutk | keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor. | expires in 6 months | First Party |
| __hssc | Keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. | expires in 30 minutes | First Party |
| __hssrc | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. f this cookie does not exist when HubSpot manages cookies, it is considered a new session. It contains the value "1" when present. | expires at the end of the session | First Party |
Our website uses Microsoft Clarity and this utilises the following cookies: -
Microsoft Clarity Analytics Cookies
| Name | Purpose | Typical duration | First or third party |
|---|---|---|---|
| _clck | Used to recognise returning visitors for Clarity analytics. Persists the Clarity user ID and preferences so the same visitor ID is used for that site. It contains a unique pseudonymous ID. | Expires in 1 year | First Party |
| _clsk | Connects multiple page views by a user into a single Clarity session recording. Lets Clarity stitch pageviews into one session. It contains a string. | Expires in 24 hours | First Party |
| CLID | Identifies the first time Clarity saw this user on any site using Clarity. Set on *.clarity.ms; cross-site analytics identifier. It contains a string. | Expires in 1 year | Third Party |
| MUID | Identifies unique browsers visiting Microsoft sites for advertising, analytics and other operational purposes. It contains a GUID. | Expires in 1 year | Third Party |
| MR | Indicates whether to refresh MUID. It contains a boolean flag. | Expires in 1 hour | Third Party |
Microsoft Clarity Advertising Cookies
| Name | Purpose | Typical duration | First or third party |
|---|---|---|---|
| ANONCHK | Used in the ad/identity stack even though Clarity doesn't use ANID directly. Indicates whether MUID is passed to ANID (an advertising cookie). For Clarity this is always 0. | Expires in 10 minutes | Third Party |
| SM | Used to synchronize the MUID across Microsoft domains. It contains character flags. | Expires in 1 week | Third Party |
Our website uses Google Analytics and this utilises the following cookies: -
Google Analytics cookies
| Name | Purpose | Typical duration | First or third party |
|---|---|---|---|
| _ga | Distinguishes users | Expires in 2 years | First Party |
| _ga_<container-id> | Persists session state for Google Analytics 4 property | Expires in 2 years | First Party |
| _gid | Distinguishes users for short-term analytics | Expires in 24 hours | First Party |
| _gat or _gat_* | Throttles request rate | Expires in 1 minute | First Party |
| _gacgb<container-id> | Stores campaign info | Expires in 90 days | First Party |
How can you manage cookies?
Removing cookies from your device
You can delete all cookies that are already on your device by clearing the browsing history of your browser. This will remove all cookies from all websites you have visited.
Be aware though that you may also lose some saved information (e.g. saved login details, site preferences).
Managing site-specific cookies
For more detailed control over site-specific cookies, check the privacy and cookie settings in your preferred browser
Blocking cookies
You can set most modern browsers to prevent any cookies being placed on your device, but you may then have to manually adjust some preferences every time you visit a site/page. And some services and functionalities may not work properly at all (e.g. profile logging-in).
Consent
We are required to obtain your consent before storing cookies on your device. Consent must be freely given, specific and informed, and it must involve some form of unambiguous positive action.
We use HubSpot's Cookie Consent Banner to provide users the option to consent "opt-in" to non-essential cookies. No non-essential cookies will be stored on the user's device until they have opted in.
How to contact us
If you have any questions regarding this Cookie Policy or the use of cookies on our website, please contact us at dataprivacy@aibs.co.uk or write to the "Data Protection Officer" at Arc-IT Business Solutions Limited, 12, Gleneagles Court, Brighton Road, Crawley, West Sussex, Rh20 6AD.
Updates
We may update this cookie policy periodically. The latest version will always be available on this page.