ENSEK's Cookies Notice
Version 1
Last updated: 9th June 2022
A - WHAT IS THIS COOKIES NOTICE ABOUT?
B - WHO IS THE PUBLISHER OF THIS COOKIES NOTICE?
C - HOW DO WE STORE OR OBTAIN INFORMATION?
D - HOW DO WE OBTAIN YOUR CONSENT?
E - WHAT INFORMATION DO WE STORE OR OBTAIN AND WHY?
A - WHAT IS THIS COOKIES NOTICE ABOUT?
This cookies notice explains what information we store on or obtain from your browser and computer when visiting our websites.
What is the applicable law? | This cookies notice is published for the purposes of Section 6 of The Privacy and Electronic Communications (EC Directive) Regulations 2003. |
What does the law require? | The law also requires us to gain your consent. The law requires us to give you clear and comprehensive information about what information we store on or extract from your browser and computer when you visit our web pages: which is the purpose of this notice. |
Overview of our usage | We use cookies and other technologies to collect data anonymously about the use of our websites and the effectiveness of our advertising campaigns. Some data may cease to be anonymous if you are added to our Hub Spot marketing database, in which case we can see what you personally are visiting on our website and when you open emails from us. |
Any questions? | If you have any questions, please contact our data protection officer through the email address provided in this document. |
Right to complain | We hope that we can resolve any query or concern you have, but in any case, you always have the right to complain to the Information Commissioner at any time. Their details are: Address: Information Commissioner’s Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF Helpline number: 0303 123 1113 ICO website: LINK : ICO: Complaints Page. |
B - WHO IS THE PUBLISHER OF THIS COOKIES NOTICE?
This cookies notice is published by the following company:
Our Company Name | ENSEK Ltd |
Our Company Number | 07167027 |
Our Country of Registration | England and Wales |
Our Registered Office | Hounds Gate, 30-34 Hounds Gate, Nottingham, England, NG1 7AB. This is also our postal address and head office. |
Our Website | |
Data Protection Email | dataprotection@ensek.co.uk |
Our Data Protection Officer | Julian Turner |
Our Head of Information Security | Trish Sewell |
C - HOW DO WE STORE OR OBTAIN INFORMATION?
We do this through technologies that are built into your browser. The technologies we use are as follows.
Cookies | This is the most well-known technology and has been in web browsers since they were first invented in the 1990s. A cookie is a tiny text file that is stored by your browser in a special folder on your computer. Your browser lets you examine them and delete them. For example, if you use Chrome, insert the following in the address bar: chrome://settings/siteData Your web browser lets you block cookies through settings, but some parts of the site may not work as a result. |
Local and Session Storage | This is a less well-known technology and has only been in browsers in the last 10 years. Your browser lets a web page store a value against a name (called a key pair), and retrieve it later. It is like a cookie but stored in a different place. This is either called Local Storage (it is stored forever, until you clear all of your history), or Session Storage (it is stored until you leave the web page only). If you have Chrome, open the Developer Tools (CTRL + SHIFT + I), and go to the Application tab. |
Javascript | JavaScripts are small computer programs that a web browser can download and run. They have been on web pages and web browsers since 1990. They cannot access your computer, but they can access what you do on the web page it came with, and send information back to the computer that sent the web page to you. They are used both to animate and operate the functionality of the web page and to send or retrieve data to the computer that sent the web page to you. They can track key presses, clicks, and mouse movements and send details of them back; which is often used for analytics purposes. If you have Chrome, open the Developer Tools (CTRL + SHIFT + I), and go to the Sources tab to see all Javascripts downloaded by our website. Your web browser lets you block Javascript through settings, but some parts of the site may not work as a result. |
Tracking Pixels | Small transparent images are included in a web page or email to let us know when it has been visited or read. We find out when your web browser or email client calls our server to retrieve images for the website or email. |
D - HOW DO WE OBTAIN YOUR CONSENT?
This part of the notice looks at how we obtained your consent.
When don't we need consent? | We don't need your consent if the information is just to enable the website to be transmitted to you or for you to send us information. We also don't need consent if the information is strictly necessary for the features of the website used by you to operate correctly (e.g., to enable you to submit a form or job application). We also don't need consent to store a cookie to remember your choices relating to the technologies we use. We refer to these as Exempted reasons. |
When do we need consent? | We need consent in every other case. |
How do we obtain consent? | We have reviewed the guidance from the Information Commissioner. We have determined that we will have a banner, that points to this notice and gives you a choice. If you click Accept, then we will proceed with our full information storage and use as explained in the next part. If you click Reject, then only transmission and strictly necessary cookies will be used. |
E - WHAT INFORMATION DO WE STORE OR OBTAIN AND WHY?
This is the most important part of this cookies notice, which explains what we actually do at present.
A good source of information is Cookies Database.
CRAFT Content Management System
Name | Technology | Used For | Expires | Further Information |
CRAFT_CSRF_TOKEN | Cookie | Transmission (Exempted) | When the browsing session ends | ENSEK uses the CRAFT content management system for its website. See https://craftcms.com/ . The cookie stores a value that uniquely identifies your browser, to ensure that messages coming into the server are genuinely from you. |
Google reCaptcha
Name | Technology | Used For | Expires | Further Information |
Overview | Cookie | Transmission (Exempt) | 6 months. | We use Google reCAPTCHA to prevent malicious actors (including automated bots) from abusing our forms and submitting lots of requests. |
_GRECAPTCHA | Cookie | Transmission (Exempted) | 6 months | Enables Google reCaptcha to see how many times a visitor is visiting, to detect if they are a bot. |
rc::a | Local Storage | Transmission (Exempted) | Indefinite | The value used to read and filter requests from bots as part of Google reCAPTCHA. |
rc::b | Session Storage | Transmission (Exempted) | End of the browsing session | The value used to read and filter requests from bots as part of Google reCAPTCHA. |
rc::c | Session Storage | Transmission (Exempted) | End of the browsing session | The value used to read and filter requests from bots as part of Google reCAPTCHA. |
Google Analytics
Name | Technology | Used For | Expires | Further Information |
Overview | JavaScript | Analytics | 2 years | We use Google Analytics to collect user interaction data with our website, anonymously, and consider that data in Dashboards and other ways, to inform our view of visits to our site, where they are coming from, and how well the site is working and what improvements we could make. In particular, we use it to track the following information (recorded anonymously by reference to a unique numerical ID assigned to your browser):
The technology used to collect this is JavaScript plus some cookies to store unique identifiers, as noted below. See: Analytics JS and the file “analytics.js” from the resource “<a href=" gtag at googleadmanager.com and" class="redactor-autoparser-object">www.google-analytics.com. &...;... the file “js?id=UA-37212384-1” from the resource <a href=" |
_ga | Cookie | Analytics | 2" class="redactor-autoparser-object">www.googletagmaager.com/gtag.&...;... years | Used by Google Analytics to uniquely but anonymously identify your browser as a visitor to our site, long term, and distinguish you from other visitors, against which tracking data can then be stored. |
_gid | Cookie | Analytics | 24 hours | Used by Google Analytics to uniquely but anonymously identify your computer as a visitor to our site for your recent visits, and distinguish you from other visitors, against which tracking data can then be stored. |
_gat_gtag_UA_37212384_1 | Cookie | Analytics | 1 minute | Used by Google Analytics to regulate and restrict number of calls to its servers in connection with your visit to our site, to manage server demand. |
CloudFlare
Name | Technology | Used For | Expires | Further Information |
__cf_bm | Cookie | Transmission(Exempt) | 30 minutes | CloudFlare is a tool used by us to host our website. This cookie is used the same as Google reCaptcha, to provide security from automated software(bots) visiting our website. |
Hubspot
Name | Technology | Used For | Expires | Further Information |
Overview | JavaScripts Cookies | Marketing | Never | We use Hubspot software to manage our sales and marketing information, and for customer relationship management, and to track when persons in our marketing database use our website. We pass through your forms from our website to Hubspot for processing - see our separate Public Privacy Notice that applies when information is linked to you and is no longer anonymous. See Hubspot Cookies. You can see Hubspot JavaScript for this from the following resources when you look at the developer tools for our website:
|
__hs_initial_opt_jn | Cookie | Analytics | 1 week | Used to record if you say "Accept" to a cookies banner. This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode. It contains the string "yes" or "no". It expires in seven days. |
__hs_initial_opt_out | Cookie | Analytics | 6 months | If you "Reject" cookies, you will not be asked again for 6 months. 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. It contains the string "yes" or "no". It expires in 6 months. |
__hstc | Cookie | Analytics | 6 months | 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). It expires in 6 months. |
Hubspotutk | Cookie | Analytics | 6 months | This cookie 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. It expires in 6 months. |
__hssc | Cookie | Analytics | 30 minutes | 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. It expires in 30 minutes. |
__hssrc | Cookie | Analytics | When browsing ends | 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. It contains the value "1" when present. It expires at the end of the session. |
Meta Pixel (Facebook)
Name | Technology | Used For | Expires | Further Information |
Overview | JavaScripts | Marketing | Never | We use Facebook Meta Pixels (Link) to track how effective our ads are on Facebook. This links your account with our ads, and also links with google ad manager and linked in. Our website downloads the following JavaScript for this purpose under the “webpack resources”:
|
Linked In
Name | Technology | Used For | Expires | Further Information |
lang | Cookies JavaScripts | Analytics | End of browsing session | Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings. See the JavaScript downloaded from the resource snap.lcdn.com (insight.min.js). |
AnalyticsSyncHistory | Cookie | Analytics | 1 month | Used to store information about the time a sync took place with the lms_analytics cookie |
UserMatchHistory | Cookie | Analytics | 1 month | Used for id sync process. It stores the last sync time to avoid repeating the syncing process in a frequent manner |
bcookie | Cookie | Analytics | 2 years | Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform |
bscookie | Cookie | Analytics | 2 years | Used for remembering that a logged in user is verified by two factor authentication |
li_gc | Cookie | Analytics | 2 years | Used to store consent of guests regarding the use of cookies for non-essential purposes |
lidc | Cookie | Analytics | 1 day | To facilitate data center selection |