Input: [First Party Cookies] baoManualDisclaimer [Expiry Date] Session [Purpose]

Output: This cookie stores information stating that a warning notice required on the website for legal reasons has already been marked as ‘read’ by the anonymous user in question.


Input: [First Party Cookies] bmwcsaCDID [Expiry Date] Session [Purpose]

Output: The tracking tool on this website is for the statistical evaluation of data and uses cookies for this purpose. The data is collected anonymously and provides parameters such as the number of visitors, clicking behaviour and the average time website users spend actively browsing a particular page. Referrer URLs are also used to statistically evaluate the number of users who come to our website via partner websites. This is done to provide an understanding of which of our in-house marketing campaigns have sparked an interest in our website.


Input: [First Party Cookies] bmwcsaCDuvt [Expiry Date] 31 days [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] bmwcsaDBID [Expiry Date] 5 years [Category*] Performance [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] bmwcsakey [Expiry Date] Session [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] bmwcsaP3P [Expiry Date] 20 years [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] bmwcsaP4P [Expiry Date] 20 years [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] bmwcsaSF [Expiry Date] Session [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] bmwcsauvt [Expiry Date] 31 days [Category*] Performance [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] bmwWorkflowHash [Expiry Date] Session [Purpose]

Output: This cookie stores anonymous information that guarantees secure data transfer like that needed, for instance, when switching between http und https pages or reloading the website.


Input: [First Party Cookies] bw [Expiry Date] Session [Category*] Functionality [Purpose]

Output: By storing anonymous information on a specific technical requirement, this cookie makes it possible to display website content based on the data capacity of the user’s Internet connection.


Input: [First Party Cookies] configsSortBy [Expiry Date] Session [Purpose]

Output: This cookie stores the last viewing mode selected by the user for the saved vehicle configurations when logged in to ‘My BMWֺ’.


Input: [First Party Cookies] consentCookie [Expiry Date] 1 year [Purpose]

Output: This cookie is needed to store information on whether the user has granted their consent to the use of cookies requiring approval on this website.


Input: [First Party Cookies] cookieDisclaimer [Expiry Date] 1 year [Category*] Strictly necessary [Purpose]

Output: This cookie is needed to store information on whether the user has granted their consent to the use of cookies requiring approval on this website.


Input: [First Party Cookies] espBasket [Expiry Date] Session [Purpose]

Output: This cookie is needed to preserve all the information on the configured vehicle relevant for the shopping basket when navigating around various pages.


Input: [First Party Cookies] JSESSIONID [Expiry Date] Session [Category*] Strictly necessary [Purpose]

Output: This cookie makes it possible to switch between various pages while a vehicle is being configured by the anonymous user and saves the technical information that has already been entered in relation to the configuration.


Input: [First Party Cookies] languageCookie [Expiry Date] 1 year [Purpose]

Output: This cookie stores the language selected by the anonymous user and displays content in the chosen language when they next visit the website without the need to ask again.


Input: [First Party Cookies] LOGGEDIN [Expiry Date] 2 hours [Category*] Strictly necessary [Purpose]

Output: This cookie is used when a user logs in to their ‘My BMW’ account to ensure that the anonymised user remains logged in when switching between different pages on the website.


Input: [First Party Cookies] component ID (the cookie name is the component ID) [Expiry Date] Session [Purpose]

Output: This cookie stores information on which website navigation tab the anonymised user has opened, thereby ensuring that the previously selected tab is displayed again when the page is reopened within the same session.


Input: [First Party Cookies] sessionDisclaimer [Expiry Date] Session [Purpose]

Output: This cookie stores information stating that a warning notice required on the website for legal reasons has already been shown to the anonymous user in question.


Input: [First Party Cookies] SMSESSION [Expiry Date] 2 hours [Category*] Strictly necessary [Purpose]

Output: This cookie stores information that is indispensable for ensuring continued security of the process flow when using the website. One example of information stored is the unique value of the Core Server to guarantee the https security standard for the duration of a user’s visit once they have logged in to their My BMW Account.


Input: [First Party Cookies] usy46gabsosd [Expiry Date] Session [Category*] Performance [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] vehiclesSortBy [Expiry Date] Session [Purpose]

Output: This cookie stores the last viewing mode selected by the user for their own saved vehicle when they are logged in to ‘My BMWֺ’.


Input: [First Party Cookies] vinToolUnsavedVehicles [Expiry Date] Session [Purpose]

Output: This cookie stores the VIN number of a vehicle entered by the user, thereby ensuring that the vehicle can be conveniently displayed without the user having to re-enter the VIN number within the same session when switching between various pages.


Input: [First Party Cookies] visitorid [Expiry Date] 4 years [Category*] Performance and Marketing [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] vtz47gabsosd [Expiry Date] Session [Purpose]

Output: See bmwcsaCDID cookie.


Input: [First Party Cookies] GOOGLE + PLUGIN COOKIES [Expiry Date] Session [Category*] Marketing [Purpose]

Output: This cookie makes it possible to send data to Google+. Further information on the use of cookies and how they can be handled is available on the Google + website.


Input: [First Party Cookies] FACEBOOK PLUGIN COOKIES [Expiry Date] Session [Category*] Marketing [Purpose]

Output: This cookie makes it possible to send data to Facebook. Further information on the use of cookies and how they can be handled is available on the Facebook website.


Input: [First Party Cookies] WT_FPC [Expiry Date] Session [Category*] Marketing [Purpose]

Output: We integrate the Denkwerk Player in our website.


Input: [First Party Cookies] Psyma_participation [Purpose]

Output: These third party cookies assist the frequency with which the Psyma self completion survey appears. The cookies prevent visitors from being repeatedly invited to provide feedback. The cookie does not contain any data from the survey, a reference to the individual visitor is not possible.


Input: [First Party Cookies] Psyma_launched [Purpose]

Output: These third party cookies assist the frequency with which the Psyma self completion survey appears. The cookies prevent visitors from being repeatedly invited to provide feedback. The cookie does not contain any data from the survey, a reference to the individual visitor is not possible.


Input: [First Party Cookies] DoubleClick [Purpose]

Output: These cookies record the time and date a specific page was viewed online. It can also supply various details relating to the user such as IP address, referring sites and browser information.


Input: [First Party Cookies] K2C-anox_BMWi_0 [Expiry Date] 1 day [Purpose]

Output: This cookie contains a value of how many icons you have declined, this controls how many intuitive icons you see in your customer journey, currently the limit is 1 per day.


Input: [First Party Cookies] K2C- anox_history [Expiry Date] 1 day [Purpose]

Output: This cookie contains the customer history of pages on the BMWi site where the K2C script is installed. This cookie is deprecated and will be replaced by events in the latest version.


Input: [First Party Cookies] s_fid [Expiry Date] 2 years [Purpose]

Output: This cookie is used to identify a unique visitor if the standard s_vi cookie is unavailable due to third party cookie restrictions. It stores a unique visitor ID time/date stamp.


Input: [Name] PHPSESSIONID [Lasts] Until you close your browser. [Purpose]

Output: Used to remember who you are as you move around the site to preserve any preferences you set.

UHY Graduate Recruitment - Cookies policy


Input: [Name] sifrFetch [Lasts] Until you close your browser. [Purpose]

Output: Used to store whether your browser supports Flash technology, used to improve the appearance of website textual content.

UHY Graduate Recruitment - Cookies policy


Input: [Name] __utma [Lasts] 2 years from set/update. [Purpose]

Output: Used to determine unique visitors to this site for statistical purposes.

UHY Graduate Recruitment - Cookies policy


Input: [Name] __utmb [Lasts] 30 minutes from set/update. [Purpose]

Output: Used to determine separate visits you make to this site for statistical purposes.

UHY Graduate Recruitment - Cookies policy


Input: [Name] __utmc [Lasts] Until you close your browser. [Purpose]

Output: Used to determine separate visits you make to this site for statistical purposes.

UHY Graduate Recruitment - Cookies policy


Input: [Name] __utmz [Lasts] 30 minutes from set/update. [Purpose]

Output: Stores how you reached this site, whether via a direct method, a referring link, a website search, or an advert.

UHY Graduate Recruitment - Cookies policy


Input: [Cookie] Google Analytics [Name(s)] _utma_utmb_utmc _utmz [More information] Click here for an overview of privacy at Google [Purpose]

Output: These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.


Input: [Cookie] Reinvigorate [Name(s)] (various) c827l-*********** [More information] You can view Reinvigorate’s privacy policy here. [Purpose]

Output: These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.


Input: [Cookie] Website Alive [Name(s)] (various) ASPSESSIONID******** [More information] You can view Website Alive’s privacy policy here. [Purpose]

Output: These cookies are used for our live chat, to collect information in an anonymous form about visitors to our site for when they use the chat function on the website.


Input: [Cookie] CMS cookie [Name(s)] PHPSESSID [Purpose]

Output: Our CMS sets this cookie to check whether or not you are logged in to the members area


Input: [Cookie] Referrer cookie [Name(s)] referrer [Purpose]

Output: Our CMS sets this cookie to detect whether or not you found our site by clicking on a link on a referring site. This is used in our analytics when you submit a quick quote request.


Input: [Cookie] Twitter Cookies [Name(s)] (various) [More information] You can view Twitter’s privacy policy here. [Purpose]

Output: Cookies set by Twitter for the “Tweet this” and “Follow” buttons.


Input: [Cookie] Google Cookies [Name(s)] (various) [More information] You can view Google’s privacy policy here. [Purpose]

Output: Cookies set by Google for the “+1” buttons.


Input: [Cookie] Facebook Cookies [Name(s)] (various) [More information] You can view Facebook’s privacy policy here. [Purpose]

Output: Cookies set by Facebook for the “Like” buttons.


Input: [Cookie] Remember Me [Name(s)] (various) ppp_remember-me-*** [Purpose]

