Here is a list of cookies that we use on www.DofE.org. If you object to us automatically storing any of this data, please adjust your browser settings or clear your cache history following a visit to this site.
In common with most information-giving websites such as this, none of the data collected from your visit is used by us for any purpose other than to make subsequent visits by you quicker and easier. Therefore, in reality, this is simply a new legal process and you don’t actually need to do anything – your visit to this website will be as rewarding as ever.
The ICO updated their policy in January 2013.
ASP.NET_SESSIONID: The ASP.NET_SessionId is used by our server to identify you as a new visitor to the DofE.org website. Each visitor to the website is given a unique session id. This cookie will expire at the end of your browsing session. MINIMALLY INTRUSIVE (NO PERSONAL INFORMATION CAPTURED)
THIRD PARTY COOKIES
TWITTER.COM: The DofE.org website uses a Twitter feed, which allows us to pull in the official tweets from the DofE on Twitter. The direct integration with the DofE.org homepage or any other page on the DofE website will generate these cookies; these cookies are used to surface this content. Twitter will automatically create two cookies on your machine:
- The cookie “guest_id” – This cookie is used to identify you to twitter, if you do not have a twitter account or never accessed the twitter.com website directly then twitter will assign you a unique code to track your visit to the Twitter feed. Twitter has the ability to track surfing habits (on Tweet button enabled websites) of users that have no Twitter account and have never visited a Twitter website before. When using the same browser to create an account at Twitter afterward this collected data of the past can theoretically be linked to the freshly created profile. This cookie will expire in two years’ after creation. MODERATELY INTRUSIVE (USER IDENTIFIABLE INFORMATION CAPTURED)
- The cookie “k” – In order to show official DofE tweets on the DofE.org website, we need to use the official Twitter API. This API creates a cookie on your machine called “k”. This cookie contains the IP address of the visitor. This cookie will expire in one week after creation. MODERATELY INTRUSIVE (USER IDENTIFIABLE INFORMATION CAPTURED)
GOOGLE.COM: The DofE.org website uses Google Analytics to track and monitor visits to the DofE.org website. Google will automatically create several cookies on your machine in order for them to be able to successfully record your visit.
- The cookie “__utma” – Each unique browser that visits a page on the DofE.org website is provided with a unique ID, it is this cookie that stores this unique ID. This cookie will expire in two years’ after creation. MINIMALLY INTRUSIVE (NO PERSONAL INFORMATION CAPTURED)
- The cookies “__utmb” & “__utmc” – Google Analytics uses these two cookies to establish a session. These cookies will expire at the end of your browsing session. MINIMALLY INTRUSIVE (NO PERSONAL INFORMATION CAPTURED)
- The cookie “__utmz” – When you visit the DofE.org website via a search engine result, a direct link or an ad Google will store this referral information in this cookie. This cookie will expire in six months after creation. MINIMALLY INTRUSIVE (NO PERSONAL INFORMATION CAPTURED) The DofE.org website also uses Google Custom Site search to allow visitors to use Google Search index to find content inside the DofE website. If you perform a search a cookie will automatically be created.
- The cookie “PREF” – This cookie is used to remember you (the visitors) basic preferences such as whether you want search results in English or whether you have opted for a SafeSearch setting. This cookie will expire in two years’ after creation. MINIMALLY INTRUSIVE (NO PERSONAL INFORMATION CAPTURED)
SAGEPAY.COM: We use the SagePay as our payment gateway to allow you to make donations on the DofE.org website. When you start the process of making a donation you start on the DofE website, you will then get transferred to the SagePay website to make your secure payment and then you will be redirected automatically back to the DofE website. When you leave the DofE website or go to the payment gateway SagePay will automatically create two cookies on your machine.
- The cookie “JSESSIONID” – Much like the ASP.NET_SessionId, this cookie will assign you a unique ID so it can differentiate you from other users of the payment gateway. These cookies will expire at the end of your browsing session. MINIMALLY INTRUSIVE (NO PERSONAL INFORMATION CAPTURED)
- The cookie “NSC_wjq-tbhfqbz-dpn” – This cookie is used to store the session identifier of your SagePay Session. This cookie will expire at the end of your browsing session. MINIMALLY INTRUSIVE (NO PERSONAL INFORMATION CAPTURED)
What are they?
Cookies are small files that allow a website to recognise and track users. They are grouped into three overlapping groups:
Session cookies: Files that allow a site to link the actions of a visitor during a single browser session. These might be used by an internet bank or webmail service. They are not stored long term and are considered “less privacy intrusive” than persistent cookies.
Persistent cookies: These remain on the user’s device between sessions and allow one or several sites to remember details about the visitor. They may be used by marketers to target advertising or to avoid the user having to provide a password each visit.
First and third-party cookies: A cookie is classed as being first-party if it is set by the site being visited. It might be used to study how people navigate a site. It is classed as third-party if it is issued by a different server to that of the domain being visited. It could be used to trigger a banner advert based on the visitor’s viewing habits.
www.aboutcookies.org/ – This web site explains how you can delete and control the cookies that are stored on your computer.