About
Our work
Evidence and data tools
Join the movement
1. What is a cookie?
A cookie is a small text file that is downloaded onto ‘terminal equipment’ (eg. your computer or your smartphone) when you access our website. They can be first or third party cookies. Cookies are used in order to make our website work and they also provide us with usage information plus allow our website to recognise your device and store some information about your preferences or past actions.
2. How does this website use cookies?
Our website uses necessary and optional cookies. Necessary cookies make our website work properly and provide core functionality such as security. Optional cookies help us to provide you with a good experience when you browse our website and also allows us to improve our website.
3. What types of cookies does this website use?
We use three types of cookies: necessary, analytical and functionality cookies. You can check for information about the cookies we use and why in the table below:
| Cookie name | Set by | Duration | Purpose |
|---|---|---|---|
| _gid | 1 day | This cookie stores information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form. | |
| _gat | 1 minute | This cookie throttles the request rate to limit the collection of data on high traffic sites. | |
| _ga | 2 years | This cookie is used to calculate visitor, session and campaign data and to keep track of site usage for the site's analytics report. This cookie stores information anonymously. | |
| __cfduid | CloudFare | 11 months | This cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application. |
| em_cdn_uid | cdn.embedly.com | 11 months | This cookie is used to measure the number of times an embedded element from a third party service has been used. |
| vuid | Vimeo | 2 years | This cookie is used to collect analytics tracking information. |
| muxData | Vimeo | 19 years | This cookie is used in context with a video-player, so that if the visitor is interrupted while viewing video content, the cookie remembers where to start the video when the visitor reloads the video. |
| intercom-id-[app_id] | Intercom | 9 months | This cookie is used to anonymously identify visitors. |
| intercom-session-[app_id] | Intercom | 1 week | This cookies identifies each unique browser session. This session cookie is refresed on each successful logged-in ping, extending it to 1 week from that moment. The user can access their conversations and have data communicated on logged out pages for 1 week, as long as the session isn't intentionally terminated with 'Intercom('shutdown'); which usually happens on logout. |
| _hjClosedSurveyInvites | Hotjar | 1 year | 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. |
| _hjDonePolls | Hotjar | 1 year | 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. |
| _hjMinimizedPolls | Hotjar | 1 year | 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. |
| _hjShownFeedbackMessage | Hotjar | 1 year | 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. |
| _hjSessionTooLarge | Hotjar | Session | 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 | Hotjar | Session | 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 | Hotjar | Session | A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection. |
| _hjid | Hotjar | 1 year | 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. |
| _hjRecordingLastActivity | Hotjar | Session | 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 | Hotjar | Session | 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 | Hotjar | Session | 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 | Hotjar | Session | 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 | Hotjar | Under 100ms | 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 | Hotjar | 30 mins | 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 | Hotjar | 30 mins | 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 | Hotjar | 30 mins | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
| _hjFirstSeen | Hotjar | Session | 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. |
| _hjViewportId | Hotjar | Session | This stores information about the user viewport such as size and dimensions. |
| _hjRecordingEnabled | Hotjar | Session | 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. |
4. How can I manage my cookies preferences?
You can change your cookie preferences at any time by clicking on the ‘manage cookies’ icon that you can find in the bottom right corner of our website, where you can adjust the available sliders to ‘On’ or ‘Off’, then clicking ‘Save and close’. You may need to refresh your page for your settings to take effect. Alternatively, most web browsers also allow you to control cookies through their settings. Find out how to manage cookies on popular browsers:
Google Chrome
Microsoft Edge
Mozilla Firefox
Microsoft Internet Explorer
Opera
Apple Safari
To find information relating to other browsers, please visit the browser developer's website.To opt out of being tracked by Google Analytics across all websites, visit http://tools.google.com/dlpage/gaoptout. Please, note this is only available for Microsoft Internet Explorer 11, Google Chrome, Mozilla Firefox, Apple Safari and Opera browsers.
5. Who should I contact if I have any questions about how this website uses cookies?
Please, find below our contact details:
Centre for Homelessness Impact
The Evidence Quarter
Floor 4, Albany House
94-96 Petty France
London
SW1H 9EA
Contact email: tech@homelessnessimpact.org
Contact telephone: (+44) (0)300 3020076
You can also contact our DPO:
Aphaia Ltd,
The Brew Eagle House,
163 City Rd,
London EC1V 1NR
Contact email: dpo@aphaia.co.uk
Contact telephone: (+44) (0)20 3917 4158