Output: An optional cookie set by the visitor to remember details entered in forms on the website. Ticking the “remember me” checkbox on the form sets these cookies, unticking it removes the cookies instantly.


Input: [Cookie name] KG_USER_LOCATION [Cookie expiry] Browser closed [Cookie purpose]

Output: With the launch of our American Kurt Geiger website (us.kurtgeiger.com), this cookie helps to remember where in the world a user is visiting our website from. If a customer would prefer to shop from our American website, the cookie remembers that as well.


Input: [Cookie name] nowelcomepopup [Cookie expiry] 24 hours [Cookie purpose]

Output: With the launch of our Kurt Geiger Welcome program. This cookie is used to determine whether a visitor had been displayed with the welcome program popup windows previously.


Input: [Cookie name] CATEGORY_INFO [Cookie expiry] Browser closed [Cookie purpose]

Output: When browsing any of our product listing pages, this cookie remembers what filtering was applied on previous page views, to enhance the browsing experience.


Input: [Cookie name] VIEWED_PRODUCT_IDS [Cookie expiry] Browser closed [Cookie purpose]

Output: This cookie remembers what products were viewed by the customer on previous page views, to enhance the browsing experience


Input: [Cookie name] CART [Cookie expiry] 24 hours [Cookie purpose]

Output: A unique id that is associated with a customer's shopping bag is kept in this cookie. This is basically so that our website has got access to this information at all times throughout a customer's visit.


Input: [Cookie name] CUSTOMER [Cookie expiry] 24 hours [Cookie purpose]

Output: Once a user is logged in, this cookie remembers a unique id associated with that customer's session, so that the website has got access to it at all times throughout the customer's visit.


Input: [Cookie name] CUSTOMER_INFO [Cookie expiry] 24 hours [Cookie purpose]

Output: Once a user is logged in, this cookie remembers a unique id associated with that customer's group that they have been placed in, so that the website has got access to it at all times throughout the customer's visit.


Input: [Cookie name] WISHLIST [Cookie expiry] 1 hour [Cookie purpose]

Output: This cookie remembers a unique id associated with a customer's wishlist, if the customer had created a wishlist during a particular visit. This is so that the website has got access to it at all times throughout the customer's visit.


Input: [Cookie name] WISHLIST_CNT [Cookie expiry] 1 hour [Cookie purpose]

Output: This cookie remembers a unique id associated with the amount of items in a customer's wishlist, if the customer had created a wishlist during a particular visit. This is so that the website has got access to it at all times throughout the customer's visit.


Input: [Cookie name] frontend [Cookie expiry] 24 hours [Cookie purpose]

Output: This cookie contains a unique id relating to a customer's session on our website. This allows the website to provide continuity between customer visits.


Input: [Cookie name] kurtgeiger_affiliate_ls [Cookie expiry] 2 years [Cookie purpose]

Output: When a customer visits our website from our Linkshare affiliate network, this cookie is used to identify which affiliate the customer found our website through.


Input: [Cookie name] kurtgeiger_affiliate_cj [Cookie expiry] 1 month [Cookie purpose]

Output: When a customer visits our website from our Commission Junction affiliate network, this cookie is used to identify which affiliate the customer found our website through.


Input: [Cookie name] __utma [Cookie expiry] 2 years [Cookie purpose]

Output: This cookie is used to enable the functionality provided by Google Analytics. This software allows us to analyse visitor information.


Input: [Cookie name] __utmb [Cookie expiry] 30 minutes [Cookie purpose]

Output: This cookie is used to enable the functionality provided by Google Analytics. This software allows us to analyse visitor information.


Input: [Cookie name] __utmc [Cookie expiry] Browser closed [Cookie purpose]

Output: This cookie is used to enable the functionality provided by Google Analytics. This software allows us to analyse visitor information.


Input: [Cookie name] __utmz [Cookie expiry] 6 months [Cookie purpose]

Output: This cookie is used to enable the functionality provided by Google Analytics. This software allows us to analyse visitor information.


Input: No Step / Not Initialized [Internal Value] -1 The HTTP(S) request had not yet started.


Input: Open Network Connection to Proxy (This processing state is only used if the load test is performed via an outbound proxy) [Internal Value] 0 Optional state: The HTTP(S) request failed during the opening of new a network connection to the outbound proxy server of your company.

Output: network problem inside your company - or on the outbound proxy


Input: Open Network Connection * [Internal Value] 1 The HTTP(S) request failed during the opening of new a network connection to the web server.

Output: network problem


Input: Transmit HTTP Request * [Internal Value] 2 The HTTP(S) request failed during the transmission of the HTTP request data.


Input: Wait for Server Response * [Internal Value] 3 The HTTP(S) request failed while waiting for the first byte of the HTTP response header data from the web server.

Output: the web application responds too slowly


Input: Receive HTTP Header * [Internal Value] 4 The HTTP(S) request failed while receiving the HTTP response header from the web server.

Output: network problem


Input: Receive Content * [Internal Value] 5 The HTTP(S) request failed while receiving the HTTP response content from the web server (HTML data, images, ...)

Output: network problem


Input: Close Network Connection [Internal Value] 6 The HTTP(S) request failed while closing the network connection to the web server.


Input: All Done [Internal Value] 7 The HTTP(S) request itself completed successfully (all data have been transmitted and received), but the received HTTP status code was incorrect, or the received MIME type (text/html, image/gif, ...) was incorrect, or an error was detected inside the received content data.

Output: malformed response content (unstable web application)


