Cookie Policy
The CID GmbH website (and other websites owned and run by companies in the CID group) uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our site.
By using our website you acknowledge your acceptance of the provisions set out on this page
What are Cookies?
A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive. More information can be found at http://www.allaboutcookies.org/
What Cookies does CID use?
We use the following cookies:
- Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website, use a shopping cart or make use of e-billing services.
- Analytical or performance cookies. These allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily.
- Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).
- Targeting cookies. These cookies record your visit to our website, the pages you have visited and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests. [We may also share this information with third parties for this purpose.]
Why does CID use Cookies?
The use of cookies enables us to:
- Estimate our audience size and usage pattern.
- Store information about your preferences, and so allow us to customise our site and to provide you with offers that are targeted to your individual interests]
- Speed up your searches.
- Recognise you when you return to our site.
- Allow you to use our site in a way that makes your browsing experience more convenient, for example, by allowing you to store items in an electronic shopping basket between visits. If you register with us or complete our online forms, we will use cookies to remember your details during your current visit, and any future visits provided the cookie was not deleted in the interim.
You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
Please note that the following third parties may also use cookies, over which we have no control. These third parties may include, for example, advertising networks and providers of external services like web traffic analysis services. These third party cookies are likely to be analytical cookies or performance cookies or targeting cookies:
To deactivate the use of third party advertising cookies, you may visit the consumer page to manage the use of these types of cookies.
You can block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our website.
Except for essential cookies, all cookies will expire as set out in the details below.
Google Analytics
Google Analytics is a simple, easy-to-use tool that helps website owners measure how users interact with website content. As a user navigates between web pages, Google Analytics provides website owners JavaScript tags (libraries) to record information about the page a user has seen, for example the URL of the page. The Google Analytics JavaScript libraries use HTTP Cookies to “remember” what a user has done on previous pages / interactions with the website.
Important: Read the Google Analytics privacy document for more details about the data collected by Google Analytics.
Google Analytics supports three JavaScript libraries (tags) for measuring website usage: gtag.js, analytics.js, and ga.js. The following sections describe how each use cookies.
gtag.js and analytics.js – cookie usage
The analytics.js JavaScript library is part of Universal Analytics and uses first-party cookies to:
- Distinguish unique users
- Throttle the request rate
When using the recommended JavaScript snippet, gtag.js and analytics.js set cookies on the highest level domain they can. For example, if your website address is blog.example.co.uk, analytics.js will set the cookie domain to .example.co.uk. Setting cookies on the highest level domain possible allows users to be tracked across subdomains without any extra configuration.
Note: gtag.js and analytics.js do not require setting cookies to transmit data to Google Analytics.
gtag.js and analytics.js set the following cookies:
| Cookie Name | Expiration Time | Description |
| _ga | 2 years | Used to distinguish users. |
| _gid | 24 hours | Used to distinguish users. |
| _gat | 1 minute | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. |
| AMP_TOKEN | 30 seconds to 1 year | Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service. |
| _gac_<property-id> | 90 days | Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more. |
Customization
Read the analytics.js Domains & Cookies developer guide to learn all the ways these default settings can be customized.
Read the Security and privacy in Universal Analytics document for more information about Universal Analytics and cookies.
ga.js – cookie usage
The ga.js JavaScript library uses first-party cookies to:
- Determine which domain to measure
- Distinguish unique users
- Throttle the request rate
- Remember the number and time of previous visits
- Remember traffic source information
- Determine the start and end of a session
- Remember the value of visitor-level custom variables
By default, this library sets cookies on the domain specified in the document.host browser property and sets the cookie path to the root level (/).
This library sets the following cookies:
| Cookie Name | Default Expiration Time | Description |
| __utma | 2 years from set/update | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmt | 10 minutes | Used to throttle request rate. |
| __utmb | 30 mins from set/update | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. |
| __utmc | End of browser session | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. |
| __utmz | 6 months from set/update | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
| __utmv | 2 years from set/update | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. |
Customization
The following methods can be used to customize how cookies are set:
| _setDomainName | Sets the domain to which all cookies will be set. |
| _setCookiePath | Sets the path to which all cookies will be set. |
| _setCookiePath | Sets the Google Analytics visitor cookie expiration in milliseconds. |
| _setVisitorCookieTimeout | Sets the new session cookie timeout in milliseconds. |
| setCampaignCookieTimeout | Sets the campaign tracking cookie expiration time in milliseconds. |
| _storeGac | Pass in false to disable the GAC cookie. Defaults to true |
Read the Tracking Multiple Domains guide to learn how to configure ga.js to measure user interaction across domains.
urchin.js – cookie usage
Historically, Google Analytics provided a JavaScript measurement library named urchin.js. When the newer ga.js library launched, developers were encouraged to migrate to the new library. For sites that have not completed the migration, urchin.js sets cookies identically to what is set in ga.js. Read the ga.js cookie usage section above for more details.
Google Analytics for Display Advertisers – cookie usage
For customers that are using Google Analytics’ Display Advertiser features, such as remarketing, a third-party DoubleClick cookie is used in addition to the other cookies described in this document for just these features. For more information about this cookie, visit the Google Advertising Privacy FAQ.
HubSpot
Legitimate interest
CID needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Privacy Policy.
Privacy policy
You can unsubscribe from these communications at any time. For more information on how to unsubscribe, our privacy practices, and how we are committed to protecting and respecting your privacy, please review our Privacy Policy.
Consent to communicate
CID is committed to protecting and respecting your privacy, and we’ll only use your personal information to administer your account and to provide the products and services you requested from us. From time to time, we would like to contact you about our products and services, as well as other content that may be of interest to you. If you consent to us contacting you for this purpose, please tick below to say how you would like us to contact you:
Tracking code
HubSpot’s tracking code sets a number of tracking cookies when a visitor lands on your site. These cookies fall into two general categories:
- Essential/necessary cookies: essential cookies which do not require consent
- Consent banner cookies: cookies included in the consent banner under GDPR
Essential/necessary cookies
| __hs_opt_out | This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again. This cookie is set when you give visitors the choice to opt out of cookies. (Expires: 13 months) |
| __hs_do_not_track | This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, as it still allows anonymized information to be sent to HubSpot. (Expires: 13 months) |
| hs_ab_test | This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before. (Expires: end of session) |
| <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. |
| hs-messages-is-open | This cookie is used to determine and save whether the chat widget is open for future visits. It resets to re-close the widget after 30 minutes of inactivity. (Expires: 30 minutes) |
| hs-messages-hide-welcome-message | This cookie is used to prevent the welcome message from appearing again for one day after it is dismissed. (Expires: 1 day) |
| __hsmem | This cookie is set when visitors log in to a HubSpot-hosted site. (Expires: 1 year) |
_Consent banner cookies
| __hstc | The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). (Expires: 13 months) |
| hubspotutk | This cookie is used to keep track of a visitor’s identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. (Expires: 13 months) |
| __hssc | This cookie 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: 30 min) |
| __hssrc | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. (Expires: end of session) |
| messagesUtk | This cookie is used to recognize visitors who chat with you via the messages tool. If the visitor leaves your site before they’re added as a contact, they will have this cookie associated with their browser. If you chat with a visitor who later returns to your site in the same cookied browser, the messages tool will load their conversation history. (Expires: 13 months) |
| Authentication cookies | If you are logged in to HubSpot, HubSpot will set additional authentication cookies. Learn more about cookies set in the HubSpot product. You can also see whether a contact accepted these cookies in their timeline. |
Ads tracking
Facebook Pixel
If you have the Facebook pixel code installed on your website, Facebook may set a cookie on your visitor’s browser. If you use the HubSpot ads tool to select and install your Facebook pixel on pages with the HubSpot tracking code, HubSpot will link the placing of that pixel code to the cookie notification banner. If you require opt-in consent via this banner, the Facebook pixel will not be able to set any cookies on a visitor until they have opted in. If you have manually placed the pixel code on pages (e.g., by editing your site header HTML), HubSpot will not be able to control which visitors Facebook is able to set cookies on.For additional information, refer to Facebook’s business tools terms and Facebook’s cookie consent guide.
How are cookies from third-party systems handled?
HubSpot isn’t able to control cookies placed by third-party scripts on your website. When a visitor accepts cookies via the HubSpot consent banner, they consent to HubSpot’s cookies only. However, you can put code in place to know when a user has accepted or declined HubSpot cookie tracking, then send that information to your third-party system. Learn more about using HubSpot’s consent banner for third-party scripts.
Learn more about removing the cookies created by the HubSpot tracking code that are included in the consent banner under GDPR. When cookies are removed, the visitor will be considered a new visitor and will see the cookie consent banner the next time they visit your site.
If you want to remove existing cookies from your device you can do this using your browser options. If you want to block future cookies being placed on your device you can change your browser settings to do this.
What if I don’t want cookies?
Please bear in mind that deleting and blocking cookies will have an impact on your user experience as parts of the site may no longer work. Unless you have adjusted your browser settings to block cookies, our system will issue cookies as soon as you visit our site or click on a link in a targeted email that we have sent you, even if you have previously deleted our cookies.