Storm Darragh latest

Cookie policy

Cookie policy

Our website 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 the site.

Information about our use of 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.

The cookies we use are 'analytical' cookies. They allow us to recognise and count the number of visitors and to see how visitors move around the site 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.

You can find more information about the individual cookies we use and the purposes for which we use them in the table below:

Cookie Name Purpose
Cookie preference CONSENT This cookie is used to remember a user’s choice about cookies on the website.
Universal Analytics (Google) _ga These cookies are used to collect information about how visitors use the site. We use the information to compile reports and to help us improve the website. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited. For more information read Google's overview of privacy and safeguarding data.
_gat
_gat_UA-nnnnnnn-nn 
_gid
Functional cookie          ASP.NET_SessionId   ASP.NET sessions store information within a cookie for the functionality of the website. Sessions are deleted when the browser is closed.
Microsoft Azure Websites ARRAffinity An affinity cookie keeps track of which of the website servers users are connected to, if we have to scale out the website when it is under a high load the affinity cookie ensure the users connection isn’t lost.  The cookie expires at the end of each session.
ARRAffinitySameSite – Azure 
YouTube cookies YSC  We embed videos from our official YouTube channel using YouTube’s privacy-enhanced mode. This mode may set cookies on your computer once you click on the YouTube video player, but YouTube will not store personally-identifiable cookie information for playbacks of embedded videos using the privacy-enhanced mode. For more information read YouTube’s embedding videos information page.
VISITOR_INFO1_LIVE 
Session cookie JSESSIONID This is used to store browsing information on the website, it expires at the end of each session.
Google+1 Cookie NID The Google+ plugin allows you to promote the website using the ‘+1’ button. This cookie is installed by Google to detect if you are currently logged in with a Google account. For more information read Google's policy.
Cloudflare cookie _cfduid The __cfduid cookie is used to override any security restrictions based on the IP address the visitor is coming from. For example, if the visitor is in a coffee shop where there are a bunch of infected machines, but the visitor's machine is known trusted, then the cookie can override the security setting. It does not correspond to any userid in the web application, nor does the cookie store any personally identifiable information.
 
Note: This cookie is strictly necessary for site security operations and can't be turned off. For more information read Cloudflare's cookie information. 
Hotjar cookies _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.
_hjid Hotjar cookie that is set when the customer 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.
_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.
_hjIncludedInPageviewSample This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
_hjIncludedInSessionSample This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.
_hjAbsoluteSessionInProgress This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjFirstSeen This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.