Input: [Cookie] SESS [What it's used for]

Output: This cookie will store information for each client session. This cookie is removed once the browser window is closed.


Input: [Cookie] has_js [What it's used for]

Output: This cookie remembers if your browser is able to display webforms that use Javascript, so we can provide feedback as you provide your details.


Input: [Cookie] _utma _utmb _utmc _utmz [What it's used for]

Output: These cookies are served by Google Analytics and are used to collect anonymous information about the number of visitors to the site, where vistors have come to the site from and the pages they visited. How to reject or delete these cookies: http://www.google.com/intl/en/policies/privacy/"


Input: [Cookie] WRUID [What it's used for]

Output: This cookie stores anonymous information about how visitors use our web site. This helps us provide a better customer experience based on how visitors use our website.


Input: [Cookie] ki_s ki_t ki_u [What it's used for]

Output: KissInsights is used to ask our website visitors their opinion on our website, cookies are used to ensure visitors do not receive multiple questions or surveys.


Input: [Cookie] abwebform [What it's used for]

Output: We use this cookie to test web site design changes. This keeps track of when we are serving a new page design.


Input: [Name] sess_track [Expiry] Session [Details]

Output: This session cookie identifies the user to the website using a unique randomly generated id. Once the user leaves the website the session ends.

First TransPennine Express Trains – Privacy Policy


Input: [Name] WebTisPersonalisation [Expiry] Session or 1st Jan 2100 if the user selects: "Remember me" [Details]

Output: This cookie stores a unique token that can be used across the website to enable personalisation.

First TransPennine Express Trains – Privacy Policy


Input: [Name] WebTisToken [Expiry] Session [Details]

Output: A unique token that can be used by web pages not included inside the online booking engine to enable the personalisation of those web pages. Is only present when the user is logged in.

First TransPennine Express Trains – Privacy Policy


Input: [Name] WebTisLogin [Expiry] Session [Details]

Output: This cookie indicates whether a user is logged in or not as well as storing items from the shopping basket.

First TransPennine Express Trains – Privacy Policy


Input: [Name] perm_track [Expiry] 1st Jan 2100 [Details]

Output: This cookie is a unique randomly generated id that links the website users' actions across their website visits (sessions). Primarily this is used for fraud detection although it is also used for analytics.

First TransPennine Express Trains – Privacy Policy


Input: [Name] ASP.NET_SessionID [Expiry] Session [Details]

Output: A token generated by the webserver that powers the website this value is used to recognise the user and link their session data to their website usage. The website cannot function without this cookie.

First TransPennine Express Trains – Privacy Policy


Input: [Name] .ASPXANONYMOUS [Expiry] Up to 2 years [Details]

Output: This cookie is used to recognise unauthorised entities when authorisation is required.

First TransPennine Express Trains – Privacy Policy


Input: [Name] SecureToken [Expiry] Session [Details]

Output: Used by SSL this randomly generated ID allows session validation in the secure areas of the website. Purchases cannot be made without this cookie.

First TransPennine Express Trains – Privacy Policy


Input: [Name] Google Analytics cookies: _utma, _utmb, _utmc, _utmz [Expiry] _utma = 2years, _utmb = 30minutes, _utmc = Not Set, _utmz = 6 months [Details]

Output: These cookies allow us to count page visits and traffic sources so we can measure and improve the performance of our site, using a service provided by Google Analytics. For more information about Google's privacy policy, please use this link:http://www.google.com/intl/en/policies/privacy.

First TransPennine Express Trains – Privacy Policy


Input: [Name] WT_FPC [Expiry] 10 years [Details]

Output: Allows us to track website usage and general user behaviour. This cookies stores the date and time the cookie was created, the last visit, and the start of the most recent session.

First TransPennine Express Trains – Privacy Policy


Input: [Name] ACOOKIE [Expiry] 2 years [Details]

Output: This cookie is used to track general website usage to facilitate site improvements

First TransPennine Express Trains – Privacy Policy


Input: [Name] language [Expiry] End of session [Details]

Output: This cookie stores your language preferences.

First TransPennine Express Trains – Privacy Policy


Input: [Cookie] Webtrends [Name] PWC_WOD [Type] Third party [Duration] 2 years from the time when you visit www.pwc.dk. [Purpose of cookie]

Output: Records for each visitor number of visits, time of the first visit, latest access and the cur-rent visit.


Input: [Cookie] Webtrends [Name] ACOOKIE [Type] Third party [Duration] 2 years from the time when you visit www.pwc.dk. [Purpose of cookie]

Output: Records by Java Script for each vis-itor number of visits, time of first visit, latest access and the current visit.


Input: [Cookie] Google Analytics [Name] __utma [Type] Third party [Duration] 2 years from the time when you visit www.pwc.dk. [Purpose of cookie]

Output: Records for each visitor number of visits, time of first visit, latest access and the current visit.


Input: [Cookie] Google Analytics [Name] __utmb [Type] Third party [Duration] 30 minutes from the time when you start your visit to www.pwc.dk. [Purpose of cookie]

Output: Records time of start of visit, when it ends and the duration of the visit.


Input: [Cookie] Google Analytics [Name] __utmc [Type] Third party [Duration] Is deleted when you leave www.pwc.dk. [Purpose of cookie]

Output: Records time of start of visit, when it ends and the duration of the visit.


Input: [Cookie] Google Analytics [Name] __utmz [Type] Third party [Duration] 6 months from the time when you start your visit to www.pwc.dk. [Purpose of cookie]

Output: Records the time when a visitor logs in to pwc.dk.


Input: [Cookie] Userneeds.dk [Name] AWSELB [Type] Third party [Duration] Is deleted when you leave www.pwc.dk. [Purpose of cookie]

Output: Records participation in our online survey regarding www.pwc.dk. Ensures that respondents do not receive the same survey more than once.


Input: [Cookie] metimus.dk [Name] pwcDialogld [Type] First party [Duration] Is deleted when you leave www.pwc.dk. [Purpose of cookie]

Output: Records whether a visitor has registered for subscription to the Dialog newsletter after the user has entered his or her email address.


Input: [Cookie] metimus.dk [Name] ASP.NET_SessionId [Type] First party [Duration] Is deleted when you leave www.pwc.dk. [Purpose of cookie]

Output: Records whether a visitor has registered for subscription to the Dialog newsletter after the user has entered his or her email address.


Input: [Cookie] CookieCuttr [Name] cc_cookie_accept [Type] Third party [Duration] 1 year from the time when you close the panel. [Purpose of cookie]

Output: Records that the cookie panel at the bottom of the page is closed, so it will not appear again.


Input: [Cookie] Adform [Name] uid, cid, c [Type] Third party [Duration] Not deleted [Purpose of cookie]

Output: Used to measure number of visits, interactions and usgae of website.


Input: [Cookie Name] locn [Originating Page] All [Expiry] Never [Purpose]

Output: Collecting region code and setting user region


Input: [Cookie Name] lang [Originating Page] All [Expiry] Never [Purpose]

Output: Collecting language code and setting display language


Input: [Cookie Name] RFID [Originating Page] Add to basket/log in [Expiry] Never [Purpose]

Output: User reference id + verification hash collected, for the purposes of session control.


Input: [Cookie Name] SID [Originating Page] First page visited [Expiry] Never [Purpose]

Output: Collects session ID for the purposes of session control.


Input: [Cookie Name] RVI [Originating Page] Viewing items [Expiry] One week [Purpose]

Output: Collects list of recently viewed items for the purposes of displaying "recently viewed items" panel.


Input: [Cookie Name] vbmprods [Originating Page] Viewing items [Expiry] One week [Purpose]

Output: Collects list of recently viewed items for the purposes of displaying "recommended items" panel.


Input: [Cookie Name] vbmtracker [Originating Page] Viewing items [Expiry] One week [Purpose]

Output: Collects recommended items tracking code for the purposes of building "recommended items" data.


Input: [Cookie Name] newCurr [Originating Page] Viewing currency exchange rates [Expiry] One week [Purpose]

Output: Collects data on currency to rate against in order to provide an exchange rate


Input: [Cookie Name] referid [Originating Page] First page visited [Expiry] 2 days [Purpose]

Output: Referral data to track sites that link to Venda


Input: [Cookie Name] httprefer [Originating Page] First page visited [Expiry] 2 days [Purpose]

Output: Referral data to track sites that link to Venda


Input: [Cookie Name] Setview [Originating Page] Product list/ search list page [Expiry] 1 week [Purpose]

Output: Keeps user's preference for the product information display page.


Input: [Cookie Name] setViewPerPage [Originating Page] Product list/ search list page [Expiry] 1 week [Purpose]

Output: Keeps user's preference for the number of products to view per page.


Input: [Cookie Name] RSI [Originating Page] Search [Expiry] 1 day [Purpose]

Output: Keeps last 3 keyword searches for the purpose of displaying the last 3 key words so users can quickly go back to them.


Input: [Cookie Name] Tracking tags [Originating Page] Various [Expiry] Not disclosed [Purpose]

Output: Analytical services


Input: [Cookie Name] Quench [Originating Page] All [Expiry] At end of browser session [Purpose]

Output: Managing performance on the Venda platform


Input: [Name of cookie] acctid [Purpose] Maintains site state information specific to current user visit [Status]

Output: Essential to site performance - session cookie

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] acctname [Purpose] Maintains site state information specific to current user visit [Status]

Output: Essential to site performance - session cookie

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] __atuvc [Purpose] 'Add this service' cookie [Status]

Output: Enables the use of social bookmarking - session cookie

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] JSESSIONID [Purpose] Maintains site state information specific to current user visit [Status]

Output: Essential to site performance - session cookie

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] LBCLUSTER [Purpose] Load balancer tracking [Status]

Output: Essential to site performance - session cookie

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] USERPASS- (where is a method of authentication such as ATHENS) [Purpose] USERPASS stores an encrypted version of the current username & password credentials [Status]

Output: Essential to site performance - session cookie

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] Google-analytics cookies [Purpose] Monitoring site usage [Status]

Output: Helpful to Bloomsbury - session based cookies. Details of these cookies are listed below:

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] __utma [Purpose] Monitoring site usage [Status]

Output: Google-analytics cookie - keeps track of the number of times a visitor has been to the site pertaining to the cookie, when their first visit was, and when their last visit occurred.

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] __utmb [Purpose] Monitoring site usage [Status]

Output: Google-analytics cookie - works with __utmc to calculate visit length by creating timestamp of the exact moment in time when a visitor enters a site.

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] __utmc [Purpose] Monitoring site usage [Status]

Output: Google-analytics cookie - works with __utmb to calculate visit length by creating timestamp 30 minutes after a visitor leaves a site. Expires if another pageview is not taken after this period.

Privacy and Cookie Policy : Berg Fashion Library


Input: [Name of cookie] __utmz [Purpose] Monitoring site usage [Status]

Output: Google-analytics cookie - tracks visitor location, search engine used, link clicked on, keyword used when site is accessed.

Privacy and Cookie Policy : Berg Fashion Library


Input: [Cookie] Google Analytics [Name] __utma __utmb __utmc __utmz [More information] Click here for an overview of privacy at Google [Purpose]

Output: These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where vistors have come to the site from and the pages they visited.


Input: [Cookie] Site cookie acceptance [Purpose]

Output: This cookie is used to record if a user has accepted the use of cookies on our website.


Input: [Cookie] Web Tracking Cookie [Name] com.silverpop.iMAWebCookie [Purpose]

Output: The Unique Identifier for the visitor. Used to pass individual identity to Engage along with specific actions.


Input: [Cookie] Web Tracking Cookie [Name] com.silverpop.iMA.page_visit [Purpose]

Output: One "per session" cookie created for each page visited in the session. Used to distinguish the first visit to a webpage by an individual from subsequent visits.


Input: [Cookie] Web Tracking Cookie [Name] com.silverpop.iMA.session [Purpose]

Output: The Unique Identifier for the current browsing session. Used to associate a series of individual events to a single functional browsing session.


Input: [Cookie] Woopra Analytics [Name] wooTracker wooMeta [Purpose]

Output: Real time analytics suite. Allows us to view visitors to the site in real time


Input: [Cookie] Quantcast [Name] __qca [Purpose]

Output: A tracking cookie allowing us to see which pages and content is viewed most often.


Input: [Cookie Names] osCsid [Expiry] 30 days [Category] General [Description]

Output: Powers website shopping basket, checkout, recently viewed products, account functions and personalised website functions

Cookie Policy Information for First Class Watches


Input: [Cookie Names] cookie_test [Expiry] 30 days [Category] General [Description]

Output: Used to check whether your web browser accept cookies or not

Cookie Policy Information for First Class Watches


Input: [Cookie Names] _ga, _dc_gtm_UA-XXXXX-X, __utma, __utmb, __utmz, __utmv, __utmx [Expiry] 30 minutes to 2 years [Category] Analytics & Research [Description]

Output: Google Analytics software cookies. These cookies allow us to measure statistics of the way you and others use our site. For example, the number of visitors or pages viewed. For information on how Google uses this information please visit Google Analytics.

Cookie Policy Information for First Class Watches


Input: [Cookie Names] webgains_affiliate [Expiry] 90 days [Category] Advertising [Description]

Output: Used to track whether or not you have visited from an affiliated partner website

Cookie Policy Information for First Class Watches


Input: [Cookie Names] optimizelyXXXXX [Expiry] 90 days [Category] Website Testing [Description]

Output: Used to improve our website by performing optimisation experiments (eg. providing two separate versions of a page for testing).

Cookie Policy Information for First Class Watches


Input: [Cookie Names] PRUM_EPISODES [Expiry] 90 days [Category] Website Testing [Description]

Output: Used to measure and improve website response time.

Cookie Policy Information for First Class Watches


Input: [Cookie Names] __ar_v4, 2c.cId [Expiry] 6 years+ [Category] Advertising [Description]

Output: A Google / YouTube / Display Network cookie which tracks clicks and views on websites across the Google properties and advertising network

Cookie Policy Information for First Class Watches


Input: [Cookie Name] prima_cookies [When not logged in] Yes [When logged in] Yes [Cookie Description]

Output: Remembers whether you have already closed this message.


Input: [Cookie Name] prima_notice [When not logged in] Yes [When logged in] Yes [Cookie Description]

Output: Remembers if you have alreaded viewed any notice/warning message(s). Such a message is used to inform users of potential downtime or issues that might affect the normal operation of the website. It is set to expire after the date when such notice is obsolete (eg after an expected downtime/error is fixed).


