Skip to main content

This is a new service - your feedback (opens in a new tab) will help us to improve it.

Cookies

GOV.UK 'Apply for a Blue Badge' puts small files (known as 'cookies') on your computer.

Cookies are used to:

  • remember the details you have entered before you submit the application
  • remember the notifications you've seen so we don't show them again
  • measure how you use the website so it can be updated and improved based on your needs

Find out how to manage cookies

Essential cookies

Essential cookies keep your information secure while you use 'Manage Blue Badges'. We do not need to ask permission to use them.

Name Purpose Expires
JSESSIONID Used to remember the details you have entered before you submit the application 1 hour
cookie_policy Saves your cookie consent settings 1 year

Analytics cookies (optional)

Google Analytics

With your permission, we use Google Analytics to collect data about how you use 'Manage Blue Badges'. This information helps us to improve our service.

Google is not allowed to use or share our analytics data with anyone.

Google Analytics stores anonymised information about:

  • how you got to 'Manage Blue Badges'
  • the pages you visit on Notify and how long you spend on them
  • any errors you see while using 'Manage Blue Badges'
Name Purpose Expires
_ga We use Google Analytics software to collect information about how you use the site. We do this to help make sure the site is meeting the needs of its users and to help us make improvements. 2 years
_gid We use Google Analytics software to collect information about how you use the site. We do this to help make sure the site is meeting the needs of its users and to help us make improvements. 24 hours
_gat Used to manage the rate at which page view requests are made. 10 minutes

Hotjar

With your permission, we use Hotjar to collect data about how you use 'Apply for a Blue Badge'. This information helps us to improve our service.

Hotjar is not allowed to use or share our analytics data with anyone.

Hotjar stores anonymised information about:

  • how you interact with the pages on 'Apply for a Blue Badge'
  • the pages you visit on 'Apply for a Blue Badge' and how long you spend on them
  • which links you choose to click and what users do and don't like

For further details, please see the 'about Hotjar' section of Hotjar's support site.

Name Purpose Expires
_hjClosedSurveyInvites Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown. 365 days
_hjDonePolls Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in. 365 days
_hjMinimizedPolls Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site. 365 days
_hjDoneTestersWidgets Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in. 365 days
_hjIncludedInSample 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. 365 days
_hjShownFeedbackMessage This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show. 365 days
_hjid

Hotjar cookie. This cookie 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.

365 days
_hjRecordingLastActivity This should be found in sessionStorage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). Session
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 for different URL substring alternatives until it fails. After this check, the cookie is removed.

Session
_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. Session
_hjCachedUserAttributes This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. Session

Do you want to accept analytics cookies?