Cookie Policy
Last updated June 02, 2020
Like most websites we use ‘cookies’ to collect anonymous statistics about how people use the site, and to help us keep it relevant for the user. Cookies ‘remember’ bits of information from your visit to the site.
What are cookies?
A cookie is a simple text file that’s stored on your computer or mobile device by a website’s server. Only that server can retrieve or read the contents of that cookie. Each cookie is unique to your web browser. So if we put a cookie on your computer, it can’t be read by any other website. Cookies are widely used by website owners in order to make their websites work, or to work more efficiently, as well as to provide reporting information.
Cookies set by the website owner are called “first party cookies”. Cookies set by parties other than the website owner are called “third party cookies”. Third party cookies enable third party features or functionality to be provided on or through the website (e.g. like advertising, interactive content and analytics). The parties that set these third party cookies can recognise your computer both when it visits the website in question and also when it visits certain other websites.
Why do we use cookies?
We use first and third party cookies for several reasons. Some cookies are required for technical reasons in order for our Websites to operate, and we refer to these as “essential” or “strictly necessary” cookies. Other cookies also enable us to track and target the interests of our users to enhance the experience on our website. Third parties serve cookies through our Websites for advertising, analytics and other purposes.
We use two types of cookie:
- ‘Session cookies’ last as long as your current visit to the site, or for up to a limited amount of time if you keep the site open without using it. They mean you don’t have to keep re-submitting information as you move through the site or carry out transactions.
- ‘Persistent cookies’ remember information from previous visits, for example names and details for online forms. They are used to collect anonymous statistics about how many people use the site, and to maintain any settings (such as accessibility) you have changed.
How to disable Cookies
If you do not want to accept cookies, you can change your browser settings so that cookies are not accepted. If you do this, please be aware that you may lose some of the functionality of this website.
The following links provide information on how to modify the cookies settings on some popular browsers:
Chrome
Safari
Firefox
Internet Explorer
To opt out of being tracked by Google Analytics across all websites, visit http://tools.google.com/dlpage/gaoptout.
Further Information
For further information about cookies and how to disable them please go to: www.aboutcookies.org or www.allaboutcookies.org.
Categories of Cookies
The specific types of first and third party cookies served through our Websites and the purposes they perform are described below:
Essential website cookies:
These cookies are strictly necessary to provide you with services available through our Websites and to use some of its features, such as access to secure areas.
Analytics and customisation cookies:
These cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customize our Websites for you.
Advertising cookies:
These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.
Functionality cookies:
These cookies enhance the functionality of a website, but are not classed as strictly essential for the website to work.
STRICTLY NECESSARY COOKIES |
||||
---|---|---|---|---|
SITE/DOMAIN | SET BY | COOKIE NAME | EXPIRES | PURPOSE |
https://www.ioutheatre.org/ | UK Cookie Consent | catAccCookies |
90 days | This cookie is set by the UK cookie consent plugin to record that a users has accepted the site uses cookies. |
More information on Uk Cookie Consent | ||||
https://www.ioutheatre.org/ | WordPress | wordpress_test_cookie |
End of session | Used on sites built with WordPress. Tests whether or not the browser has cookies enabled |
wordpress_logged_in_[hash] |
2 weeks | After login, wordpress sets the wordpress_logged_in_[hash] cookie, which indicates when you’re logged in, and who you are, for most interface use. |
||
wp-settings-[UID] wp-settings-{time}-[UID] |
1 year 1 year |
WordPress also sets a few wp-settings-{time}-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface. |
||
More info on WordPress Cookies | ||||
https://www.ioutheatre.org/ | PHP Session ID | PHPSESSID |
End of browser session | The PHPSESSID cookie is native to PHP and enables websites to store serialised state data. It is used to establish a user session and to pass state data via a temporary cookie, which is commonly referred to as a session cookie. |
https://www.ioutheatre.org/ | Wordfence | wfwaf-authcookie-(hash) |
End of Session | This cookie is used by the Wordfence firewall to perform a capability check of the current user before WordPress has been loaded. This is only set for users that are able to log into WordPress. This cookie allows the Wordfence firewall to detect logged in users and allow them increased access. It also allows Wordfence to detect non-logged in users and restrict their access to secure areas. The cookie also lets the firewall know what level of access a visitor has to help the firewall make smart decisions about who to allow and who to block. |
wf_loginalerted_(hash) |
End of Session | This cookie is used to notify the Wordfence admin when an administrator logs in from a new device or location. This is only set for administrators. This cookie helps site owners know whether there has been an admin login from a new device or location. | ||
wfCBLBypass |
Unknown | Wordfence offers a feature for a site visitor to bypass country blocking by accessing a hidden URL. This cookie helps track who should be allowed to bypass country blocking. When a hidden URL defined by the site admin is visited, this cookie is set to verify the user can access the site from a country restricted through country blocking. This will be set for anyone who knows the URL that allows bypass of standard country blocking. This cookie is not set for anyone who does not know the hidden URL to bypass country blocking. This cookie gives site owners a way to allow certain users from blocked countries, even though their country has been blocked. | ||
More information on WordFence Cookies |
ANALYTICAL COOKIES |
||||
---|---|---|---|---|
SITE/DOMAIN | SET BY | COOKIE NAME | EXPIRES | PURPOSE |
https://www.ioutheatre.org/ | Google Analytics | |||
These cookies are used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in an anonymous form, including the number of visitors to the website and blog, where visitors have come to the website from and the pages they visited
More information on Google Analytics Cookie Usage |
||||
_ga |
2 years | Used to distinguish users. | ||
_gid |
24 hours | Used to distinguish users. | ||
_gat |
1 minute | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_. |
||
The following Cookies are only used if you use Google Analytics Content Experiments
More information on Google Analytics Cookie Usage |
||||
_ |
18 months | Used to determine a user’s inclusion in an experiment. | ||
_ |
18 months | Used to determine the expiry of experiments a user has been included in. |
FUNCTIONALITY COOKIES |
||||
---|---|---|---|---|
SITE/DOMAIN | SET BY | COOKIE NAME | EXPIRES | PURPOSE |
vimeo.com | Vimeo | vuid |
1 minute | This first party cookie created by Vimeo is used to assign a Vimeo Analytics unique id. |
player |
1 minute | This first party cookie created by Vimeo is used to remember user’s player mode preferences. | ||
More info on Vimeo Cookies |
ADVERTISING COOKIES |
||||
---|---|---|---|---|
SITE/DOMAIN | SET BY | COOKIE NAME | EXPIRES | PURPOSE |
youtube.com | YouTube | |||
We embed videos from our YouTube channel using YouTube’s privacy-enhanced mode. This mode may set cookies on your computer once you click on the YouTube video player, but YouTube will not store personally-identifiable cookie information for playbacks of embedded videos using the privacy-enhanced mode. To find out more please visit YouTube’s embedding videos information page. | ||||
visitor_info1_live |
8 months | Tries to estimate the users’ bandwidth on pages with integrated YouTube videos. | ||
ysc |
Expires at the end of your session | This cookie is set by the YouTube video service and aims to limit repeat advertising and deliver more relevant advertising to you. | ||
pref |
8 months | Registers a unique ID that is used by Google to keep statistics of how the visitor uses YouTube videos across different websites. | ||
_ |
10 minutes | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing _ cookies exists. The cookie is updated every time data is sent to Google Analytics. |
||
_ |
30 mins from set/update | Used to throttle request rate. | ||
_ |
End of browser session | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the _ cookie to determine whether the user was in a new session/visit. |
||
_ |
6 months from set/update | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. | ||
_ |
2 years from set/update | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _ method. The cookie is updated every time data is sent to Google Analytics. |
||
More info on YouTube Cookies More information on YouTube embedding |