Input: [Cookie Name] PHPSESSID [When not logged in] Yes [When logged in] Yes [Cookie Description]

Output: The ID of your session.


Input: [Cookie Name] __utma [When not logged in] Yes [When logged in] Yes [Cookie Description]

Output: This is set by Google Analytics. It stores each user's amount of visits, and the time of the first visit, the previous visit, and the current visit.


Input: [Cookie Name] __utmb, __utmc [When not logged in] Yes [When logged in] Yes [Cookie Description]

Output: These are set by Google Analytics. They are used to check approximately how long you stay on a site (when a visit starts, and approximately ends).


Input: [Cookie Name] __utmz [When not logged in] Yes [When logged in] Yes [Cookie Description]

Output: This is set by Google Analytics. It stores where a visitor came from (search engine, search keyword, link).


Input: [Name] infCookie [Duration] Expires in five years. [Purpose]

Output: It let us know wheter the Cookie Advice Message has been displayed.


Input: [Name] SESS* [Duration] Expires at the end of the session. [Purpose]

Output: Used by encryption language PHP to allow session variables be stored on the web server.


Input: [Name] has_js [Duration] Expires when you closet he browser. [Purpose]

Output: Reports if javascript is enabled in your browser settings.


Input: [Name] _utma [Duration] Expires in two years.s [Purpose]

Output: Used to do a count of how many times a user visits the website.


Input: [Name] _utmb [Duration] Expires alter 30 minutes since the last record of page views. [Purpose]

Output: It ist used to calculate how long the user has benn on the web for statistical purposes.


Input: [Name] _ubmc [Duration] Expires at the end of the session. [Purpose]

Output: It ist used to calculate how long the user has benn on the web for statistical purposes.


Input: [Name] _utmz [Duration] Expires alter 6 month. [Purpose]

Output: It let us know how each user reached the webiste.


Input: [0] Application [1] Cookie name [3] More information [2]

Output: Purpose


Input: [0] Google maps [1] MPRF NID PREF SNID [3] Typical content: randomly generated numbers and letters. An overview of privacy at Google (external link). [2]

Output: These cookies are used by Google to store user preferences and information when viewing pages with Google maps on them. If you disallow these cookies you may not be able to access all the features of this site.


Input: [0] User satisfaction survey [1] Socitm_include_me[x] Socitm_exclude_me[x] Socitm_include_alt[x] [3] Typical content: randomly generated numbers. SOCITM insight privacy policy (external link). [2]

Output: These cookies are used to prevent customers being invited to participate multiple times in the same survey. They contain no personally identifiable data. If you disallow these cookies you will not be invited to participate in this survey.


Input: [0] Education jobs site (teaching jobs) [1] ASP.NET_SessionId LoggedIn .DBANON LastLoginDate [3] Typical content: either randomly generated letters and numbers or in the case of LoggedIn the words true or false, and in the case of LastLoginDate the date and time of your last login. Eteach privacy policy (external link). [2]

Output: These cookies are used to maintain your user session. Two of these cookies (ASP.NET_SessionId and LoggedIn) are deleted when you close your browser. If you disallow these cookies you may not be able to access all the features of this site.


Input: [0] YouTube [1] VISITOR_INFO1_LIVE PREF use_hitbox [3] Typical content: randomly generated numbers and letters. An overview of privacy at Google (external link). [2]

Output: Sets the default state for any user of YouTube and to store user preferences. Use_hitbox is deleted when you close your browser. If you disallow this cookie you may not be able to access all features of YouTube


Input: [0] Twitter [1] k Guest_id [3] Typical content: randomly generated numbers and letters. Twitter’s privacy policy (external link). [2]

Output: Sets the default state for any user of Twitter. The service will work as normal for functions such as searching or looking at public user profiles


Input: [0] Add This [1] psc ssc ssh sshs uid uit uvc loc dt di [3] Typical content: either constant numbers, randomly generated letters and numbers or information about how you chose to share (for example by email, facebook). An overview of Add This privacy policy (external link). [2]

Output: These cookies are used to to provide you with a more personal and interactive experience. They are also used to improve the quality of their site; to keep track of your login name, passwords, and pages you have visited on their site; and to tailor content to your interests and to personalize the site on your behalf. If you disallow cookies you may not be able to access certain personalized sections of their services such as publisher reports.


Input: [Cookie] basket [Purpose]

Output: This cookie keeps track of items selected and place in the basket and allows the checkout process to function.


Input: [Cookie] profile [Purpose]

Output: This cookie enables us to serve relevant products and offers to customers based on browsing behaviour.


Input: [Cookie] userregion [Purpose]

Output: This cookie enables us to display content that is relevant to your country (including pricing and delivery options).


Input: [Cookie] mobileondesktopsite mobile desktop [Purpose]

Output: These cookies enable us to display and determine the correct version of our website to a user such as the desktop version - or a version tailored to mobile devices.


Input: [Cookie] __utma __utmb __utmc __utmz [Purpose]

Output: These cookies are placed by Google Analytics, which we use to record anonymous statistics about the usage of our site.


Input: [Cookie] mmcore.mmact mmcore.pd mmcore.srv mmcore.tst mmid mmpa.tst [Purpose]

Output: These cookies are placed by Maxymiser, which we use to carry out tests for new website functionality and to serve product recommendations to customers.


Input: [0] Cookie [1] Name [3] More information [2]

Output: Purpose


Input: [0] ASP.NET SessionID [1] ASP.NET_SessionID [3] Only lasts for the current browsing session. [2]

Output: A default cookie that allows the site to know it is the same computer that has viewed the previous page.


Input: [0] Subscribe to Research [1] research_form [2]

Output: Records whether a user has already subscribed to the website to view research and if they have not, will request them to enter minimal details to do so.


Input: [0] Google Analytics [1] _utmx [3] How to reject or delete this cookie http://www.google.com/intl/en/privacypolicy.html [2]

Output: The Savills Website uses Google Analytics, a web analytics service provided by Google, Inc. Google Analytics sets a cookie in order to evaluate your use of our website and compile reports for us on activity of our website.


Input: [0] WebTrends [1] WT-FPC and ACOOKIE [2]

Output: The Savills website uses WebTrends Analystics package to evaluate the activity on our website.


Input: [0] Accordian Bar [1] home_accordian [3] Only lasts for the current browsing session. [2]

Output: Records how the user last viewed the home page so this view is replicated the next time they visit.


Input: [0] Alerts [1] savills_alert_cookie [3] Lasts for 100 days [2]

Output: Records that the user has subscribed for alerts so that they can change their preference in the future.


Input: [0] Recent Properties [1] savills_rs_recent_properties [3] Lasts for 2 weeks [2]

Output: Records the recent properties the user has viewed.


Input: [0] Recent searches [1] savills_rs_recent_searches [3] Lasts for 3 months [2]

Output: Records the recent searches the user has undertaken


Input: [0] Last Search [1] savills_rs_lastsearch [3] Lasts for 3 months [2]

Output: Records the last search that a user has undertaken


Input: [0] Saved Properties [1] savills_saved_properties [3] Lasts for 3 months [2]

Output: Records the properties a used has clicked "Save" next to.


Input: [0] Machine Tracker [1] savills_tracker_global [3] Lasts for 1 year [2]

Output: Records when the user returns to our site from the same computer.


Input: [0] Machine Tracker [1] savills_rs_tracker_global, savills_tracker_commsearch [3] Lasts for 1 year [2]

Output: Records when the user returns to our site from the same computer.


Input: [0] Session Tracker [1] savills_rs_tracker_session [3] Lasts for 1 day [2]

Output: Records what repeated searches users undertake


Input: [0] Alerts [1] InternationalInformation [3] Lasts for 10 years [2]

Output: Records that the user has subscribed for alerts so that they can change their preference in the future on our international search.


Input: [Cookie name] _we_wk_ss_lsf [Purpose] Used by our WebEngage survey software to determine if you have visited our website before, whether or not you have completed a survey before and the last time you did so [More information]

Output: The cookie is used across the main sections of our website

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] __utma, __utmb, __utmc, __utmz, _ga, __gat [Purpose] Used to collect information anonymously about how visitors use the Site. We use the information to compile reports and to make improvements [More information]

Output: Google analytics cookies are used across the whole NHM domain http://www.google.com/analytics/learn/privacy.html

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] datr [Purpose] Used to track Facebook login status, for sharing content to Facebook. [More information]

Output: These cookies are used when a Facebook 'like' button is embedded into a page

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] twll, k, k (r_twing.com), pid, original_referer, _twitter_sess [Purpose] Multiple cookies used by Twitter services, to monitor referral links, and login status. [More information]

Output: These are used where the 'Tweet this' button or other Twitter widgets are present on the website. https://twitter.com/privacy

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] PREF [Purpose] Stores Google Search preferences [More information]

Output: Used across the website to support the internal search engine functionality.

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] jive.recentHistory.-1, jive.recentHistory.{userid} [Purpose] Stores browsed NaturePlus content identifiers, creates one cookie for all non-logged in users and individual cookies for logged in users [More information]

Output: Used within the NaturePlus section

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] JSESSIONID [Purpose] Stores basket and login information to enable effective online transactions [More information]

Output: Used within the Shop sectionhttp://www.nhmshop.co.uk

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] BROWSERSESSION, Coyote-2-d04dd0ad [Purpose] Stores basket and login information to enable effective online transactions [More information]

Output: Used within the Prints on Demand sectionhttp://prints.nhmshop.co.uk

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] NaturalHistoryMuseum, cookieaddposition, cookieconfirmpopup, cookieshowfixed, cookielbcart, cookielbfixedoptions, cookieminmax, lastsearch [Purpose] Used to store information relating to items in the basket or lightbox, recent searches, and login information [More information]

