What are Cookies?
Cookies are small files saved on your phone, tablet, or computer by websites that you visit. They are widely used to make websites work, or work more efficiently, as well as to provide information to the owners of the site. The information stored in cookies is used to make websites work or contains things about how you use the website. For example, that you have acknowledged a pop-up or the pages you visit.
Cookies are not viruses or computer programs. They are very small text files, so they do not take up much space on your computer or mobile device by websites that you visit. Most modern websites use them to enable functionality, to help the site work more efficiently, or to provide information about the use of the site to the owners.
This statement refers to ‘cookies’ but covers similar browser storage technologies, such as HTML local storage. Our cookies do not contain any personal information about you and do not hold any information about which sites you visited before you came here.
How we use Cookies
We use cookies to:
- make our website work, for example by keeping it secure
- measure how you use our website, for example, which links you click on.
Each cookie listed shows the cookie name, type, duration, and purpose.
We use cookies only for the purpose described.
The following cookies may be used on this site:
Essential Cookies
These essential, or ‘strictly necessary’, cookies enable basic functions like page navigation and access to secure areas of the website.
Our website and services cannot function properly without these cookies, so we do not provide a way to manage them. They can only be blocked or deleted by changing your browser preferences, as described in the Managing Cookies section in this statement.
| Cookie | Service | Purpose | Expiration |
|---|---|---|---|
| cfide | Mura | Identifying the code of the client's current session. It allows the server to identify the client from whom it receives the calls. | 1 year 1 month 6 days |
| cftoken | Mura | To keep track of user sessions on the site and identify your user session. | 1 year 1 month 6 days |
| MuraCMSAffinity | Mura | Manages sticky sessions in a load-balanced environment, to keep a user's session tied to a single server. | End of session |
| MuraCMSAffinityCORS | Mura | Manages sticky sessions in a load-balanced environment, to keep a user's session tied to a single server. | End of session |
| MXP_TRACKINGID | Mura | This relates to the suite of features with MXP, which gives the ability for users to have a personalized experience while on that mura site, based on selections either made by the user or the site. This cookie enables the site to persist an experience unique to that decision. If you are not leveraging MXP, this cookie serves no purpose. | 1 year 1 month 6 days |
| MURA_UPC | Mura |
This is the output cache, it allows for requests to use the proxy cache - our goal is to put a proxy in front of each API call to Mura, this tells whether or not it should be used or not. |
1 year 1 month 6 days |
| rb | Mura | Is a resource bundle cookie that should only affect when you are logged into admin. | 1 year 1 month 6 days |
| RB | Mura | Is a resource bundle cookie that should only affect when you are logged into admin. | 1 year 1 month 6 days |
| FETDISPLAY | Mura | Is a toolbar on the front end, where hitting the logo does or doesn't show it. Again, this only affects you when you are logged into admin. | 1 year 1 month 6 days |
| MURA_OSC | Mura |
Allows the user to cache or not cache. This uniquely sets when you actually do use the cache, so the cache is relevant. |
1 year 1 month 6 days |
| infobanner* | Mura | Information banner is a module that may be added to the site, when dismissed a cookie is created to indicate it should not appear again for the duration of the session. | End of session |
| _rspkrLoadCore | ReadSpeaker | Set after the service has been activated, ie when you have interacted with the player. An initiation cookie that determines whether or not to load the scripts on the page load. | End of session |
| ReadSpeakerSettings | ReadSpeaker | Set if you change a setting in the settings menu. | 4 days |
Third-Party Cookies
We embed some content on our website from external providers. These providers may set cookies, known as ‘third party’ cookies.
We do not control these cookies and cannot prevent these sites or domains from collecting information on your use of this content. Check the relevant third-party website for more information about them and how to opt out:
| Service | Usage | Information |
|---|---|---|
| SoundCloud | Embedding audio clips and podcasts | SoundCloud privacy policy SoundCloud cookie policy |
| X (Twitter) | Embedding tweets and timelines | X's use of cookies X's privacy policy X's privacy controls for personalised ads |
| YouTube | Embedding videos | Google privacy policy Ad settings on Google |
| Canva | Embedding social media posts, presentations, posters, videos & logos | Canva privacy policy Canva cookie policy |
Website Usage Cookies
We use tools such as Google Analytics, Google Optimize and Hotjar to help us anonymously measure how you use our websites. This allows us to make improvements based on our users' needs.
These tools set cookies that store anonymised information about how you got to the site, and how you interact with the site. We do not allow these tools to use or share the data about how you use this site and all data stored is anonymised.
Website usage cookies can be managed on this website, as described in the managing cookies section in this statement. Each of the services we use to record website usage provides a way to opt out of cookies.
Google Analytics
We use Google Analytics for usage analytics like page views and link clicks.
You can opt out of Google Analytics cookies. View Google's privacy policy for more information.
| Cookie | Purpose | Expiration |
|---|---|---|
| _ga | Used to distinguish users. | 2 years |
| _ga_ | Used to distinguish users in Google Analytics 4. If Google Analytics 4 is deployed via Google Tag Manager, this cookie will be named _ga_<property-id>. | 2 months |
| _gat | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>. | 1 minute |
| _gid | Used to distinguish users. | 1 day |
| _tempCid | Copy of _ga used to track successful sign-in from the server rather than client side. | 30 minutes |
Hotjar
We use Hotjar for behaviour analysis, heatmaps, clickmaps, usage recordings, polls and surveys.
You can opt out of Hotjar cookies. View Hotjar's privacy policy for more information.
| Cookie | Purpose | Expiration |
|---|---|---|
| _hjAbsoluteSessionInProgress | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. | 30 minutes |
| _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. | End of session |
| _hjClosedSurveyInvites | This cookie is set once a visitor 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. | 1 year |
| _hjDonePolls | This cookie is set once a visitor 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. | 1 year |
| _hjid | 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 behaviour in subsequent visits to the same site will be attributed to the same user ID. | 1 year |
| _hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by the site's pageview limit. | 30 minutes |
| _hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by the site's daily session limit. | 30 minutes |
| _hjLocalStorageTest | This cookie is used to check if the Hotjar tracking script can use local storage. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. | Under 100ms |
| _hjMinimizedPolls | This cookie is set once a visitor minimises an On-site Survey widget. It is used to ensure that the widget stays minimised when the visitor navigates through your site. | 1 year |
| _hjRecordingLastActivity | This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records). | End of session |
| _hjShownFeedbackMessage | This cookie is set when a visitor minimises or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimised immediately if the visitor navigates to another page where it is set to show. | 1 year |
| _hjTLDTest | When the script executes, Hotjar tries to determine the most generic cookie path to use instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, Hotjar tries to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. | End of 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. | End of session |
Marketing and Advertising Cookies
We may use Google Ads, LinkedIn and Facebook to show adverts that promote our services, events and content. These adverts are shown on external websites, which are not owned or operated by us.
Google Ads, LinkedIn and Facebook use cookies to:
- help measure how many times people click on adverts and interact with our website
- perform functions like preventing the same advert from continuously reappearing
- help show you relevant adverts, based on your interests and past visits to our website.
Marketing and advertising cookies can be managed on this website, as described in the managing cookies section in this statement. You can also control advert personalisation on other websites using Your Online Choices.
You can manage your advertising preferences on Facebook. View Facebook's privacy policy for more information.
| Cookie | Purpose | Expiration |
|---|---|---|
| _fbp | Used to identify users across webpages where Facebook pixel is installed. The pixel automatically saves a unique identifier to an _fbp cookie for the website domain if one does not already exist. | 3 months |
| _fbc | Used to identify the link users initially clicked across webpages where Facebook pixel is installed. The link ad on Facebook sometimes includes a fbclid query parameter. When the user lands the pixel automatically saves the fbclid query parameter to an _fbc cookie for that website domain. | 3 months |
Managing Cookies
Find out how to manage cookies on popular browsers:
To find information relating to other browsers, visit the browser developer's website.
Further Information
If you have any questions about our use of cookies or other technologies, Please contact us. We welcome calls and correspondence in Welsh. We will respond in Welsh without delay.
Statement Updates
