cookies:
what, why and how

What are cookies?

A cookie, also known as an HTTP cookie, web cookie, or browser cookie, is a piece of data stored by a website on a user’s computer by a browser, and then subsequently sent back to the same website by the browser.


Why do we use them?

Cookies fulfil different roles. Some are required for site functionality, some allow us to analyse how our site is used and some are from third parties (i.e. Facebook).

Cookies make browsing websites more efficient, give the opportunity for advanced functionality and also allow our website team to analyse how the site is used (through Google Analytics for example).

A great example of a cookie at work is if you’ve ever visited an eCommerce site and put a product in your basket without completing the purchase. You may have returned a few days later to see the same item in your basket; it is the cookie on your computer that identifies to the website you have returned and re-populates your basket.


Why do we collect data on how visitors use our site?

Firstly, it’s important to point out we don’t collect any data that can identify a unique user or contact data on that person (unless of course you volunteer such information via the contact form for example).

We use Google Analytics to track how anonymous users make use of our site. The data we receive allows us to ensure our site remains easy to use, fully functional and gives users, such as yourself, the best possible experience.


Why do we need to outline our cookies and their use?

The ICO (Information Commissioner’s Office) and UK Government have begun to enforce the E-Privacy Directive. The E-Privacy Directive is an EU based directive aimed at privacy protection in a digital environment.

The directive is aimed at informing and educating web users on what cookies the websites they visit use and what they are for. The premise behind the directive is that users will have more control over their online privacy and gain a greater understanding of information collected (although we must point out that information collected on our site cannot be used to identify a single user).


What cookies we use?

As noted earlier, our cookies fall into three categories.  Those that are required for functionality, those that allow us to collate and analyse site usage statistics and those that are used by third parties (such as Facebook).

Below is a list of the cookies we use. Some of them have already been used to ensure you are able to use our site and read this page for example. If you would like to clear our cookies, please visit this website for a guide on how to do so.
 

Owner/Domain	Cookie Name	Expires	More Details
pixelbuilders.com	ASP.NET_SessionId	On site exit	This is a functionally required cookie that sets unique ID for your visit and expires when you leave the site
pixelbuilders.com	CMSPreferredCulture	325 days	This is a cookie used by the wesbite to determine the culture to display the site in
pixelbuilders.com	CMSPreferredUICulture	352 days	This is a cookie used by the website to determine the culture to display the User Interface in should you login
Facebook	c_user	30 days	This cookie is used by Facebook to check your User ID and allows you to 'Like' articles in our news section without logging in
Facebook	datr	690 days	The datr cookie is when a web browser accesses facebook.com (such as when you like an article), it helps Facebook identify suspicious login activity and keep users safe
Facebook	locale	6 days	Sets your country and language for any interactions with Facebook
Facebook	lu	690 days	On single user computers, Facebook use the ‘lu’ cookie to prefill your facebook e-mail address on the login screen if you have not explicitly logged out
Facebook	xs	30 days	This is a session cookie (similar to our own ASP.NET_SessionId) set by Facebook
Google Analytics	__utma	730 days	This cookie is used by Google Analytics to recognise a unique user
Google Analytics	__utmc	Date not set	This is a session cookie (similar to our own ASP.NET_SessionId) set by Google Analytics and helps us understand return/repeat visits
Twitter	auth_token_session	7255 days	Used by Twitter to identify authenticated users. Allowing you to tweet news stories from our site without logging in
Twitter	guest_id	643 days	Creates a guest ID for accessing Twitter functionality
Twitter	secure_session	7255 days	Used by Twitter to identify is a user is securly authenticated
Twitter & Google Analytics	__utma	729 days	This cookie is used by Google Analytics to recognise a unique user. Twitter in this instance are using Google Analytics for their site analysis too
Twitter & Google Analytics	__utmv	729 days	This cookie is used by Google Analytics and allows Twitter to report on custom variables in their reporting suite
Twitter & Google Analytics	__utmz	182 days	This cookie is used by Google Analytics to confirm the source of the visit to Twitter
YouTube	demographics	529 days	A tracking cookie used by YouTube to analyse usage
YouTube	HSID	3650 days	A session ID set by YouTube
YouTube	LOGIN_INFO	3649 days	This cookie is used by YouTube to validate an authenticated user
YouTube	PREF	3650 days	YouTube viewing preferences set by user
YouTube	SID	3650 days	A session ID set by YouTube
YouTube	VISITOR_INFO1_LIVE	233 days	This cookie is used by YouTube to store user preferences when viewing pages containing video content.

What if you don’t want to allow us to use cookies?

As noted earlier, you can clear the cookies on your browser by following instructions found here. You can also block cookies from our site, or any other site you visit, using your browser settings. Unfortunately, if you chose to take this approach you will no longer be able to view our website as a number of the cookies listed above are critical to the site’s usage.


Need more information?

If you’d like more information on cookies and the ICO’s directive, please visit the ICO site. Please also take time to read our website privacy policy that deals with other elements of online privacy.