Output: Used within the Picture Library section http://piclib.nhm.ac.uk/

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] .ASPXFORMSAUTH, ASP.NET_SessionId [Purpose] Session cookies that are used to manage logged in users [More information]

Output: Used within our recruitment portalhttp://nhm.irecruittotal.com

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] wpy.vote [Purpose] Used to record a user vote for a competition entry for the Wildlife Photographer of the year competition [More information]

Output: Found within the Wildlife Photographer of the Year sectionhttp://www.nhm.ac.uk/visit-us/wpy/

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] Activityino2, targetinginfo, u2 [Purpose] Used to assess the effectiveness of our digital marketing, and to ensure we do not expose you to the same advert multiple times. The cookie does not capture personal or sensitive information. [More information]

Output: Found within the Wildlife Photographer of the Year sectionhttp://www.nhm.ac.uk/visit-us/wpy/. Persistent for four months.

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] Archive.Catalog.Search [Purpose] Stores search history for library catalogue [More information]

Output: Only used within the library section athttp://www.nhm.ac.uk/research-curation/library/archives/catalogue/

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] site-version [Purpose] Records user selection of viewing device preference (mobile or desktop) [More information]

Output: Used across the website when a user chooses to view in either 'desktop' or 'mobile' mode.

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] nhm_cookie_accept [Purpose] Records user acceptance of cookie notice [More information]

Output: Used across the website to control the cookie notification banner

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] CACHED_FRONT_FORM_KEY, CART, CATEGORY_INFO, LAST_CATEGORY, PHPSESSID, VIEWED_PRODUCT_IDS, adminhtml, frontend [Purpose] Records user preferences and online experience for online shop [More information]

Output: Used on the http://www.nhmshop.co.uk online shop site

Cookies on the Museum's website | Natural History Museum


Input: [Cookie name] _stid, _uset [Purpose] _uset records when you receive a cookie from our Share This tool, and _stid associates users with topics of interest to help advertisers deliver targeted messages [More information]

Output: _stid is only currently used in the United States and not within the European Union

Cookies on the Museum's website | Natural History Museum


Input: [Cookie Name] djcs_session [Further information]

Output: Encrypted user session identifier


Input: [Cookie Name] djcs_route [Further information]

Output: Device tracking identifier


Input: [Cookie Name] djcs_demo [Further information]

Output: Compressed user demographics data


Input: [Cookie Name] djcs_group [Further information]

Output: Encrypted group user information


Input: [Cookie Name] GPLogin [Further information]

Output: Permanent cookie used to trigger redirects for transparent authentication on multiple Sites


Input: [Cookie Name] GSLogin [Further information]

Output: Temporary cookie used to trigger redirects for transparent authentication on multiple Sites


Input: [Cookie Name] LPLogin [Further information]

Output: Last log-in identifier


Input: [Cookie Name] LSLogin [Further information]

Output: Keeps track of last user log-in


Input: [Cookie name] Adtech [More Information] Adtech Cookie opt-out [Purpose]

Output: Adtech is EMAP's online ad server used for serving and tracking advertisements across the EMAP websites

HSJ Privacy Policy - Health Service Journal


Input: [Cookie name] Webtrends WT.FPC [More Information] WebTrends Privacy Policy [Purpose]

Output: WebTrends uses a cookie to track the number of unique users of this website. It basically tells us whether the website has a small number of regular visitors or a large number of infrequent visitors. The cookie only relates to what goes on in this website

HSJ Privacy Policy - Health Service Journal


Input: [Cookie name] Google Analytics _utma _utmb _utmc _utmz [More Information] Google Analytics Privacy Policy [Purpose]

Output: These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.

HSJ Privacy Policy - Health Service Journal


Input: [Cookie name] comScore [More Information] comScore Privacy Policy [Purpose]

Output: Comscore help us to provide online surveys and video content through our Site. Comscore use cookies so that they can provide anonymous statistics on the interaction of users with these online surveys or video content.

HSJ Privacy Policy - Health Service Journal


Input: [Cookie name] AddThis [More Information] AddThis opt-out [Purpose]

Output: AddThis helps us to integrate social media sharing tools into our website such as facebook or twitter and to measure the effectiveness of these sharing tools

HSJ Privacy Policy - Health Service Journal


Input: [Cookie name] DoubleClick (Google) [More Information] Google Privacy Policy [Purpose]

Output: Doubleclick use a cookie when they serve advertisements in order that they can deliver reports on the effectiveness of these advertisements on our Site. The cookie records what advertisements the user has seen and how often

HSJ Privacy Policy - Health Service Journal


Input: [Cookie name] Optify _opt_gvi [More Information] Optify Privacy Policy [Purpose]

Output: Optify collects information about End User activity on the Site, including a unique Optify Customer ID, the End User’s IP address, the URL of the “referring” Web page (i.e., the page viewed by the End User prior to visiting the tracked page on your Site), the title and URL of tracked pages on the Site, and information about pages visited and actions taken. The Javascript code makes a “call” to our Software Services where, relying on third party service providers, we use the IP address to identify company name and approximate geographical location for the End User.

HSJ Privacy Policy - Health Service Journal


Input: [Cookie Name] __utmz, __utmc, __utmb, __utma (www.firstdata.com domain) [More Information] Click here for an overview of privacy at Google [Purpose]

Output: These functional cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.


Input: [Cookie Name] s_vi, s_sess (www.firstdata.com domain) [More Information] Click here for an overview of privacy at Omniture [Purpose]

Output: These functional cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.


Input: [Cookie Name] ELQSTATUS, ELOQUA (both under eloqua.com domain) [More Information] Click here for an overview of privacy at Eloqua [Purpose]

Output: These functional cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.


Input: [Cookie Name] Lang (www.firstdata.com domain) [More Information] Not applicable [Purpose]

Output: Country Site Selection - This functional cookie is used to record the country/site that the user is accessing. We use the information to improve user's experience with the site. This cookie will expire 30 days after it is set.


Input: [Cookie Name] fdcsp (www.firstdata.com domain) [More Information] Not applicable [Purpose]

Output: Product Selection - This strictly necessary cookie is used to record the specific products that the user is interested in, so that the site can provide user with information about these products. This cookie will expire 30 days after it is set.


Input: [Cookie Name] useCookies [More Information] Not applicable [Purpose]

Output: Cookie Selection - This strictly necessary cookie is used to record if a user has accepted the use of cookies on this website. This cookie will expire 30 days after it is set.


Input: [1] Cookie name [3] More information [2]

Output: Purpose


Input: [0] Google Analytics [1] _utma _utmb _utmc _utmz [3] An overview of privacy at Google [2]

Output: These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitor have come to the site from and the pages they visited.


Input: [0] welove-music.com [1] CFID CFTOKEN _atuvc [2]

Output: These are temporary cookies that expire when you close your browser. We use them to help track certain vital activities such as items you might add to a lightbox or shopping cart or to authenticate your log in details as required.


Input: [0] addthis.com [1] uid uvc uit psc loc dt di [3] An overview of privacy at addthis.com AddThis opt-out [2]

Output: AddThis helps us to integrate social media sharing tools into our website such as facebook or twitter and to measure the effectiveness of these sharing tools


Input: [0] new.official.fm [1] _utma _utmb _utmc _utmz [2]

Output: These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitor have come to the site from and the pages they visited.


Input: [0] twitter.com [1] pid [3] Privacy at twitter.com [2]

Output: Set by Twitter


Input: [Cookie Name] style [Expiry] 12 months [Description]

Output: If you choose to use the website's built-in accessibility features to change the display colour scheme or font size, the site stores a cookie to remember your preference so that your experience remains consistent throughout your visit, and when you visit again in future.


Input: [Cookie Name] sessionid [Expiry] The length of the current session [Description]

Output: This ID is used by the website to identify you during your session. A lot of the time it isn't used at all, but if you decide to do something complex during your visit that isn't simply clicking a link to move from one page to another (such as filling out a form), the website uses this ID to identify you throughout the process to make sure it runs smoothly.


Input: [Cookie Name] __utma, __utmb, __utmc, __utmz [Expiry] From 30 minutes to up to 1 year [Description]

Output: Google Analytics: Tracking the path of visitors through the website and identifying returning visitors. Statistics derived from this information help us identify how well certain pages and aspects of the site perform, and where we can make improvements to help visitors access the information they need more quickly and with less hassle.


Input: [Cookie Name] __atuvc [Expiry] 2 years [Description]

Output: AddThis: The __atuvc cookie is created and read by the AddThis social sharing site JavaScript on the client side in order to make sure the user sees the updated count if they share a page and return to it before our share count cache is updated. No data from that cookie is sent back to AddThis and removing it when disabling cookies would cause unexpected behaviour for users.


Input: [Cookie Name] __cfcduid [Expiry] 1 year [Description]

Output: Cloudflare: Helps improve our website security by identifying if you are a legitimate user


Input: [Cookie Name] __utmb, __atuvc [Expiry] Varies [Description]

Output: YouTube: We embed videos from our official YouTube channel using YouTube's privacy-enhanced mode. This mode may set cookies on your computer once you click on the YouTube video player, but YouTube will not store personally-identifiable cookie information for playbacks of embedded videos using the privacy-enhanced mode. To find out more please visit YouTube's embedding videos information page.


Input: [Cookie Name] userCountry, userCurrencySymbol, user Explicit, userLangId, userLanguage, userPreferredUrl, userprefs, userSalesCatalogId, userStoreId, viewed, WC_ACTIVE_POINTER, WC_AUTHENTICATION, WC_PERSISTENT, WC_SESSION_ESTABLISHED, WC_USERACTIVITY, SessionExists, ShowAlert, arc-33056-recently-viewed, JSESSIONID, mdr_browser [Cookie Purpose]

Output: These cookies remember your preferences from previous visits, allow you to add to basket and store your shopping basket. The website wouldn't work for you without them.


Input: [Cookie Name] _utma, _utmb, _utmc, _utmz [Cookie Purpose]

