Home Data Protection & Privacy Notice FAQs

Like most websites, we use cookies. A cookie is a piece of text that a web server can store on the user’s hard drive. Cookies allow websites to store information on the user's device and to retrieve such information at a later date. They are not programs and therefore cannot “do” anything on the computer. A website can only retrieve the information that it has placed on the computer. It does not have access to any other cookie files or to any other information on the computer.

For example, the text file or cookie may be an individual identification number that the website assigns to a computer. This identification number is sent to the website if the computer accesses the website again. This is how website operators collate their visitor numbers and statistics.

We use only strictly necessary cookies. These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.

This site uses the following cookies, which are required by the site to function as intended

Cookie: ASPSESSIONIDASVABCTA

Purpose: Session state enables you to store and retrieve values for a user as the user navigates pages in a web application.

Lifespan: Session: 30-minutes since last access by user for given session

Cookie: NGSecure

Purpose: Created and used by the firewall / load balancer for session persistence

Lifespan: Session: 30-minutes since last access by user for given session

Cookie: ep

Purpose: Stores variables related to report dispatch and intake method for NAVEX contact center intake method

Lifespan: Session: 30-minutes since last access by user for given session

Cookie: incap_ses

Purpose: Supports firewall. The cookie on which relate HTTP requests to a certain session (AKA visit - re-opening the browser and accessing same site is supposed to be considered different visits).

Lifespan: Session

Cookie: visid_incap

Purpose: Supports firewall. The cookie on which we relate sessions to a specific visitor (visitor representing a specific computer)

Lifespan: 1 year

Cookie: nlbi

Purpose: Supports firewall. To ensure requests by a client are sent to the same origin server.

Lifespan: Session