Menu

Detailed Cookies Use Policy

Last modified: May 25, 2018

Cookies are small files of letters and numbers stored on your browser or device that enable the cookie owner to recognize the device when it visits websites or uses online services. The website may set cookies directly, known as first-party cookies, or may trigger cookies set by other domain names, known as third-party cookies. While we may automatically use some cookies that are strictly necessary to provide the services you request or enable communications, we request your consent for all other cookie uses.
 
Types of Cookies We Use

We may use the following types of cookies:

Strictly necessary cookies. Our website requires the use of these cookies to properly operate or provide necessary functions relating to the services you request. 

Analytical/performance cookies. These cookies allow us, and our third-party service providers, to recognize and count the number of visitors and to see how visitors navigate our website when they are using it. This helps us improve how our website works by ensuring that users can easily find what they need on our website. These cookies generate aggregate statistics that are not associated with an individualized profile.

Functionality cookies. These cookies enable helpful but non-essential website functions that improve your website experience. By recognizing when you return to our website, they may, for example, allow us to personalize our content for you, greet you by name, or remember your preferences (for example, choice of language or region). These cookies may enable visitor identification across websites and over time.

Tracking or targeting cookies. These cookies enable different marketing-related functions. They may allow us to record information about your visit to our website, such as pages visited, links followed, and videos viewed so that we can make our website and the content displayed on it more relevant to your interests. These cookies may enable visitor identification across websites and over time. We may share the information with third parties for similar purposes.

Third-party cookies. Our website may contain helpful but non-essential features or plug-ins enabling third party services that use cookies, such as social network connectors, maps, or web traffic analysis services. These cookies may enable visitor identification across websites and over time. We do not control the third party's use of those cookies. Please review each party's cookie disclosure before consenting to this use category.

Our Privacy Statement describes our practices for any personal data that our first-party cookies collect, store, or use.

Except for strictly necessary cookies, all first-party cookies set by this site will expire no later than 2 years after your last website visit. Third-party cookie expiration periods are set by their respective owners. 

Please see below for a list of the individual first-party and third-party cookies potentially used on this site and their specific purposes. 

Cross-Border Data Transfers
The cookies we use may process, store, or transfer personal data in and to a country outside your own, with privacy laws that provide different, and possibly lower, protections. You consent to this transfer, storing, or processing when you consent to our cookie use. We are based in the United States. Please review the third-party cookie provider's policy to learn more about its location.

Your Cookie Choices
You consent to our use of cookies when you continue using our site. 

Most web browsers allow you to directly block all cookies, or just third-party cookies, through your browser settings. You may withdraw your consent for our cookie uses that are not strictly necessary at any time by managing your content settings in your browser. Using your browser settings to block all cookies, including strictly necessary ones, may interfere with proper site operation.

Changes to Our Cookie Uses
We will post any changes to the way we use cookies on this page and indicate on our website that we updated this cookie notice. If the changes materially alter how we use cookies, we will post a notice on our website and request your consent for the materially different use. Please check back frequently to see any updates or changes to our cookie use notice.

Contact Information
Please submit any questions, comments, or requests regarding this cookie use notice to Marketingteam@treliant.com

Cookie Table
 
Cookies Used on www.Treliant.com

The following table lists all cookies potentially in use on www.treliant.com. We will update this table as our website changes and evolves, so please check back frequently to review any new cookie uses. Visit our Privacy Statement for more information about our cookie use, including our contact information and complaint procedures.

Last modified: May 25, 2018

Cookie Category

Cookie Name and Owner

Purpose

More information

Functional

language Treliant

Identifies visitor’s default language (i.e., English, French, etc.)

httpOnly - This cookie is not readable by client-side JavaScript code.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: five bytes

 

Classification: same-origin session

 

sample: en-US

Analytical or Performance

.ASPXANONYMOUS Treliant

Create local, anonymous ID for visitors

httpOnly - This cookie is not readable by client-side JavaScript code.

 

This cookie expires within 90 days of an individual’s first visit.

 

Size: 65 bytes

 

Classification: same-origin persistent

 

sample: O2c1Nklk0wEkAAAAYjE5NWZjN2QtODg2OS00MGUxLTliM2MtYjU1MTViMTY4NjQx

Analytical or Performance

ASP.NET_SessionId

Treliant

Track individual sessions by visitors

httpOnly - This cookie is not readable by client-side JavaScript code.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: 24 bytes

 

Classification: same-origin session

 

sample: Cavn4vyezytwitwdwmdfnnhs

Analytical or Performance

__RequestVerificationToken

Treliant

Anti-forgery token

httpOnly - This cookie is not readable by client-side JavaScript code.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: 124 bytes

 

Classification: same-origin session

 

sample: bUzYw7SovhXBK8OfgXDhKMMIVfwYJOg8pJZ5xy4RC3tUE6tXrWQkCBBKBUE4UwMzYGlHQbEdTuwcmT27uZowu64kPhW2uRb

Analytical or Performance

__utmt

 

Google

Throttle request rate

This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: one byte

 

Classification: same-origin session

 

sample: 1

Tracking

__utma

 

Google

distinguishes users and sessions in Google Analytics

This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag.

 

This cookie expires within 2 years of most recent visit.

 

Size: 55 bytes

 

Classification: same-origin persistent

 

sample: 260243912.1006290787.1505434363.1505434363.1505434363.1

Tracking

__utmb

 

Google

determines new sessions/visits

This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: 25 bytes

 

Classification: same-session origin

 

sample: 260243912.1.10.1505434363

Tracking

__utmc

 

Google

Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit

This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: nine bytes

 

Classification: same-session origin

 

sample: 260243912

Tracking

__utmz

 

Google

rack how visitors came to our site

This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag.

 

This cookie expires within two years of most recent visit.

 

Size: 70 bytes

 

Classification: same-origin persistent

 

sample: 260243912.1505434363.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)

Functional

dnn_IsMobile

 

Treliant

determines if visitor should see mobile or desktop presentation of website

httpOnly - This cookie is not readable by client-side JavaScript code.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: five bytes

 

Classification: same-origin session

 

sample: False

Necessary

ArticleDetailTemplate

 

Treliant

Presents article text in designated template

This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag.

 

The cookie expires after one day.

 

Size: 5 bytes

 

Classification: same-origin session

 

sample: False

Functional

setButtonStateCookie

 

Treliant

Determines visibility of buttons

This cookie can be read by client-side JavaScript which might increase chances of stealing it in case of a successful Cross-Side Scripting attack. It's recommended that cookies storing authentication-related session token are protected by the flag.

 

The cookie is only valid during current browser session and it will be deleted when you close browser.

 

Size: 256 bytes

 

Classification: same-origin session

 

Sample: 0