Output: These cookies enable Google Analytics software. It helps us take and analyse visitor information such as browser usage and new visitor numbers. That information helps us to improve the website and your shopping experience, and to make our marketing campaigns relevant. The data stored by these cookies never shows personal details from which your individual identity can be established.


Input: [Cookie Name] _#env, _#lps, _#sess, _#srchist, _#tsa, _#uid, _#vdf [Cookie Purpose]

Output: We work with DC Storm to help make our marketing campaigns more relevant. DC Storm cookies are used to help us see which marketing campaigns you click on and interact with. The data taken does not contain personal details from which your individual identity can be established.


Input: [Cookie Name] _qsst, _qst, _qubitTracker cookies, _qPageNum_*name of brand* [Cookie Purpose]

Output: These cookies enable Qubit analytics software. This software helps us take and analyse visitor information such as browser usage, new visitor numbers, response to marketing activity and shopping times. That information helps us to improve the website and your shopping experience, and to make our marketing campaigns relevant. The data stored by these cookies never shows personal details from which your individual identity can be established.


Input: [Cookie Name] peerius_ct, peerius_rid, peerius_sess, peerius_user [Cookie Purpose]

Output: These cookies enable Peerius software. This software allows us to make recommendations of products that we think might be of interest to you, based on what you and other visitors have viewed


Input: [Cookie Name] s_cc, s_sq, s_vi [Cookie Purpose]

Output: These cookies enable SiteCatalyst analytics software, supplied by Adobe. This software helps us take and analyse visitor information such as browser usage, new visitor numbers, response to marketing activity and shopping times. That information helps us to improve the website and your shopping experience, and to make our marketing campaigns relevant.


Input: [Cookie Name] s_campaign, s_ev20, _#tsa [Cookie Purpose]

Output: These cookies show us how you found our website and which website you came from. This helps us know which of our online marketing channels is most effective. They also allow us to reward some external websites for directing you to us


Input: [Cookie] ecl_auth [Origin] www.whymsical.com [Persistency] Expires after 30 days [Information and Usage]

Output: This cookie contains the text "EU Cookie Law - LiPF cookies authorised". Without this cookie, the Forums' software is prevented from setting other cookies.


Input: [Cookie] AWNUTSWhymsicalcom [Origin] www.whymsical.com [Persistency] Expires according to user-chosen session duration [Information and Usage]

Output: If you log-in as a member of this site, this cookie contains your user name, an encrypted hash of your password and the time you logged-in. It is used by the site software to ensure that features such as indicating new Forum and Private messages are indicated to you. This cookie is essential for the site software to work correctly.


Input: [Cookie] PHPSESSID [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: This cookie contains a unique Session Identification value. It is set for both members and non-members (guests) and it is essential for the site software to work correctly. This cookie is not persistent and should be automatically removed when you close the browser window.


Input: [Cookie] pmx_upshr{NAME} [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: These cookies are set to records your display preferences for the site's Portal page if a panel or individual block is collapsed or expanded


Input: [Cookie] pmx_pgidx_blk{ID} [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: These cookies are set to records the page number for the site's Portal page if the page for a individual block is changed.


Input: [Cookie] pmx_cbtstat{ID} [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: These cookies are set to records the expand/collapse state for a CBT Navigator block content.


Input: [Cookie] pmx_poll{ID} [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: These cookies are set to records the id for the current poll in a multiple Poll block.


Input: [Cookie] pmx_{fadername} [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: These cookies are set to records the state for a Opac-Fader block.


Input: [Cookie] pmx_LSBsub{ID} [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: These cookies are set to records the current category and the state for a static Category block.


Input: [Cookie] pmx_shout{ID} [Origin] www.whymsical.com [Persistency] Current session only [Information and Usage]

Output: These cookies are set to records the current state of a Shout box block.


Input: [Cookie] pmx_php_ckeck [Origin] www.whymsical.com [Persistency] Page load time [Information and Usage]

Output: This cookie will probably never see you. It is set, if a Syntax check on a PHP block is initiated and will be deleted if the function executed.


Input: [Cookie] pmx_YOfs [Origin] www.whymsical.com [Persistency] Page load time [Information and Usage]

Output: This cookie will probably never see you. It is set on portal actions like click on a page number. The cookie is evaluated on load the desired page and then deleted. It is used to restore the vertical screen position as before the click.


Input: [HTTP Code] 200 [Description] Successful API call. Learn more [Summary]

Output: OK

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 400 [Description] A validation exception has occured. Learn more [Summary]

Output: Bad Request

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 401 [Description] Invalid authorization credentials. Learn more [Summary]

Output: Unauthorised

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 403 [Description] The client SSL certificate was not valid. This indicates the Xero Entrust certificate required for partner API applications is not being supplied in the connection [Summary]

Output: Forbidden

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 404 [Description] The resource you have specified cannot be found [Summary]

Output: Not Found

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 500 [Description] An unhandled error with the Xero API. Contact the Xero API team if problems persist. [Summary]

Output: Internal Error

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 501 [Description] The method you have called has not been implemented (e.g. POST Organisation) [Summary]

Output: Not Implemented

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 503 [Description] The API rate limit for your organisation/application pairing has been exceeded. Learn more [Summary]

Output: Rate Limit Exceeded

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 503 [Description] API is currently unavailable – typically due to a scheduled outage – try again soon. Learn more [Summary]

Output: Not Available

HTTP Response Codes with Xero API | Xero Developer


Input: [HTTP Code] 503 [Description] The organisation temporarily cannot be connected to. Learn more [Summary]

Output: Organisation offline

HTTP Response Codes with Xero API | Xero Developer


Input: [Cookie Length (seconds)] 63,072,000 [Description] This cookie keeps track of the number of times a visitor has been to the site, when their first visit was, and when their last visit occurred. [Cookie Name]

Output: __utma

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] 1,800 [Description] Holds timestamp of the exact moment in time when a visitor first visits the site [Cookie Name]

Output: __utmb

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] Session (until browser is closed) [Description] Holds timestamp of the exact moment in time when a visitor leaves the site [Cookie Name]

Output: __utmc

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] 63,072,000 [Description] Stores information used within Analytics to identify user as part of a custom segmentation. [Cookie Name]

Output: __utmv

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] 63,072,000 [Description] Stores data pertaining to which particular Website Optimizer test a user is part of. [Cookie Name]

Output: __utmx

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] 15,768,000 [Description] Keeps track of where the visitor came from, what search engine they used, what link was clicked on, what keyword they used, and where in the world they are when they accessed the website. [Cookie Name]

Output: __utmz

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] 31,536,000 [Description] Keep an anonymous track of the user so clicktale can do usage and usability reports. [Cookie Name]

Output: WRUID

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] 600 [Description] Used if clicktale doesn't want to record the users details. [Cookie Name]

Output: WRIgnore

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Cookie Length (seconds)] 31,536,000 [Description] Keeps an anonymous track of the user in order to aid improvements to the user experience. [Cookie Name]

Output: VCID

Easy Fundraising Ideas | easyfundraising.org.uk | easyfundraising


Input: [Name] PHPSESSID [Typical Content] PHP Session ID [Expires]

Output: When you close your browser


Input: [Name] SESS[Random string] [Typical Content] Drupal Session ID [Expires]

Output: When you close your browser


Input: [Name] SSESS[Random String] [Typical Content] Drupal Session ID when accessed over SSL [Expires]

Output: When you close your browser


Input: [Name] has_js [Typical Content] indicates whether Javascript is enabled [Expires]

Output: When you close your browser


Input: [Name] Drupal.toolbar.collapsed [Typical Content] controls visibility of a toolbar. Set after successful login to our Drupal Content Management system [Expires]

Output: Expires one week after installation


Input: [Name] cookie-agreed-en [Typical Content] Indicated whether consent for storing cookies has been given. [Expires]

Output: Expires 12 weeks after installation


Input: [Name] _UPRN [Typical Content] This cookie is set when you log onto mydundeeaccount.dundeecity.gov.uk. The cookie stores your Unique Property Reference Number and is used for displaying your house location on maps. [Expires]

Output: When you close your browser.


Input: [Cookie] __utma [More information] Tracks the number of times a visitor has been to our website, when their first visit was, and when their last visit occurred. [Purpose]

Output: A Google Analytics cookie which helps us understand how visitors are using our website, so we can make it more useful. Lifespan: Persistent

Property Services: Privacy Policy for the Property Website


Input: [Cookie] __utmb [More information] Tracks approximately how long a visitor stays on our website. [Purpose]

Output: A Google Analytics cookie which helps us understand how visitors are using our website, so we can make it more useful. Lifespan: 30 minutes

Property Services: Privacy Policy for the Property Website


Input: [Cookie] __utmc [More information] Tracks approximately how long a visitor stays on our website. [Purpose]

Output: A Google Analytics cookie which helps us understand how visitors are using our website, so we can make it more useful. Lifespan: At end of session

Property Services: Privacy Policy for the Property Website


Input: [Cookie] __utmz [More information] Tracks where a visitor came from, for example which search engine, search keyword or link they used. [Purpose]

Output: A Google Analytics cookie which helps us understand how visitors are using our website, so we can make it more useful. Lifespan: 6 months

Property Services: Privacy Policy for the Property Website


Input: [Cookie] show_bar [Purpose]

Output: Determines whether the cookie information bar at the top of the site is shown. Lifetime: 10,000 days

Property Services: Privacy Policy for the Property Website


Input: [Cookie] style [Purpose]

Output: Determines the layout of the page i.e small screen or large screen Lifetime: 365 days

Property Services: Privacy Policy for the Property Website


Input: [Cookie] sifrFetch [Purpose]

Output: Used to display custom fonts on the website Lifetime: Expires with session

Property Services: Privacy Policy for the Property Website


Input: [Cookie] slider [Purpose]

Output: Used to display the image slider on the website Lifetime: Expires with session

Property Services: Privacy Policy for the Property Website


Input: [Cookie] mysession [Purpose]

