Here is information about how Cookies are used in the Britain from Above website...
Cookies are files that store information on your hard drive or browser which means Britain from Above can recognise that you have visited the website before. They make it easier for you to maintain your preferences on the website, and by seeing how you use them, we can tailor them around your preferences and measure usability of the site.
sess* - session cookie (category - strictly necessary)
Britain from Above sets a session cookie (sess*) when a user comes to the website. The cookie works by setting a key which allows the website to see how users interact with the webpages including their route through the site. This cookie is also necessary to indicate when a user is logged in. knowing whether a user is logged in or no allows the user to remain logged in as they move through the site and also means that pages are tailored/personalised for the user. This also lets the user add and store favourites to their account which they can access when logging into the site at a later date. The session cookie also allows contributions to be set against users so the site can display what contributions were made by which users. In short, the general functionality of the site for logged in users who wish to contribute and engage with the site depends on the session cookies being set.
Social Media related cookies (category - functionality)
Each Aerofilms image in the Britain from Above site comes with a Facebook "Like" button, a Twitter tweet button as well as a Google+ share button which allows the user to upload the Aerofilms image, image title and the Britain from Above URL for that image to these social media sites. Third party cookies are set in these cases, so the user is able to share the images socially if they do choose.
_utma,_utmb,_utmc,_utmz Google Analytics cookies (category - performance)
These cookies are used by Google Analytics to assist in collation of statistics informing us how our website is used by our visitors. Our staff use this information in aggregated reports to help measure our visitor experience, and how we might make improvement.
Generally these cookies will be essential first-party session cookies, and if persistent or third party, there should be a good justification for this. Not all first-party session cookies will fall into the ‘strictly necessary’ category for the purposes of the legislation. Strictly necessary cookies will generally be used to store a unique identifier to manage and identify the user as unique to other users currently viewing the website, in order to provide a consistent and accurate service to the user.
• Remembering previous actions (e.g. entered text) when navigating back to a page in the same session.
• Managing and passing security tokens to different services within a website to identify the visitor’s status (e.g. logged in or not)
• To maintain tokens for the implementation of secure areas of the website
• To route customers to specific versions/applications of a service, such as might be used during a technical migration
These cookies will not be used
• To gather information that could be used for marketing to the user.
• To remember customer preferences or user ID’s outside a single session (unless the user has requested this function).
These cookies can be first or third party, session or persistent cookies. To fall within this category their usage should be limited to performance and website improvement.
• Web analytics—where the data collected is limited to the website operator’s use only, for managing the performance and design of the site. These cookies can be third-party cookies but the information must be for the exclusive use of the publisher of the website visited.
• Ad response rates—where the data is used exclusively for calculating response rates (click-through rates) to improve the effectiveness of advertising purchased on a site external to the destination website. If the same cookie is used to retarget adverts on a third-party site this would fall outside the performance category (see category d)
• Affiliate tracking—where the cookie is used to let affiliates know that a visitor to a site visited a partner site some time later and if that visit resulted in the use or purchase of a product or service, including details of the product and service purchased. Affiliate tracking cookies allow the affiliate to improve the effectiveness of their site. If the same cookie is used to retarget adverts this would fall outside the performance category (see category d)
• Error management—Measuring errors presented on a website, typically this will be to support service improvement or complaint management and will generally be closely linked with web analytics.
• Testing designs—Testing variations of design, typically using A/B or multivariate testing, to ensure a consistent look and feel is maintained for the user of the site in the current and subsequent sessions. These cookies should not be used to re-target adverts, if they are, they should be placed in category d) as well.
These cookies can be first party, third party, session or persistent cookies. These cookies will typically be the result of a user action, but might also be implemented in the delivery of a service not explicitly requested but offered to the user. They can also be used to prevent the user being offered a service again that had previously been offered to that user and rejected.
• Remembering settings a user has applied to a website such as layout, font size, preferences, colours etc.
• Remembering a choice such as not to be asked again to fill in a questionnaire.
• Detecting if a service has already been offered, such as offering a tutorial on future visits to the website.
• Providing information to allow an optional service to function such as offering a live chat session.
• Fulfilling a request by the user such as submitting a comment.
These cookies should not be used to re-target adverts, if they are, they should be placed in category d) as well.
These cookies will usually be third-party cookies, although if a user is visiting the advertising network’s own website it is technically possible these could be first party. They will always be persistent but time-limited cookies. These cookies can be associated with services provided by the third party but this is not always the case. These cookies contain a unique key that is able to distinguish individual users’ browsing habits or store a code that can be translated into to a set of browsing habits or preferences using information stored elsewhere. Generally speaking, the privacy statement should indicate if the cookie is being used as part of an advertising network. Cookies may also be used to limit the number times a user sees a particular ad on a website and to measure the effectiveness of a particular campaign.
• Cookies placed by advertising networks to collect browsing habits in order to target relevant adverts to the user. The site the user is visiting need not actually be serving adverts, but often this will also be the case.
• Cookies placed by advertising networks in conjunction with a service implemented by the website to increase functionality, such as commenting on a blog, adding a site to the user’s social network, providing maps or counters of visitors to a site.