29 August 2023

Cookie statement

Steel Protection Group B.V. uses cookies. Cookies are small text files stored by browsers on your computer, tablet, or smartphone. The information they contain can be sent to our servers on your next visit to our website.

What are cookies?

Steel Protection Group uses cookies to optimise its website and monitor usage by keeping track of visitor numbers and times, as well as the average time spent on a page. These data are processed in aggregated form only and cannot be traced back to particular computers or individuals. Below Steel Protection Group will explain the different types of cookies it uses and what they do.

Functionality cookies

Without functionality cookies websites do not work optimally. These cookies are necessary to retain the information that you provide, store preferences and login data and to remember your browser settings to enable you to view the website properly. These strictly necessary cookies do not require your consent. Go to your browser settings if you wish to disable functionality cookies.

Performance cookies

Performance cookies help Steel Protection Group monitor which parts of the website draw most visitors. The information gathered (visitor numbers, average time spent, popular pages and topics, etcetera) are used for statistics. The statistics enable Steel Protection Group to optimise its website and make content and navigation as user-friendly as possible. These statistical data cannot be used to identify visitors.

Google Analytics

Through our website cookies are placed of Google as part of their Analytics service. Google uses this tool to make reports for Steel Protection Group on how visitors use the website. As Steel Protection Group has made a processor agreement with Google, the ’share data with Google’ option has been disabled, Google does not process the full IP address and no other Google services are used, the installation of those cookies does not require your consent.

Tracking Cookies

Hubspot tracking cookies are used to make specific recommendations to you on the basis of how you behave when surfing the web. By doing so, we hope to customise our website and information better, so that you do not miss any information and recommendations which are of interest to you. We will only place these cookies if you have given us permission.

Cookies

The list below shows all the cookies that could be placed during a visit to our website. It shows the name of the cookie, information about the cookie measures and purpose and for how long the cookie is stored.

hubspotuk
•    Purpose: 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.
•    Expiry period: 13 months

_hstc
•    Purpose: 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).
•    Expiry period: 13 months

_ga
•    Purpose: This registers a unique ID that is used to generate statistical data about the way in which the visitor uses the website.
•    Expiry period: 2 years

_gcl_au
•    Purpose: Used by Google AdSense for experimenting with advertisement efficiency across websites using their services.
•    Expiry period: 3 months

_gid
•    Purpose: This registers a unique ID that is used to generate statistical data about the way in which the visitor uses the website.
•    Expiry period: 24 hours

_gat
•    Purpose: Used by Google Analytics to limit the number of requests sent to the Analytics server.
•    Expiry period: 1 minute

__hssc
•    Purpose: 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.
•    Expiry period: 30 minutes

__hssrc
•    Purpose: 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.
•    Expiry period: Session

messagesUtk
•    Purpose: 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.
•    Expiry period: 13 months

cookieconsent_status
•    Purpose: This cookie is used to remember if you have consented to the use of cookies on this website. When you consent, a cookie is set which prevents the Cookie Notifier bar from appearing at the bottom of the browser window.
•    Expiry period: 1 year

UMB_UCONTEXT
•    Purpose: Umbraco backend session cookies. Essential for accessing secure areas of our website. Used for maintaining the session stage of the logged in user.
•    Expiry period: Session

UMB_UCONTEXT_C
•    Purpose: Umbraco backend session cookies. Essential for accessing secure areas of our website. Used for maintaining the session stage of the logged in user.
•    Expiry period: Session

UMB-XSRF-V
•    Purpose: Umbraco backend session cookies. Essential for accessing secure areas of our website. Used for maintaining the session stage of the logged in user.
•    Expiry period: Session

UMB-XSRF-TOKEN
•    Purpose: Umbraco backend session cookies. Essential for accessing secure areas of our website. Used for maintaining the session stage of the logged in user.
•    Expiry period: Session

_hjid
•    Purpose: 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.
•    Expiry period: 1 year

_hjIncludedInSample
•    Purpose: 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.
•    Expiry period: 1 year

_fbp
•    This cookie will help deliver our advertising to people who have already visited our website when they are on Facebook or a digital platform powered by Facebook Advertising.
•    Function: Targeting/ Re-marketing cookies.
•    Expiry period: 3 months

__RequestVerificationToken
•    Purpose: This is an anti-forgery cookie set by web applications built using ASP.NET MVC technologies. It is designed to stop unauthorised posting of content to a website, known as Cross-Site Request Forgery. It holds no information about the user and is destroyed on closing the browser.
•    Expiry period: Session

ASP.NET_SessionId
•    Purpose: ASP.Net_SessionId is a cookie which is used to identify the users session on the server. The session being an area on the server which can be used to store session state in between http requests.
•    Expiry period: Session

ARRAffinity
•    Purpose: This is used because our website is hosted on Microsoft Azure to keep a visitor’s session to a specific instance of the website within Azure.
•    Expiry period: Session

Enabling, disabling and removing cookies

For more information about enabling or disabling or removing cookies, please read the instructions and/or the Help section of your browser. Disabling cookies may mean that the website no longer works optimally. To turn off cookies from specific parties, we refer you to www.youronlinechoices.eu.

Geen resultaten gevonden