Output: Used to store data entered on the website such as seach terms Lifetime: Expires with session

Property Services: Privacy Policy for the Property Website


Input: [Cookie] map_zoom [Purpose]

Output: Used to store the current zoom level of a Google map Lifetime: Expires with session

Property Services: Privacy Policy for the Property Website


Input: [Cookie] map_lat [Purpose]

Output: Used to store the current latitude point of a Google map Lifetime: Expires with session

Property Services: Privacy Policy for the Property Website


Input: [Cookie] map_lng [Purpose]

Output: Used to store the current longitude point of a Google map Lifetime: Expires with session

Property Services: Privacy Policy for the Property Website


Input: [Cookie] WordPress [Type] Persistent [Duration] 1 year [Description]

Output: WordPress is the Content Management System (CMS) that runs this website. It uses cookies and is essential for proper website operation. There are cookies for logged in users and for commenters, so for most people it is not set at all. Users are those people who have registered an account with CrethiPlethi.com. The user cookies are set to expire two weeks from the time they are set. When you comment on our blog, you too get cookies stored on your computer. This is purely a convenience, so that you won’t need to re-type all your information again when you want to leave another comment. The commenter cookies are set to expire a little under one year from the time they’re set. User data is all anonymous.


Input: [Cookie] Article Comments [Type] Persistent [Duration] 1 year [Description]

Output: If you leave a comment on an article, then a cookie may be stored to ‘remember’ your email address for the next time a comment is submitted on the same page or blog post (should you choose the “Notify me of followup comments via e-mail” option).


Input: [Cookie] Google Analytics [Type] Persistent [Duration] 1 year [Description]

Output: Google Analytics uses cookies in order to provide meaningful reports about how many people visit our site, how visitors use our site, which country they are from, how many pages they visited, the time spend on our site, how fast our site loaded, and so on. However, these cookies do not collect personal data about our website visitors and is completely anonymous, it does not identify you as an individual in any way.


Input: [Cookie] Google AdSense [Type] Persistent [Duration] 1-6 years [Description]

Output: Google Adsense may use the DoubleClick cookie on our site to serve more relevant ads across the web and limit the number of times a given ad is shown to you. When you visit our website, view an ad, or click an ad supported by Google’s advertising services, it may set a cookie on your browser. This information helps Google deliver ads that are relevant to your interests, control the number of times you see a given ad, and measure the effectiveness of ad campaigns. This data is completely anonymous, it does not identify you as an individual in any way.


Input: [Cookie] EU Cookie Info [Type] Persistent [Duration] 1 year [Description]

Output: In the footer of each web page on this site you will see a message alerting you of our Privacy and Cookie Policy. We use a cookie to remember whether or not you’ve accepted our cookie policy. You can delete it by clicking this link. Note that this does NOT delete other cookies, it just deletes the EU cookie info that CrethiPlethi.com uses to remember if a visitor has closed the EU cookie info bar or not. User data is all anonymous.


Input: [Cookie] Social Media [Type] Persistent [Duration] 1-2 years [Description]

Output: Cookies set by other websites who run content on our website are known as third party cookies. For example Facebook sets cookies via our website if a visitor ‘likes’ one of our articles on our site, Twitter sets cookies if a visitor tweets one of our articles and YouTube sets cookies via our website when a visitor views an embedded video in one of our articles. Other social media buttons or plugins (such as Google+) also set cookies via our website when clicked by a visitor.


Input: [Cookie] Adobe Flash [Type] Persistent [Duration] 1 year [Description]

Output: Adobe Flash Player allows you to view and interact with SWF and FLV files (files that are read by Flash Player) created and published across the Internet using your browser or mobile device. It allows authors of SWF and FLV files and the websites hosting those files to use local shared objects (LSOs). LSOs can be used in a similar manner as cookies, and can be used for a variety of purposes such as keeping track of information you provided and remembering your preferences. If you have Adobe Flash Player installed on your computer, Flash Player can be set to reject or delete LSOs in the System Preferences on Mac OS X, in the Flash Player Control Panel on Windows®, or with the Flash Player management tools available on the Adobe website so that you can make your own choices about LSOs and other privacy issues.


Input: [Cookie name] Serverid JSESSIONID PHPSESSID [Purpose] These cookie identifies the user. It is used for tying the user session to a particular application server. This cookie is set when you visit any of our pages being served from our content management systems. It is used to help our server to handle your requests in the most efficient way and is deleted when you quit your browser. [Term]

Output: Expires when the browser session is closed.

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] __utma, ..., __utmz [Purpose] These cookies are used to collect information about how visitors use our site. We use Google Analytics to compile reports and to help us improve the site. The cookies collect information anonymously and includes the number of visitors to the site, where visitors have come to the site from and the pages they visited on a RIPE NCC website. [Term]

Output: Expires after 2 years

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] crowd.token_key [Purpose] This cookie identifies the user. It is used to authenticate logged-in single-sign-on (RIPE NCC Access) users. [Term]

Output: Expires when the browser session is closed

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] _pk_id.4.1234 [Purpose] This cookie is used to keep track of traffic for analytic purposes when accessing a RIPE Meeting website. [Term]

Output: Expires after 2 years

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] _pk_ses.4.1234 [Purpose] This cookie is used to keep track traffic for analytic purposes upon accessing RIPE Meeting sites. This information is not shared with third parties. [Term]

Output: Expires after 30 minutes

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] lastKnownLocationLng lastKnownLocationLat lastKnownLocationZoom [Purpose] This cookie saves the state of the LIR Locator application. When the user opens the page again, they will find the same location they had in their previous visit. [Term]

Output: Expires after 3 months

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] m2mTermsAccepted [Purpose] This cookie is set when users accept Terms of Service or Terms and Conditions of a service. If this cookie is not set, users will be asked to accept terms every time before they use a RIPE NCC service. [Term]

Output: Expires after 3 months

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] firstVisit-beta [Purpose] This cookie prevents help information from appearing again after the user has discarded it. [Term]

Output: Expires after 3 months

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] stat-session atlasessp [Purpose] These are standard cookies for user identification and session persistence. [Term]

Output: Expires after 2 weeks

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] stat-csrftoken csrftoken [Purpose] These cookies enhance security to protect from cross-site scripting attacks. Presently they are used to support comments forms. [Term]

Output: Expires after 1 year

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] crowd.token_key [Purpose] This cookie is used to identify logged in users among RIPE NCC services (Single Sign On). [Term]

Output: Expires when the browser session is closed

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] PREF [Purpose] This cookie is used for YouTube services. It is handling user preferences. It is beyond the RIPE NCC’s control. Use of YouTube services like embedded video require that the user request those services from YouTube directly, which in turn sets this cookie. Users interested in Google policies around this cookie should consult their privacy policy site: http://www.google.com/intl/en/policies/ [Term]

Output: Expires after 10 years

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] VISITOR_INFO1_LIVE [Purpose] For YouTube services. This cookie is used for YouTube services. It is handling visitor data to aid in streaming quality. It is beyond the RIPE NCC’s control. Use of YouTube services like embedded video require that the user request those services from YouTube directly, which in turn sets this cookie. Users interested in Google policies around this cookie should consult their privacy policy site: http://www.google.com/intl/en/policies/ [Term]

Output: Expires after 1 year

Cookies used by the RIPE NCC — RIPE Network Coordination Centre


Input: [Cookie name] .ASPXAUTH [More Information] www.meed.com [Purpose]

Output: ASP Authentication – A cookie used to determine if a user is authenticated

MEED: Middle East business intelligence, news, data, analysis, reports, consulting and services


Input: [Cookie name] uid [More Information] www.tynt.com/about-tynt/privacy-policy [Purpose]

Output: Cookie used to tracking what is being copied from the site

MEED: Middle East business intelligence, news, data, analysis, reports, consulting and services


Input: [Cookie name] SSOEX_1477230 [More Information] www.meed.com [Purpose]

Output: Concurrency cookie – manages the number of active sign ins to the site

MEED: Middle East business intelligence, news, data, analysis, reports, consulting and services


Input: [Cookie name] SSOEX_1477876 [More Information] www.meed.com [Purpose]

Output: Concurrency cookie – manages the number of active sign ins to the site

MEED: Middle East business intelligence, news, data, analysis, reports, consulting and services


Input: [Cookie name] emapauth [More Information] www.meed.com [Purpose]

Output: Login for MEED.com

MEED: Middle East business intelligence, news, data, analysis, reports, consulting and services


Input: [Cookie name] tempid [More Information] www.meed.com [Purpose]

Output: Single sign-on

MEED: Middle East business intelligence, news, data, analysis, reports, consulting and services


Input: [Cookie name] PHPSESSID [Cookie type] Strictly Necessary [Cookie purpose]

Output: This is the Usabilla session cookie. It determines if a user is logged in or not.


Input: [Cookie name] REMEMBERME [Cookie type] Functionality [Cookie purpose]

Output: This cookie is placed when a visitors checks the “remember me” option when logging in. It means we keep the session cookie for a longer period and the visitors doesn’t have to log in every time he or she visits the website.


Input: [Cookie name] usabilla.live_setup_info, usabilla.live_triggers_info [Cookie type] Functionality [Cookie purpose]

Output: We use these kind of cookies to know if you have closed certain help messages in our admin. This helps us to hide these messages from you in the future.


Input: [Cookie name] __utma, __utmc, __utmc [Cookie type] Performance [Cookie purpose]

Output: These types of cookies are used by Google Analytics. We use Google Analytics to collect aggregated data on the usage of our website (e.g. how many people visited certain pages, how long they stayed on our website, etc.). For more info on these cookies visit the Google Analytics privacy statement.


Input: [Cookie name] optimizelyEndUserId, optimizelyBucket, optimizelyCustomEvents, external_[ProjectId]_end_user_id [Cookie type] Performance [Cookie purpose]

