To help inform us of ways to improve our website, small files called 'cookies' are placed on your computer. Cookies provide us with useful information, such as how you use our site. They don’t identify individuals, only the computer used.
a) Strictly necessary
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.
Cookies used by Scotland's Rock Art Project
Rockart.scot sets the following cookies:
|AWSELB||Used by Amazon's elastic load balancer to uniquely identify a client device (browser) to enable the site to maintain user session variables.||30 minutes||Functionality|
|MXP_TRACKINGID||Used by Mura CMS to uniquely identify a client device (browser) to enable the site to maintain user session variables.||30 years||Functionality|
|cfid||Used in conjunction with cftoken this cookie helps to uniquely identify a client device (browser) to enable the site to maintain user session variables.||20 days||Functionality|
|cftoken||Used in conjunction with cfid this cookie helps to uniquely identify a client device (browser) to enable the site to maintain user session variables.||20 days||Functionality|
|mobileFormat||Used to determine whether or not to show the mobile format of the website.||30 years||Functionality|
|_ga and _gat||Used by Google Analytics. This helps us count how many people visit rockart.scot by tracking if you have visited before||2 years||Performance|
|_utma||Used by Google Analytics. Like _ga, this lets us know if you’ve visited before, so we can count how many of our visitors are new to rockart.scot or to a certain page||2 years||Performance|
|_utmb||Used by Google Analytics. This works with _utmc to calculate the average length of time you spend on rockart.scot||30 minutes||Performance|
|_utmc||Used by Google Analytics. This works with _utmb to calculate when you close your browser||when you close your browser||Performance|
|_utmz||Used by Google Analytics. This tells us how you reached rockart.scot (like from another website or a search engine)||6 months||Performance|
|analytics_nextpage_call||Used by Google Analytics. This lets us know the next page you visit on rockart.scot, so we can make journeys better||when you close your browser||Performance|
|GDS_successEvents and GDS_analyticsTokens||Used by Google Analytics. These help us identify how you use rockart.scot so we can make the site better||4 months||Performance|
|Social Media related cookies||Cookies served to deliver the Social Media share buttons. Third party cookies are set to allow users to share images.||Vary from session to 10 years||Functionality|
Google Analytics provides an opt-out browser ad-on.