This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Cookie Policy
OVERVIEW
A ‘cookie’ is a text-only string of information that a website transfers to the cookie file of the browser on your computer’s hard disk so that the website can remember specific information about your use of the website. This can include which pages you have visited, choices you have made from menus and the time and date of your visit. Importantly, cookies enable users to set accessibility preferences on the Wren website without having to register or log in. None of the cookies used on the Wren website are regarded as being intrusive.
Most internet software browsers are initially set to accept cookies. However, you have the ability to disable cookies if you wish, generally through changing the browsing settings. Please refer to the Help section on your browser. If cookies are disabled it may mean that not all services of a website might be available.
We may collect information about your computer, including where available your IP (Internet Protocol) address, operating system and browser type to help diagnose problems with our server, and to administer the website. An IP address is a number that is assigned to your computer when you use the Internet. This information does not contain any personally identifiable information about you.
This website uses Google Analytics. Google Analytics uses cookies to help us see how many users come to our website and the pages that generate most interest. This information is useful when we come to redesign the website to ensure the Wren website continues to be an effective source of information. Google Analytics cookies do not enable any website user to be individually identified and these cookies will only be used for website design purposes.
By using this website, you consent to the use of the Google Analytics cookies and IP address collection in the manner and for the purposes set out above.
We do not use any of the following cookies:
- Advertising cookies – These are set on the website by ads such as banners
- Flash cookies – These are set by Flash objects to track behaviour on site
- Marketing cookies – These are set by promotional activities such as email campaigns.
DETAIL ABOUT COOKIES WE USE
A list of the cookies used on the Wren website and information about what they are used for are contained in the tables below. The Wren website is maintained using a Content Management System (CMS).
The Cookie Privacy Acceptance Cookie:
This cookie is used to record if a user has accepted the use of cookies on the Wren website.
To withdraw your consent after accepting this cookie, delete the CookiesAccepted cookie.
Google Analytics Cookies:
| Cookie Name | Expiry | Data Stored | Purpose |
| __utma | 730 days | Initially a Unique Client ID is stored; subsequently, the number of visits, and the time of the first, previous and current visit. | When users visit the Wren website for the first time, the __utma cookie is used to identify each unique visitor, as determined by the user’s PC.
The __utma cookie is subsequently used to track user visits and activity on the Wren website over time. |
| __utmb | 30 minutes | Duration of visit | The __utmb cookie is used to establish and maintain a single user session, and to measure the duration of each session.
The __utmb cookie will remain in place whilst the user is active on the Wren website. If the user is inactive for 30 minutes, the cookie will expire and the session will be determined as completed for analytics purposes. |
| __utmc | 1 session | Duration of visit | The __utmc cookie works in conjunction with the __utmb cookie to establish and maintain a single session. |
| __utmz | 180 days | Referral data: where the user came from. | The __utmz cookie is used to determine the “referral type” i.e. the path the user took to get to the Wren website. For example, whether the user entered the Wren URL directly into their browser, or they did a Google Search, or they clicked on a link on another website. |
CMS Cookies: All Users
| Cookie Name | Expiry | Data Stored | Purpose |
| PHPSESSID | 1 session | Unique Session ID | On the Wren website the PHPSESSID cookie is used to establish a user website session and to pass status data via a temporary cookie, which is commonly referred to as a session cookie. As the PHPSESSID cookie has no timed expiry, it disappears when the user website session is closed.
The use of the PHPSESSID cookie is central to the working of the CMS used by the Wren website e.g.it is used for initiating a session when a web page is requested and for recording the page viewing history. |
CMS Cookies: Registered Users only
| Cookie Name | Expiry | Data Stored | Purpose |
| PastMember | 90 days | Value = 0 or 1 depending upon whether the user is registered or not | This cookie is created at first registration and may also be created at a subsequent login. It indicates that a user who is, or was, logged in is a registered user of the Wren website.
The function that sets this cookie also updates the LastVisited timestamp in the registered user‘s record. As the cookie has a 90 day duration, if more than 90 days have elapsed between registration and login or between logins, the cookie will disappear and be recreated the next time the user logs in. |
| alc_enc | 90 days | Encrypted User ID | This cookie is used for automatic login. This occurs if the user Wren website session is closed unexpectedly or by accident and then re-opened. If the user was logged in at the time that the session closed, they get logged in again automatically.
This cookie is created if the “remember me” checkbox is checked at login. |
| $login_marker_cookie | 1 session | Value = 1 | This is not an actual cookie, but a placeholder that works in conjunction with the session cookie.
The CMS uses this code to set a session cookie to “1” whenever a user logs in. This allows the Wren web server program to detect whether a user is logged in or not and alters behaviour accordingly. |
Information updated on 23rd May 2013