“Us” means READ Media
“Website” means the website operated by Us located.
and “You” refers to any user of the Website.
1.2 Words such as “We”, “Our” and “Your” shall be construed as referring to the relevant person in accordance with this clause.
2.3 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.
2.4 On our Website, We use the following cookies:
- Strictly necessary (first-party) cookies: These are cookies that are required for the operation of the Website. They include, for example, cookies that enable You to log into secure areas of the Website, use a shopping cart or make use of e-billing services.
- Functionality (first-party) cookies: These are used to recognise You when You return to the Website. This enables Us to personalise Our content for You, greet You by name and remember Your preferences (for example, Your choice of language or region).
- Analytical/performance (third-party) cookies: They allow Us to recognise and count the number of visitors and to see how visitors move around the Website when they are using it. This helps Us to improve the way the Website works.
2.5 More information about the individual third-party cookies We use, and the purposes for which We use them, are as follows:
The following cookies allow Us to recognise and count the number of visitors and to see how visitors move around the Website when they are using it. This helps Us to improve the way the Website works.
Purpose: To allow us to better understand the kind of people who visit the website and what content they’re reading. This allows use to make better decisions about content and offers. Occasionally, we will compile aggregate statistics about the number of visitors this site receives, and browsers being used. No personally identifying data is included in this type of reporting.
|Cookie Name||Expiration Time||Description|
||2 years||Used to distinguish users.|
||24 hours||Used to distinguish users.|
||1 minute||Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named
More information: All activity falls within the bounds of the Google Analytics Terms of Service.
|_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
|_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|
|_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 immediately after creating it so the expected storage time is under 100ms.||N/A|
More information: For further details, please see the ‘about Hotjar’ section of Hotjar’s support site.
WP Cerber Security & Antispam
Purpose: To protect the website from hackers, cyber criminals, spammers and bots. These cookies do not store any personal identifiers.
2.7 You can block cookies by activating the setting on Your browser that allows You to refuse the setting of all or some cookies. However, if You use Your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of the Website.
2.8 Except for essential cookies, all cookies will expire after 7 days.