Details about cookies

This site puts small files (known as 'cookies') onto your computer to collect information about how you browse the site.

Cookies are used to:

  • measure how you use the website so it can be updated and improved based on your needs
  • remember some of the notifications you've seen so that we don't show them to you again
  • enable functionality of some parts, e.g. remember items in shopping baskets, search criteria etc.

Cookies used


Cookies that are strictly necessary

Cookie details:

  • __Host-CookieSettings
    • Stores your chosen cookie options. It also stops you seeing our cookie message every time you visit a page.
    • Expires: One year
  • __Secure-SpecialHome
    • Cookie used if we need to set a special home page. This cookie stops the special home page from repeatedly showing whilst you browse the site.
    • Expires: When you close your browser
  • ASP.NET_SessionId
    • Used to maintain session information for the Microsoft .NET framework
    • Expires: When you close your browser
  • clientvars
    • Used to maintain session information for the platforms other than Microsoft .NET framework
    • Expires: When you close your browser
  • ASPSESSIONID
    • Session information used in the online courses system to remember search criteria, course titles etc.
    • Expires: When you close your browser
  • mode
    • Sets colour scheme mode - This cookie is no longer used, but exists in our web content management system. It only contains a value of zero.
    • Expires: When you close your browser
  • TextOnlyX
    • Used by Microsoft Internet Explorer only to enable text only
    • Expires: Unknown

Cookies that are used for functional website use

Some Bury.gov.uk pages may contain content from other sites, like YouTube, which may set their own cookies. These sites are sometimes called 'third party' services. This tells us how many people are seeing the content and whether it's useful.

In addition, if you share a link to a Bury.gov.uk page, the service you share it on (for example, Facebook) may set a cookie. We have no control over cookies set on other websites - you can turn them off, but not through us.

Cookie details:

  • _hjMinimizedPolls
    • Hotjar cookie that is set once a user minimizes an on-site survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site
    • Expires: One year
  • _hjShownFeedbackMessage
    • Hotjar cookie that is set when a user minimizes or completes incoming feedback. This is done so that the incoming feedback will load as minimized immediately if the user navigates to another page where it is set to show
    • Expires: One year

Cookies that are used for website measurement

We use Google Analytics software (Universal Analytics) to collect anonymised information about how you use Bury.gov.uk. We do this to help make sure the site is meeting the needs of its users and to help us make improvements to the site.

These store information about:

  • how you got to the site
  • the pages you visit on Bury.gov.uk and how long you spend on them
  • what you click on while you're visiting the site

We don't collect or store your personal information (for example your name or address) so this information can't be used to identify who you are.

Cookie details:

  • _ga
    • This helps us count how many people visit, by tracking if you've visited before
    • Expires: Two years
  • _gid
    • This helps us count how many people visit, by tracking if you've visited before
    • Expires: 24 hours
  • _gat or _gat_gtag_UA_
    • Used to manage the rate at which page view requests are made
    • Expires: 10 minutes
  • nmstat
    • This cookie name is associated with the website analytics service provided by SiteImprove. It enables site owners to gather usage statistics about their websites
    • Expires: Two years
  • 1P_JAR
    • This cookie carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the website
    • Expires: One month
  • NID
    • Contains a unique ID Google uses to remember your preferences and other information, such as your preferred language (e.g. English), how many search results you wish to have shown per page (e.g. 10 or 20), and whether or not you wish to have Google's SafeSearch filter turned on
    • Expires: Six months
  • CONSENT
    • This cookie carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the website. Also used when when viewing some embedded YouTube videos
    • Expires: 18 years
  • VISITOR_INFO1_LIVE
    • This cookie is set by Youtube to keep track of user preferences for Youtube videos embedded in sites. It can also determine whether the website visitor is using the latest or older versions of the YouTube interface
    • Expires: Nine months
  • IDE
    • Used when playing some YouTube videos. Doubleclick is Googles real time bidding advertising exchange
    • Expires: One year
  • __cfduid
    • Used by SiteImprove software we use for in-house analytics. Cookie associated with sites using CloudFlare, used to speed up page load times. According to CloudFlare it is used to override any security restrictions based on the IP address the visitor is coming from. It does not contain any user identification information
    • Expires: One month
  • siteimproveses
    • Session cookie used by SiteImprove software we use for in-house analytics
    • Expires: When you close your browser
  • AWSELB
    • This cookie name is associated with the Amazon Web Services Elastic Load Balancing functionality for routing client request on the server
    • Expires: Unknown
  • _hjSessionUser{site_id}
    • Hotjar cookie that is set when a user 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
    • Expires: One year
  • _hjSession{site_id}
    • A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session
    • Expires: 30 minutes
  • _hjSessionTooLarge
    • Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit
    • Expires: When you close your browser
  • _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
    • Expires: When you close your browser
  • _hjSessionResumed
    • A cookie that is set when a session or recording is reconnected to Hotjar servers after a break in connection
    • Expires: When you close your browser
  • _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
    • Expires: One year
  • _hjRecordingLastActivity
    • This should be found in session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records)
    • Expires: When you close your browser
  • _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 this cookie for different URL substring alternatives until it fails. After this check, the cookie is removed
    • Expires: When you close your browser
  • _hjUserAttributesHash
    • User attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated
    • Expires: When you close your browser
  • _hjCachedUserAttributes
    • Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar feedback tool, but the cookie will be used regardless of whether a feedback tool is present
    • Expires: When you close your browser
  • _hjLocalStorageTest
    • This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in this cookie has no expiration time, but it is deleted almost immediately after it is created
    • Expires: Under 100 miliseconds
  • _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
    • Expires: 30 minutes
  • _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
    • Expires: 30 minutes
  • _hjAbsoluteSessionInProgress
    • This cookie is used to detect the first pageview session of a user. This is a True or False flag set by the cookie
    • Expires: 30 minutes
  • _hjFirstSeen
    • This is set to identify a new user's first session. It stores a true or false value, indicating whether this was the first time Hotjar saw this user. It is used by recording filters to identify new user sessions
    • Expires: When you close your browser
  • _hjViewportId
    • This stores information about the user viewport such as size and dimensions
    • Expires: When you close your browser
  • _hjRecordingEnabled
    • This is added when a recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session
    • Expires: When you close your browser

Cookies that are used for website settings

These cookies do things like remember your preferences and the choices you make, to personalise your experience of using Bury.gov.uk.

For example, we might display a message on all Bury.gov.uk pages to tell you about an important event or situation. We'll save a cookie that will let us know if you've dismissed it so it won't be shown again unless it changes or is reset by us.

Cookie details:

  • hideMessage
    • Sometimes we set a site wide message for important announcements. This cookie is set when you opt to hide the message to stop it displaying every time you go on one of our web pages, unless the site message is amended or reset
    • Expires: Six months
  • _hjClosedSurveyInvites
    • Hotjar cookie that is set once a user interacts with an external link survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown
    • Expires: One year
  • _hjDonePolls
    • Hotjar cookie that is set once a user completes a survey using the on-site survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in
    • Expires: One year

Changing your settings

If you have selected not to accept all cookies, you may find that some parts of the web site may not work. You may need to change your settings.

Manage your cookie settings on Bury.gov.uk

Contact for Web team (technical)