GDPR, Privacy Policies, and Cookies in the Agilent Community

Document created by mnevill Employee on Apr 27, 2018Last modified by mnevill Employee on Jul 11, 2018
Version 6Show Document
  • View in full screen mode

In an effort to be transparent and assist with questions related to GDPR, this document has been created to help explain how to view your user data within the Agilent Community, request erasure, and download your information for data portability.



Privacy Policies

As a part of the Terms and Conditions of this site, the Agilent Privacy Policy is utilized.  The Agilent Privacy Policy can be accessed from this link:


The Agilent Community is run off of the Lithium JX platform.  To view Lithium's Privacy Policy please reference this link:



GDPR Right to Request Erasure

If you wish to request erasure, please reference the instructions in the applicable section of Agilent's Privacy Policy via the link below and make sure to specifically mention erasure from the Agilent Community:



Your Profile Data

You can access and change all of your profile data by clicking on the avatar in the top right and clicking the link for Edit Profile.

The resulting page will show your profile data and allow you to make edits.  For fields that are not editable you can contact the Agilent Community Team ( for assistance.


Make sure to click the Finished button after making any changes.



Your Content

From the avatar menu you can access your content by clicking the Your Content link:


The resulting page will give you a filterable list for the various content you have authored, drafted, or participated in:



Data Export of Your Information

The platform the Agilent Community uses supports API calls to allow downloads of information. You can use the links below to download a JSON dump of things related to your account.

You must be logged in to use these links.

Your Profile -

Your Images -

Your Blog -

Your Activities -

Your Authored Content -

Your Content Participation -

Content You Are Following -

People You Are Following -

Your Followers -

Expertise Endorsements -

Security Permission Groups -


For related information please also reference Privacy Settings in the Agilent Community


How Cookies Are Used

The table below explains how cookies that are used on this site are classified:

1Strictly necessaryThese cookies are necessary for the proper functioning of the community, such as tracking a user session, or accessing secure areas.Session cookie used to pin a logged-in session to a browser
2PerformanceThe information these cookies collect is anonymous and is used to collect aggregate data including information about the pages users visit.Cookies delivered by Omniture WebAnalytics and Google Analytics for purposes of aggregate reporting
3FunctionalThese cookies allow websites to remember preferences and settings, such as your username, language, region, font size, and so on.Cookie used to hold a user’s username as part of a “remember me” feature
4Tracking, targeting and sharingThese cookies remember that you've visited a website, a particular web page, and/or track your activities on the site. This information is sometimes shared with third party advertisers for serving targeted online advertising or other personalized content.Cookies used to track visitor activity on an individual basis can be used by Lithium or its third party business partners to serve personalized content, and/or later aggregated and used to analyze website traffic and trends.



The table below explains what cookies the Agilent Community platform uses:

Cookie NameDescription and PurposePossible ValuesTypeExpiration Time/Type


Used only by the Gamification module. Tracks if the user is authenticated or not.true or false3one year
BIGipServerCookies prefixed with BIGipServer help to efficiently route internal traffic, and contain encoded addresses of internal Jive servers. These addresses are strictly internal, and cannot be used to connect to internal servers from the Internet. Altering the values of the cookie will not have any effect. For more information about these cookies, see the article Overview of BIG-IP persistence cookie encoding on the F5 Support site.2
clickedFolderThis cookie is used in the Admin Console to persist the open/closed status of the current folder as used in various tree-view portions of the Admin Console.string, true, or false.1at session end

Used for RPC and Proxy Calls (Shindig Token) in loading app data in iFrames

String, alphanumeric1configurable, defaults to 1 hour
highlightedTreeviewLinkThis cookie is used in the Admin Console to persist the current folder as used in various tree-view portions of the Admin Console.integer, the DOM ID of the clicked folder.1at session end
jive-cookieThis cookie is used in the Admin Console to temporarily persist an encrypted username/password when creating a bridge between two sites. The information in the cookie is first encrypted with AES/256 encryption and then Base64 encoded.string, Base64 encoded, encrypted username/password of remote site.1at session end
jive_default_editor_modeThis cookie is used on the front-end for guest/anonymous users who choose to use an editor mode other than the default editor mode.string, advanced3
30 days
jiveLocaleThis cookie is used on the front-end for guest/anonymous users who choose a locale setting.string, locale code330 days
jive.login.tsStores the time stamp of the user's last login.epoch time in ms1at session end
jive.login.typeStores the type of login that was performed, either true native Lithium-JX login or via SSOString, either "form" or "saml"130 days cookie retains the user's selection for opening content in the Jive Mobile Web app or the Jive Native App when using a mobile device. Currently supported for iOS devices only.WEB, NATIVE3one month
jiveRegularLoginUserCookieThis cookie is used to auto-redirect the login screen to the built-in authentication page (if the value exists and is set).true1one month
jive.saml.passive.triedThis cookie is used to mark when SAML passive authentication has already been attempted.true13600 seconds (one hour) cookie is the authentication context for the user.the user's encrypted security contex130 minutes unless refreshed. Same as the standard servlet container session timeout
jive.server.infoThis cookie is used on the front-end in combination with Content Distribution Networks (CDN) like Akamai to associate the user with a specific server (also known as "session affinity").string, a combination of the serverName, serverPort, contextPath, localName, localPort, and localAddr1at session end
jiveSSOLoginUserCookieThis cookie is used to auto-redirect the SSO screen to the built-in authentication page (if the value exists and is set).true1one month
jiveTimeZoneIDThis cookie is used on the front-end for guest/anonymous users who choose a timezone setting.string, timezone ID330 days
jive.senttoidpUsed to indicate whether a user has logged in with an SSO authority, used in conjunction with the "require explicit first time login" featurestring, true330 days
jive.user.loggedinThis cookie is used on the front-end in combination with Content Distribution Networks (CDN) to denote the status of the current request.string, true if the current request originates from a browser where the user is logged in1at session end
jive_wysiwygtext_heightThis cookie is used on the front-end to persist the height of the editor window across sessionsinteger, the height in pixels of the editor after the user chooses to expand the editor window3one year
JSESSIONIDThis cookie is used on the front-end and the Admin Console to identify a session. It is part of the Java Servlet specification.string, the unique token generated by Apache Tomcat1at session end
linkedin_oauth_This cookie is used to communicate and authenticate with LinkedIn.1
place_infoThis cookie is used to temporarily store the tile configuration information when a user is configuring a tile that integrates with a third-party system, such as Salesforce. After the user clicks Save in the place template editing interface, the cookie is destroyed.string, encoded representation of the place type and place id1after place template changes are saved
skin.palette.previewThis cookie is used to preview the site with an unpublished template.ID (long value) of the template1long lived. 30 days
SPRING_SECURITY_REMEMBER_ME_COOKIEThis cookie is used on the front-end as part of the security authentication process to denote whether or not the user wants to have their credentials persist across sessions. It is part of the Spring Security specification; details are available here.string, the Base64 encoded username and expiration time combined with an MD5 hex hash of the username, password, expiration time, and private key.1defaults to 14 days
X-JCAPI-TOKENLegacy csrf token, only in use in the mobile apps, set only to provide backwards compatibilityString, random with 8-character length11 year


NOTE: Some additional cookies not listed above are used for feedback, analytics, and site performance evaluation.