Output: These types of cookies are used by Optimizely. We use Optimizely to A/B test our website. This means we can show different variations of parts of our website to users. We use the aggregated data to see which variation performs best and this way optimize the user experience on our website. For more info on these cookies visit the Optimizely knowledge base


Input: [Cookie name] PREF, NID, HSID, SSID, APISID, SAPISID, S, SS, SID, BEAT [Cookie type] Targeting [Cookie purpose]

Output: These cookies are used by the Google+ social share button. We use this service to show you have “liked” our website on the Google+ social network.


Input: [Cookie name] datr, lu, c_user, fr, xs, p, presence, act, sub [Cookie type] Targeting [Cookie purpose]

Output: These cookies are used by the Facebook social like button. We use this service to show you have “liked” our website on the Facebook social network. For more info on these cookies visit Facebook help.


Input: [Cookie Name] ASPSESSIONIDXXXXXXXX [Purpose]

Output: ASP session cookie that identifies the customer’s current session with the server. This cookie does not contain any content other than the session ID (indicated in the cookie name by “XXXXXXXX”)

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] Vsettings [Purpose]

Output: This cookie stores any settings for that session. Eg. if a customer selects to display 24 results per page on Search Results and Category pages, this cookie will store that setting throughout the customer’s browsing experience.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] Slt [Purpose]

Output: This cookie is a session login token that gets set when a customer logs in to our store. This allows customers to check out as a returning customer. This cookie is only set when the customer logs in, and is not set if the customer is returning to an active session.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] CartID5 [Purpose]

Output: This cookie allows customers to add items to the cart. Without this cookie customers would not be able to proceed to the checkout page.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] History50 [Purpose]

Output: This cookie stores the ProductIDs of the last items viewed by a customer on your store. This cookie is used to control the customers product view history.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] _atuvc [Purpose]

Output: This cookie comes from AddThis, which allows share buttons (Twitter, Email, Google+, etc.) to appear beneath the product image.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] Referrer [Purpose]

Output: This cookie is used to indicate the site from which the customer navigated to our store.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] AffiliateID [Purpose]

Output: This cookie is used to tell our Affiliate partners who should get credit/commission for items purchased through an Affiliate link.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] AffiliateTrackedToday [Purpose]

Output: This cookie is used to ensure that the affiliate link does not get click-through credit on each page load.

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Cookie Name] Google Analytics [Purpose]

Output: Non-personal information used to track a visitors route through the website. This is used to find at which point customers have abandoned the checkout process and is used to improve the website. You can read more information on the cookies used by Google Analytics uses on its information page

Cookie Policy | How We Use Cookies | Punky Pins


Input: [Compared URL] http://www.example.com/dir/page.html [Outcome] Success [Reason]

Output: Same protocol and host

Using jQuery To Load Content Onto A Page Without An iFrame | #! code


Input: [Compared URL] http://www.example.com/dir2/other.html [Outcome] Success [Reason]

Output: Same protocol and host

Using jQuery To Load Content Onto A Page Without An iFrame | #! code


Input: [Compared URL] http://www.example.com:81/dir/other.html [Outcome] Failure [Reason]

Output: Same protocol and host but different port

Using jQuery To Load Content Onto A Page Without An iFrame | #! code


Input: [Compared URL] https://www.example.com/dir/other.html [Outcome] Failure [Reason]

Output: Different protocol

Using jQuery To Load Content Onto A Page Without An iFrame | #! code


Input: [Compared URL] http://en.example.com/dir/other.html [Outcome] Failure [Reason]

Output: Different host

Using jQuery To Load Content Onto A Page Without An iFrame | #! code


Input: [Compared URL] http://example.com/dir/other.html [Outcome] Failure [Reason]

Output: Different host (exact match required)

Using jQuery To Load Content Onto A Page Without An iFrame | #! code


Input: [Compared URL] http://v2.www.example.com/dir/other.html [Outcome] Failure [Reason]

Output: Different host (exact match required)

Using jQuery To Load Content Onto A Page Without An iFrame | #! code


Input: [Name] wp-settings-3 [Group] WordPress [Description]

Output: Only used for logged in administrative users of the site

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] wp-settings-time-3 [Group] WordPress [Description]

Output: Only used for logged in administrative users of the site

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] wordpress_test_cookie [Group] WordPress [Description]

Output: To test if cookies are enabled

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] __utma [Group] Google Analytics [Description]

Output: Used to determine unique visitors. Expires 2 years from set / update.

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] __utmb [Group] Google Analytics [Description]

Output: Establish and continue a user session. Expires 30 minutes from set / update

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] __utmc [Group] Google Analytics [Description]

Output: Determines Visitor Session

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] __utmv [Group] Google Analytics [Description]

Output: Visitor segmentation

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] __utmz [Group] Google Analytics [Description]

Output: Used for tracking referrals from other websites. Expires 6 months after set/update.

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] site_font_size [Group] Font size [Description]

Output: Holds your preferred font size for this site

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Name] ecd-opt-in [Group] Cookie opt-in [Description]

Output: This cookie is used to record if a user has accepted the use of cookies on this website.

Privacy | Lucy Craske Health and Beauty Salon Leeds


Input: [Category] Pay attention to what you post and upload [No] 1 [Description] Remember that a social network is a public space; only post information or upload images you are comfortable with, keeping in mind that at a later stage you might be confronted with the content you uploaded, e.g. in a job interview. Information and pictures you post online should be considered permanent. They can be copied and stored by other individuals and can resurface years later in search engines. [Recommendations]

Output: Consider carefully which images, videos and information you choose to publish


Input: [No] 2 [Description] Do not make information such as address, date of birth or financial data available in your profile. A criminal might access your profile and steal your identity. [Recommendations]

Output: Never post sensitive information


Input: [No] 3 [Description] You do not need to use your real name in an online profile. Using a nickname can help you protect your identity and privacy; only close contacts will know who is behind the nickname. [Recommendations]

Output: Use a pseudonym


Input: [Category] Choose your friends with care [No] 4 [Description] Be selective about who you accept as a friend on a social network. You do not have to feel obliged to add someone to your friends’ list. Politely refuse or simply ignore the request. [Recommendations]

Output: Do not accept friend requests from people you do not know


Input: [No] 5 [Description] Ensure that the people you are in contact with or who sent a friend request are really who they say they are. Do not trust them immediately. [Recommendations]

Output: Verify all your contacts


Input: [Category] Protect your work environment and avoid reputation risk [No] 6 [Description] Do not use your company e-mail address but your private one and do not post confidential or competitive information about your organization. Be careful about the information you reveal about your workplace, for example do not post pictures shot in front of your office with the company's address or logo on the background that may lead to your job or workplace address. [Recommendations]

Output: When joining a social networking site use your personal e-mail address


Input: [No] 7 [Description] Consider what your employer would think before posting any comments or material online about your company or organisation. [Recommendations]

Output: Be careful how you portray your company or organisation online


Input: [No] 8 [Description] You have no control over what your friends may post online or how they may portray you and consequently what your employer, colleagues and clients may be exposed to. [Recommendations]

Output: Do not mix your business contacts with your friend contacts


Input: [Category] Protect your mobile phone and the information saved on it from any physical intrusion [No] 9 [Description] Before accessing your profile through your mobile phone pay attention to the environment and people that are surrounding you. If someone is trying to see what you are doing access your profile in a safer place. [Recommendations]

Output: Do not let anyone see your profile or personal information without your consent


Input: [No] 10 [Description] Someone with malicious intent could update your profile and status with false details. Remember to log out from the social network once your navigation is over and not to allow the social network to remember your password (this function is called ‘Auto-complete’). [Recommendations]

Output: Do not leave your mobile phone unattended


Input: [No] 11 [Description] Mobile phones can be easily lost or stolen and if you save your password on your mobile device anyone who may have possession of it can access your profile, see your pictures and friends. Try to commit your password to memory and if you write it down be careful where you store it. [Recommendations]

Output: Do not save your password on your mobile phone


Input: [No] 12 [Description] Remember to lock the keypad when not in use and to protect the device with a PIN or a password. Backup your details to another device such a PC in case your mobile phone is lost or stolen. Configure connections (such as Bluetooth and Wi-fi), especially in airports and public spaces, to be secure and if your mobile device has a built in firewall remember to enable it. [Recommendations]

Output: Use the security features available on your mobile phone


Input: [Category] Respect other people’s privacy [No] 13 [Description] Do not upload pictures or personal information regarding other people without their consent. You might commit a criminal offence. [Recommendations]

Output: Be careful what you publish about someone else


Input: [Category] Inform yourself [No] 14 [Description] Always be informed about who provides the service and how your personal information will be used and who has the right to access the information you post. [Recommendations]

Output: Read carefully and in full the privacy policy and the conditions and terms of use of the social network you choose


Input: [Category] Protect your privacy with the privacy settings [No] 15 [Description] Set the profile privacy level properly. Check the privacy settings of your profile — who can see your pictures, who can contact you and who can add comments in order to avoid making your profile available to everyone. [Recommendations]

Output: Use privacy-oriented settings


Input: [Category] Report immediately lost or stolen mobile [No] 16 [Description] Report immediately stolen or lost mobile phone with contacts and pictures saved in its memory and personal information regarding you and your friends (e.g. those friends whose contacts on the SNS have been synchronized with the mobile phone) and change the passwords on the social networks your are a member of. [Recommendations]

Output: Be careful when using your mobile phone and pay attention to where you put it


Input: [Category] Pay attention to the location based services and information of your mobile phone [No] 17 [Description] Remember to deactivate location based features of your mobile phone if you don’t need them. [Recommendations]

Output: Deactivate location based services when not using them.


Input: [Cookie name] _olocookie [Description]

Output: This cookie is used by General Insurance to store session information related to the Home Insurance sales process. No information is held specific to the customer. The data relates to how the customer arrived at the site. The session data is only held for 1 day and is necessary to track the performance of our sales process. This is a third party cookie.

Halifax | Security, Privacy & Cookies | Cookies