This page provides comprehensive information about how we use cookies on our website to enhance your browsing experience, improve website performance, and deliver personalized content. Cookies are small text files that are stored on your device when you visit our site. They help us understand how visitors interact with our website, allowing us to offer a smoother and more efficient user experience. In the table below, you will find detailed information about each type of cookie we use, their purpose, and how long they remain on your device. We are committed to respecting your privacy and providing transparency about the data we collect through cookies. For more information on how we handle your personal data, please see our Privacy Policy.
Essential
Essential cookies enable basic functions and are necessary for the proper function of the website.
| Name | Description | Duration |
|---|---|---|
| yhm_session_cookie | Provides wishlist functionality for the online moulding catalog. | 14 days |
| wpconsent_preferences | This cookie is used to store the user's cookie consent preferences. | 30 days |
CleanTalk
CleanTalk offers effective spam protection and website security solutions to enhance user experience.
| Name | Description | Duration |
|---|---|---|
| wordpress_apbct_antibot | Used in order to detect spam and improve the website's security. | Session |
| apbct_ | Group of cookies which are set from backend and contain information about the current user | Session |
| ct_ | Group of cookies used for storing dynamic variables from browser | Session |
| ct_sfw_ | Group of cookies used for our SpamFireWall technology. | Session |
| spbc_cookies_test | Cookie to test cookies so we know that everything working properly | Session |
| spbc_firewall_pass_key | The flag defines if the Security Firewall was passed. | Session |
| spbc_is_logged_in | Dashboard. Flag defines if a user was logged in. | Session |
| spbc_timer | Dashboard. Time spent on the page. | Session |
| spbc_log_id | Dashboard. User identification. | Session |
| spbc_2fa_passed | Dashboard. Flag defines if Two-Factor Authentication was passed. | Session |
| apbct_antibot | This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. | session |
| ct_check_js | Used in order to detect spam and improve the website's security. | session |
| ct_fkp_timestamp | Used in order to detect spam and improve the website's security. Does not store visitor specific data. | session |
| ct_has_scrolled | This cookie is used to distinguish between humans and bots. | session |
| ct_pointer_data | Used in order to detect spam and improve the website's security. Does not store visitor specific data. | session |
| ct_ps_timestamp | Used in order to detect spam and improve the website's security. Does not store visitor specific data. | session |
| ct_timezone | Used in order to detect spam and improve the website's security. | Session |
| apbct_cookies_test | Сookie to validate other cookies, so they can’t be spoofed. | Session |
CloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Learn more| Name | Description | Duration |
|---|---|---|
| cf_use_ob | The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds. | session |
| __cfwaitingroom | The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active. | session |
| cf_chl_rc_i | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| cf_chl_rc_ni | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| cf_chl_rc_m | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| __cfruid | Used by the content network, Cloudflare, to identify trusted web traffic. | session |
| __cf_bm | Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. | session |
| __cflb | When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool. | session |
| _cfuvid | The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address. | session |
| cf_clearance | Whether a CAPTCHA or Javascript challenge has been solved. | session |
| __cfseq | Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies. | session |
| cf_ob_info | The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic | session |
Statistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Ads
Google Ads is an online advertising platform that enables businesses to create targeted ads displayed on Google search results and partner sites.
Learn more| Name | Description | Duration |
|---|---|---|
| __Secure-1PSID | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years |
| __Secure-1PSIDCC | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years |
| __Secure-3PAPISID | Profiles the interests of website visitors to serve relevant and personalised ads through retargeting. | 2 years |
| AEC | AEC cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user's knowledge. | 6 months |
| ADS_VISITOR_ID | Cookie required to use the options and on-site web services | 2 months |
| __Secure-3PSIDCC | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years |
| __Secure-3PSIDTS | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years |
| __Secure-1PSIDTS | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years |
| __Secure-1PAPISID | Targeting cookie. Used to create a user profile and display relevant and personalised Google Ads to the user. | 2 years |
| __Secure-3PSID | Targeting cookie. Used to profile the interests of website visitors and display relevant and personalised Google ads. | 2 years |
| Conversion | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 days |
| _gcl_aw | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days |
| _gcl_gs | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days |
| _gcl_gb | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days |
| _gac_gb_ | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days |
| FPGCLGB | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days |
| FPGCLAW | Google uses cookies for advertising, including serving and rendering ads, personalizing ads (depending on your ad settings at g.co/adsettings), limiting the number of times an ad is shown to a user, muting ads you have chosen to stop seeing, and measuring the effectiveness of ads. | 90 Days |
Google Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Learn more| Name | Description | Duration |
|---|---|---|
| __utmb | Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server. | 30 minutes after last activity |
| __utmc | Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. | End of session (browser) |
| __utmz | Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server | 6 months after last activity |
| __utmv | Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server. | 2 years after last activity |
| __utmx | Used to determine whether a user is included in an A / B or Multivariate test. | 18 months |
| _ga | ID used to identify users | 2 years |
| _gali | Used by Google Analytics to determine which links on a page are being clicked | 30 seconds |
| _ga_ | ID used to identify users | 2 years |
| _gid | ID used to identify users for 24 hours after last activity | 24 hours |
| _gat | Used to monitor number of Google Analytics server requests when using Google Tag Manager | 1 minute |
| _gac_ | Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. | 90 days |
| __utma | ID used to identify users and sessions | 2 years after last activity |
| __utmt | Used to monitor number of Google Analytics server requests | 10 minutes |
Hotjar
Hotjar is a powerful analytics tool that helps you understand user behavior through heatmaps and session recordings.
| Name | Description | Duration |
|---|---|---|
| _hjptid | This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site. | session |
| _hjAbsoluteSessionInProgress | The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. | 30 minutes |
| _hjFirstSeen | The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. | 30 minutes |
| _hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's page view limit. | 30 minutes |
| _hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit | 30 minutes |
| _hjSession_ | A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. | 30 minutes |
| _hjSessionUser_ | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. | 365 days |
| _hjSessionTooLarge | Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit. | session |
| _hjSessionRejected | If present, this cookie will be set to 1 for the duration of a user’s session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues. | session |
| _hjSessionResumed | A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection. | session |
| hjViewportId | This cookie stores user viewport details such as size and dimensions. | Session |
| _hjSessionStorageTest | This cookie checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set. | Session |
| _hjTLDTest | When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. | session |
| _hjCookieTest | This cookie checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set. | Session |
| _hjUserAttributesHash | User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. | session |
| _hjCachedUserAttributes | This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. | session |
| _hjLocalStorageTest | This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted immediately after creating it so the expected storage time is under 100ms. | |
| _hjHasCachedUserAttributes | This cookie sets when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. Ensures data from subsequent visits to the same site are attributed to the same user ID. | 365 days |
| _hjid | Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. | 365 days |
| hj_visitor | hotjar uses cookies to enhance the user’s experience on our website, for example to complete forms, navigating the site, and identify returning users and offer related content. Users can control the use of cookies at the individual browser level. | Session |
| _hjIncludedInSample | Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels. | 365 days |
| _hjClosedSurveyInvites | Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown. | 365 days |
| _hjDonePolls | Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in. | 365 days |
| _hjMinimizedPolls | Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site. | 365 days |
| _hjDoneTestersWidgets | Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in. | 365 days |
| _hjMinimizedTestersWidgets | Hotjar cookie. This cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site. | 365 days |
| _hjShownFeedbackMessage | This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show. | 365 days |
Marketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Google AdSense
Monetize your website by displaying targeted ads and earning revenue from clicks and impressions.
| Name | Description | Duration |
|---|---|---|
| _gcl_au | Used by Google AdSense to store and track conversions and experiment with advertisement efficiency across websites. | 90 days |
| GED_PLAYLIST_ACTIVITY | Improves targeting/advertising within the website | session |
| ACLK_DATA | This cookie is used to help improve advertising. This targets advertising based on what's relevant to a user, to improve reporting on campaign performance. | 5 minutes |
| __gsas | Provides ad delivery or retargeting. | 3 months |
| __gpi | Collects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website. | 13 months |
| __gpi_optout | Collects information on user behaviour on multiple websites. This information is used in order to optimize the relevance of advertisement on the website. | 13 months |
| __eoi | This cookie is used for security authenticate users, prevent fraud, and protect users as they interact with a service. | 3 Months |
| pm_sess | This cookie is used for functionality allow users to interact with a service or site to access features that are fundamental to that service. Things considered fundamental to the service include preferences like the user's choice of language, product optimizations that help maintain and improve a service, and maintaining information relating to a user's session, such as the content of a shopping cart. | 30 minutes |
| pm_sess_NNN | This cookie is used for functionality allow users to interact with a service or site to access features that are fundamental to that service. Things considered fundamental to the service include preferences like the user's choice of language, product optimizations that help maintain and improve a service, and maintaining information relating to a user's session, such as the content of a shopping cart. | 30 minutes |
| aboutads_sessNNN | This cookie is used for security authenticate users, prevent fraud, and protect users as they interact with a service. | 30 minutes |
| ANID | Cookies used for functionality allow users to interact with a service or site to access features that are fundamental to that service. Things considered fundamental to the service include preferences like the user's choice of language, product optimizations that help maintain and improve a service, and maintaining information relating to a user's session, such as the content of a shopping cart. | 13 months |
