In particular, our online services use the following categories of Cookies:
Most browsers are initially set up to accept HTTP cookies. The “help” feature of the menu bar on most browsers will tell you how to stop accepting new cookies, how to receive notifications of new cookies, and how to disable existing cookies. For more information about HTTP cookies and how to disable them, you can consult the information at www.allaboutcookies.org/manage-cookies/.
Controlling the HTML5 local storage on your browser depends on which browser you use. For more information regarding your specific browser, please consult the browser’s website (often in the Help section).
For more information about Flash “cookies” or local storage objects or LSOs, and how to disable them, you can consult the information provided at http://kb2.adobe.com/cps/526/52697ee8.html.
Please note, however, that without HTTP cookies and HTML5 and Flash local storage, you may not be able to take full advantage of all our online services features, and some parts of the online services may not function properly.
The following table sets out some examples of the individual cookies we use and the purposes for which we use them:
|Strictly Necessary Cookies||These cookies are required for device fingerprinting||Stores session identifier||Session cookie (expires when browser is closed)|
|Performance Cookies||Cookies in this category enable [Insert Name] to measure the performance of our digital properties||Unique visitor ID time/date stamp||Updated every page view|
|Functionality Cookies||These cookies store user settings and preferences to enable functionality||User entered zip code for locale search||Session expires when the browser is closed|
|Targeting Cookies||Advertising cookies enable more precise ad delivery to our visitors||Unique user identifier||2 years|
A cookie (sometimes referred to as a local storage object or LSO) is a data file placed on a device. Cookies can be created through a variety of web-related protocols and technologies, such as HTTP (sometimes referred to as “browser cookies”), HTML5, or Adobe Flash.
Small graphic images or other web programming code called web beacons (also known as “1×1 GIFs” or “clear GIFs”) may be included in our online service’s pages and messages. Web beacons may be invisible to you, but any electronic image or other web programming code inserted into a page or e-mail can act as a web beacon.
Clear gifs are tiny graphics with a unique identifier, similar in function to cookies. In contrast to HTTP cookies, which are stored on a user's computer hard drive, clear gifs are embedded invisibly on web pages and are about the size of the period at the end of this sentence.
An embedded script is programming code that is designed to collect information about your interactions with the online service, such as the links you click on. The code is temporarily downloaded onto your device from our web server or a third-party service provider and is active only while you are connected to the online service and is deactivated or deleted thereafter.
A feature of the cache in browsers, an ETag is an opaque identifier assigned by a web server to a specific version of a resource found at a URL. If the resource content at that URL ever changes, a new and different ETag is assigned. Used in this manner ETags are a form of device identifier. ETag tracking may generate unique tracking values even where the consumer blocks HTTP, Flash, and/or HTML5 cookies.
For each user that accepts push notifications in mobile apps, the app developer is provided with a unique device token (think of it as an address) from the app platform (e.g., Apple and Google).
The unique series of numbers and letters assigned to your device
We provide the chart below as a courtesy, but we are not obligated to maintain or update it. We are not responsible for third-party sites and their privacy practices as it relates to opt-outs from tracking activities. The following third parties that collect information from you on our Sites have given us notice that you may obtain information on their policies and practices, and in some instances opt out of certain of their activities, as follows:
|Party||Service||For More Information||Use of Tracking Technologies||Privacy Choices|
|Yahoo Ad Exhchange||Advertising||https://policies.yahoo.com/us/en/yahoo/privacy/adinfo/index.htm||Yes||https://policies.yahoo.com/us/en/yahoo/privacy/index.html|
|LinkedIn Marketing Solutions||Advertising||https://www.linkedin.com/about-us||Yes||https://www.linkedin.com/legal/privacy-policy|
|Google AdWords Conversion||Advertising||http://www.google.com/intl/en/about.html||Yes||http://www.google.com/intl/en/policies/privacy/|
|Facebook Custom Audience||Advertising||https://www.facebook.com/business/||Yes||https://www.facebook.com/full_data_use_policy|
|Google Dynamic Remarketing||Advertising||http://www.google.com/intl/en/about.html||Yes||http://www.google.com/intl/en/policies/privacy/|
|Google Tag Manager||Essential||http://www.ensighten.com/company/about-us/||Yes||http://www.ensighten.com/privacy-policy/|
|Google Analytics||Site Analytics||http://www.google.com/intl/en/about.html||Yes||http://www.google.com/intl/en/policies/privacy/|
|New Relic||Site Analytics||https://newrelic.com/about||Yes||https://newrelic.com/privacy|
|LinkedIn Analytics||Site Analytics||https://www.linkedin.com/about-us||Yes||https://www.linkedin.com/legal/privacy-policy|
|GA Audiences||Site Analytics||http://www.google.com/intl/en/about.html||Yes||http://www.google.com/intl/en/policies/privacy/|
|Facebook Connect||Social Media||https://www.facebook.com/FacebookforDevelopers||Yes||https://www.facebook.com/about/privacy/|