Company

Cookie Policy

Coherent Cookie Policy

Last Updated: October 10, 2017

This Coherent Cookie Policy describes the different types of cookies that may be used in connection with the website owned and controlled by us from which you are accessing this Cookie Policy (the “Site”), and how you can manage them.

We may change this Cookie Policy at any time. Please take a look at the “LAST UPDATED” legend at the top of this page to see when this Cookie Policy was last revised. Any changes in this Cookie Policy will become effective when we make the revised Cookie Policy available on or through the Site.

This Cookie Policy provides (a) a description of what cookies are how they are used; (b) a listing of the types of cookies used on the site (strictly necessary, functionality, performance, advertising); (c) how third parties used cookies on our Site; and (d) your cookies options.

1. What is a cookie?

A cookie is a small text file that is stored in your web browser that allows Coherent or a third party to recognize you. Cookies might be used for the following purposes: (1) to enable certain functions; (2) to provide analytics; (3) to store your preferences; and (4) to enable ad delivery and behavioral advertising.

Cookies can either be session cookies or persistent cookies. A session cookie expires automatically when you close your browser. A persistent cookie will remain until it expires or you delete your cookies. Expiration dates are set in the cookies themselves; some may expire after a few minutes while others may expire after multiple years. Cookies placed by the website you’re visiting are sometimes called “first party cookies,” while cookies placed by other companies are sometimes called “third party cookies.”

2. What cookies are used when I use the Site?

When you use the Coherent Site, Coherent or a third party may place a number of cookies in your browser. First-party cookies are cookies placed and used by Coherent; third-party cookies are those placed by a third party. Some of the cookies will only be used if you use certain features or select certain preferences, and some cookies will always be used. You can find out more about each cookie by viewing our current cookie list. We update this list periodically, so there may be additional cookies that aren’t yet listed.

Each cookie serves one of four different purposes:

A. Strictly Necessary Cookies

Strictly necessary cookies are necessary for the Site to work and enable you to move around it and to use its services and features. Without these absolutely necessary cookies, the Site will not perform as smoothly for you as we would like it to and we may not be able to provide the Site or certain services or features you request. The following are the types of strictly necessary cookies we use. Strictly necessary cookies are all first-party cookies.

Description How to manage cookies Cookie type
Session cookies are used to maintain the state of the application. Examples include: ai_session, PHPSESSID, and SLIBeacon_* . Accept/refuse via browser setting Session
Load balancing cookies are used to distribute the assets across the globe and lighten the server load. Examples include: ARRAfinity. Accept/refuse via browser setting Load balancing
User ID cookies are used to ensure that users only see their own information. Examples include: Peoplefluent. Accept/refuse via browser setting User ID
Security cookies are used for security controls and checks. Examples include: exp_csrf_token. Accept/refuse via browser setting Security

B. Functionality cookies

These first party cookies (also called preference cookies) store your preferences, such as username, language or region, in order to provide improved and personalized features. They can also be used to provide services requested by the user, such as viewing videos or social media integration. The following functionality cookies are used on the Site:

Description How to manage cookies Cookie Name
The session cookie named “pardot” is only set if you’re logged into the Pardot app as a user (i.e. prospects will not have this cookie set). Accept/refuse via browser setting pardot
The persistent cookie named “pi_opt_in” is what Pardot uses to stay in compliance with the “Do Not Track” initiative. Accept/refuse via browser setting pi_opt_in
Native to PHP and enables websites to store serialized state data. It is used to establish a user 6session and to pass state data via a temporary cookie, which is commonly referred to as a session cookie. It disappears when the client is closed. Accept/refuse via browser setting PHPSESSID
Used to help prevent spam and protect against Cross-site Request Forgery (CSRF), ExpressionEngine adds a random string to a hidden field on all forms. A copy of this string - also known as a CSRF token - is stored in the database along with the session id for which that form was generated. Accept/refuse via browser setting exp_csrf_token
Used by our third party site search provider to track the user’s session for reporting and learning, the value is essentially random given to the user when they load up one of our pages. Accept/refuse via browser setting Uid
Used by our third party site search provider to track the user’s session for reporting and learning, the value is essentially random given to the user when they load up one of our pages. Accept/refuse via browser setting sli_uuid
The conversion tracker session cookie used by our third party site search provider that contains a random unique identifier when the session is first created. Accept/refuse via browser setting SLIBeacon_* (eg SLIBeacon_846464540)
Contains the same session identifier created for SLIBeacon_* along with a timestamp of when the session started, the number of ‘page’ events and the number of searches that have taken place in this session. Accept/refuse via browser setting SLI1_* (eg SLI1_846464540)
Contains the same session identifier created for SLIBeacon_* along with a timestamp of when the session started, the number of ‘page’ events and the number of searches that have taken place in this session. Accept/refuse via browser setting SLI2_* (eg SLI1_846464540)
Contains the same session identifier created for SLIBeacon_* along with a timestamp of when the session started, the number of ‘page’ events and the number of searches that have taken place in this session. Accept/refuse via browser setting SLI4_* (eg SLI1_846464540)
Used only on our Job Search page, this cookie enhances the performance and functionality of the job search functions. It is non-essential to its use the job search. Accept/refuse via browser setting Peoplefluent

C. Performance Cookies

These cookies allow us to analyze activities on our Site and on other sites where we post content in order to monitor performance and improve and optimize the way our Site works. For example, we may use these types of cookies to ensure that visitors can easily find the information they are looking for on our Site. We might also use these cookies to test new ads, pages, or features to see how users react to them. Performance cookies may either be first party cookies or third party cookies. The following performance cookies are used on our Site:

Description How to manage cookies Cookie Name
Pardot CRM - The visitor cookie includes the name “visitor_id” plus the unique identifier for our account, which is derived from the tracking code placed on our site. The value stored is the unique ID for the visitor. For example, cookie name “visitor_id12345” stores the visitor value “123456789,” where 12345 is the account identifier and 123456789 represents the visitor ID. This cookie is set by Pardot tracking code on visitors and prospects. Accept/refuse via browser setting visitor_id* (eg visitor_id191222)
Pardot CRM - The visitor cookie includes the name “visitor_id” plus the unique identifier for our account, which is derived from the tracking code placed on our site. The value stored is the unique ID for the visitor. For example, cookie name “visitor_id12345” stores the visitor value “123456789,” where 12345 is the account identifier and 123456789 represents the visitor ID. This cookie is set by Pardot tracking code on visitors and prospects. The Hash ID extension help shorten ID and disallow exposure of database IDs to the user. Accept/refuse via browser setting visitor_id*-hash (eg visitor_id191222-hash)
MS AZURE Application Insights- Collects statistical usage and telemetry information for apps built on the Azure cloud platform to gauge performance. Accept/refuse via browser setting ai_user
MS AZURE Application Insights- Collects statistical usage and telemetry information for apps built on the Azure cloud platform to gauge performance. Accept/refuse via browser setting ai_session
Known as an affinity cookie, it allows the service to choose the right instance the user was using to serve subsequent requests made by that user. This means, a client establishes a session with an instance and it will keep talking to the same instance until his session has expired. Accept/refuse via browser setting ARRAfinity
Expression Engine CMS- Used to sets the date time that the user last visited the site. Accept/refuse via browser setting exp_last_visit
Expression Engine CMS- Every time the state is updated (the page reloaded) the last activity is set to the current date time. Used to determine expiry. It is used for content administration, but is set for both guests and administrators. Accept/refuse via browser setting exp_last_activity
Expression Engine CMS- Used to tracks the last 5 pages viewed by the user, and is used primarily for redirection after logging in etc. Affects guests and logged in users. Accept/refuse via browser setting exp_tracker
Google Analytics- Used to distinguish users, in order to gauge performance and statistical data for measuring how users interact with the website Accept/refuse via browser setting _ga
Google Analytics- Used to distinguish users, in order to gauge performance and statistical data for measuring how users interact with the website Accept/refuse via browser setting _gid
Google Analytics- Used to throttle request rate. Accept/refuse via browser setting _gat

D. Advertising cookies

These third party cookies are placed by advertising platforms or networks in order to deliver ads that may be relevant to you based upon your activities (this is sometimes called “behavioral” or “targeted” advertising) and track the performance of such ads. The following advertising cookies are used on our Site:

Description How to manage cookies Cookie Name
Used for customized ads on Google properties and in Google search. If you don’t want the ads you see to be coordinated across your devices, you can opt out of Ads Personalization using Ads Settings. NID

3. How do third parties use cookies on the Coherent Service?

Third party companies like analytics companies (such as Google analytics) and ad networks generally use cookies to collect user information on an anonymous basis. They may use that information to build a profile of your activities on the Coherent Site and other websites that you’ve visited. You can learn more about how these companies use your information by visiting the privacy policies listed in our cookie list.

4. What are my cookie options?

If you don’t like the idea of cookies or certain types of cookies, you can change your browser’s settings to delete cookies that have already been set and to not accept new cookies. To learn more about how to do this, visit the help pages of your browser. Please note, however, that if you delete cookies or do not accept them, you might not be able to use all of the features we offer, you may not be able to store your preferences, and some of our pages might not display properly.

You may also opt out of third party cookies by following the instructions provided by each third party in its privacy policy or opt-out pages. Please see our cookie list above for links to the third party privacy or opt-out policies. Some third party ad networks are members of the Network Advertising Initiative (NAI). You can visit the NAI’s website to find out how to opt out of members’ cookies.

5. Do you use any other user tracking technologies?

We use additional technologies to help track user activities and preferences. For example, we use web beacons (also known as clear gifs, pixel tags or web bugs). [Note: please confirm this] Coherent does not intentially use web beacons, but a third party vendor may. Web beacons are tiny graphics (about the size of period) with a unique identifier that are embedded invisibly on web pages or emails. They are used to track user activities and communicate with cookies. You cannot opt out of web beacons used in webpages, but you can limit their use by opting out of the cookies they interact with. You can opt out of web beacons used in emails by setting your email client to render emails in text mode only. Finally, we use local storage to facilitate certain functions, but we do not retain the data captured via local storage.

6. Do you respond to Do Not Track Signals?

Coherent does not track users of its Site over time and across third party websites to provide targeted advertising and therefore does not respond to Do Not Track (DNT) signals. However, as noted above, some third parties use cookies to provide your targeted advertising on other websites or in search results.

7. Where can I find more information about cookies?

You may learn more about cookies and how to opt out of them by visiting the following third party websites:

http://www.allaboutcookies.org/

http://optout.networkadvertising.org/#!/

If you have any questions about our Cookie Policy, you may contact us by email or by writing to us at: coherentwebmaster@coherent.com


Related Links

Please Read Before Continuing

Risk factors: Except for the historical information contained here, many of the matters discussed in this Web site are forward-looking statements, based on expectations at the time they were made, that involve risks and uncertainties that could cause our results to differ materially from those expressed or implied by such statements. These risks are detailed in the “Factors That May Affect Future Results” section of our latest 10-K or 10-Q filing. Coherent assumes no obligation to update these forward-looking statements.


I have read the terms and conditions