This document is copyright protected and we actively use Copyscape to ensure that this documentation has not been redistributed without the prior consent of Our IT Department Ltd.
What is a cookie?
A cookie (also known as an HTTP cookie, web cookie, or browser cookie) is a small piece of information that a website transfers to your computer’s hard disk so that the website can ‘remember’ things about your previous visits and current visits. Typically, aa cookie will contain the following information:
- the name of the domain from which the cookie has come
- the “lifetime” of the cookie
- a value, usually a randomly generated unique number.
You can learn more about cookies on this resource page – allaboutcookies.org/manage-cookies/index.html
Cookies are used on this website for Traffic Analysis. The cookies collect information in an anonymous form; this information typically includes the following:
- The page URL
- The page title
- User agent
- IP address
- Screen resolution
- Tracking cookie
Cookies set by Google Analytics:
__utma – This cookie is typically written to the browser upon the first visit to your site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits your site, a new __utma cookie is written with a different unique ID. This cookie is used to determine unique visitors to your site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that Google Analytics uses to ensure both the validity and accessibility of the cookie as an extra security measure. Expires 2 years from set/update.
__utmb – This cookie is used to establish and continue a user session with your site. When a user views a page on your site, the Google Analytics code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on your site, this cookie is updated to expire in 30 minutes, thus continuing a single session for as long as user activity continues within 30-minute intervals. This cookie expires when a user pauses on a page on your site for longer than 30 minutes. You can modify the default length of a user session with the _setSessionCookieTimeout() method. Expires 30 minutes from set/update.
__utmc – This cookie is no longer used by the ga.js tracking code to determine session status. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether or not to establish a new session for the user. For backwards compatibility purposes with sites still using the urchin.js tracking code, this cookie will continue to be written and will expire when the user exits the browser. However, if you are debugging your site tracking and you use the ga.js tracking code, you should not interpret the existence of this cookie in relation to a new or expired session. Expiration not set.
__utmz – This cookie stores the type of referral used by the visitor to reach your site, whether via a direct method, a referring link, a website search, or a campaign such as an ad or an email link. It is used to calculate search engine traffic, ad campaigns and page navigation within your own site. The cookie is updated with each page view to your site. Expires 6 months from set/update.
__utmv – This cookie is not normally present in a default configuration of the tracking code. The __utmv cookie passes the information provided via the _setVar() method, which you use to create a custom user segment. This string is then passed to the Analytics servers in the GIF request URL via the utmcc parameter. This cookie is only written if you have added the _setVar() method for the tracking code on your website page. Expires 2 years from set/update.
__utmx – This cookie is used by Website Optimizer and only set when the Website Optimizer tracking code is installed and correctly configured for your pages. When the optimizer script executes, this cookie stores the variation this visitor is assigned to for each experiment, so the visitor has a consistent experience on your site. See the Website Optimizer Help Center for more information. Expires 2 years from set/update
Cookies set by Get Clicky:
Jsuid – This is a random number that is generated by the Code the first time someone visits a web site with the Code installed. Its sole purpose is to better identify new and unique visitors to a web site. The value of this cookie is sent to the Service for every event logged. The value of this cookie will also be set as a third party cookie with the name of “cluid” if such a cookie does not exist. The purpose of this is for web sites with multiple domains and who want to track visitor sessions across multiple domains, which is not possible with first party cookies.
first_pv_[site_id] – This is a session cookie that is set on the first page view of any visit. Its purpose is so that certain parts of the Code only fire on the first page view, making it faster and more efficient.
unpoco_[site_id] – The Code sends “pings” when a visitor sits on a single page. This allows the Service to more accurately track “time on site” values. Because this feature uses a lot of extra bandwidth, it requires a paid account. For non-paid accounts, this cookie is set to tell the Code not to send these pings. This cookie expires after 24 hours but will be set again upon future visits by the same visitor
no_tracky_[site_id] – When a site stops using the Service, it is quite common for the web master to leave the code installed, which is against the Terms of service. For high traffic sites, this can use a lot of extra bandwidth and CPU resources on our servers. This cookie is set whenever data is sent in for a site that is disabled. It tells our tracking code to stop sending data to us. This cookie expires after 24 hours but will be set again upon future visits by the same visitor, until the Code is removed from the offending web site..
clicky_olark – This is a session cookie that gets set if you are using Olark chat in combination with Clicky. It contains Olark’s unique ID information for the visitor. This cookie is sent to the Service, which is needed in order to initiate the chat process within Spy.
How to enable and Disable Cookies
Your internet browser can be configured to accept and reject all cookies, or notify you when a cookie is set. Each browser is different; please see the following guides below on how to change the security settings of the most common internet browsers:
Internet Explorer. Version 6 +.
1. Select ‘Tools’, then ‘Internet Options’.
2. Click on the “Privacy” tab,
3. The default setting is medium. Move the slider to determine your setting of choice.
You can also click on “Advanced” for specialised cookie settings.
If you are using Internet Explorer version 5.0:
1. Select ‘Tools’, then ‘Internet Options’
2. Click on the ‘Security’ tab
3. Click on ‘Internet’, then ‘Custom Level’
4. Navigate to ‘Cookies’ and choose one of the two options
1. Select ‘Tools’, then ‘Internet’ Options
2. Click the “Privacy” tab
3. Check or uncheck the option – ‘Accept cookies from sites’
NOTE – You can also click on “Exceptions” for advanced cookie options.
If you are using Netscape version 9:
1. On the task bar, click ‘Tools’ and then ‘Options’
2. Click on ‘Privacy’
3. Under ‘Cookies’, set the cookie acceptance policy to your desired level
If you are using Opera.
1. To enable or disable cookies, select ‘settings’
2. Select ‘quick preferences’
3. Check or uncheck ‘enable cookies’
To delete cookies,
1. select ‘settings’ then ‘preferences’
2. click ‘advanced’ then ‘cookies’
3. check ‘delete new cookies when exiting opera’