This Cookies Notice explains how we use cookies to enhance visitors' experience of our Website and to track and optimise its performance.
It should be read alongside our Privacy Notice.
When we refer to 鈥渙ur website鈥� or 鈥渢his website鈥� we mean the webpages of www.maggies.org.
Use of cookies
We want to make access to our website and what we offer online easy, useful and reliable.
Sometimes this involves placing text files containing small amounts of information on your computer or mobile phone known as cookies when you visit our Website.
You can find more information about cookies at and (each of which is an external link).
These small pieces of information are used to improve online services for you and the operation of our Website through, for example:
- Enabling our Website to recognise your device (your computer, phone or tablet for example) so you don't have to give the same information several times during one task or session, like submitting a form.
- Recognising that you may already have given a username and password so you don't need to do it for every webpage you subsequently access on our Website.
- Measuring how many people are using our Website, and services made available through our Website, so they can be made easier to use and there's enough capacity to ensure they operate and respond efficiently.
You can view what cookies are stored on your computer, remove them or stop them being placed in the future through the web browser settings for each browser that you use to access the internet.
Note that the way in which you do this is different for different web browsers and devices. To find out how to do this for your device鈥檚 web browser, search for 鈥榗ookies鈥� in your browser鈥檚 help menu.
You should also be aware that some areas of our Website may not function if your web browser does not accept cookies.
If you wish to control the placing of cookies on your computer but still enable the full functionality of our Website, you could impose restrictions on the placing of cookies on your computer but make our Website a "trusted website" in your web browser. Again, the help menu in your web browser should tell you how to do this.
Cookies we use
13.1 SER (Google Analytics)
We use Google Analytics to measure the number of visitors we have to our Website and what content they use most. This helps us ensure that this Website continues to meet the needs of our visitors and they can find information quickly and easily. It does not identify individual users but measures the overall behaviour or our visitors.
Cookie names: _utma, _utmb, _utmc, _utmz
Expires: up to 2 years after visit so new and returning visitors can be distinguished
13.2 sIFR (or Scalable Inman Flash Replacement)
Our Website makes use of Flash to display fonts in the way that is intended by our Website even if the fonts aren鈥檛 necessarily installed on your computer. This cookie is set once the fonts are loaded to prevent the need to keep re-loading them on your computer.
Cookie name: sifrFetch
Expires: at end of browsing session
13.3 Sessions (JSESSID and User)
Session cookies are set once you have logged in with your username and password, so you don't have to do it for every web page you navigate to on our site. This information is stored as a random string of letters and numbers.
Cookie names: JSESSID, User
Expires: at end of browsing session
13.4 _hjIncludedInSample
From time to time we conduct tests (such as looking at different layouts) and see how people respond. We use this cookie to work out if you're included in these tests or not.
13.5 csrftoken (Our website editor)
This is used to make sure that any forms you submit on our site were really submitted by you rather that a script on another site.
13.6 django_language (Our website editor)
This is how we track the language that we serve our content to you in.
13.7 sessionid (Our website editor)
Our content management system (website) django session identifier.
13.8 surveyDone
This is used to determine if you have participated in one of our surveys.
13.9 JSESSION ID, SRV BROWSER - blog.maggies.org (Google Analytics)
This is used by our server to track which one of our server sent you the web page you are viewing
Cookie names: _utma, _utmb, _utmc, _utmz
14.0 HOTJAR
_hjClosedSurveyInvites (Hotjar)
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: 365 days
_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: 365 days
_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: 365 days
_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: 365 days
_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.
_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.
_hjSessionResumed
A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
_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: 365 days
_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).
_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.
_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.
_hjCachedUserAttributes
This cookie stores User 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.
_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_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
_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/False flag set by the cookie
Expires: 30 minutes
_hjFirstSeen
This is set to identify a new user鈥檚 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.
_hjViewportId
This stores information about the user viewport such as size and dimensions.
_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.