Effective May 24, 2018
Currently, our systems do not recognize browser “do-not-track” requests. You may, however, disable certain tracking as discussed in this section (e.g., by disabling cookies); you also may opt-out of targeted advertising by following the instructions in the Third Party Ad Network section.
Cookies. Cookies are alphanumeric identifiers that are transferred to your computer’s hard drive through your web browsers for record-keeping purposes. Some cookies allow us to make it easier for you to navigate our Site and services, while others are used to enable a faster log-in process or to allow us to track your activities at our Site and Service. There are two types of cookies: session and persistent cookies.
Session Cookies. Session cookies exist only during an online session. They disappear from your computer when you close your browser or turn off your computer. We use session cookies to allow our systems to uniquely identify you during a session or while you logged into the Site. This allows us to process your online transactions and requests and verify your identity, after you have logged in, as you move through our Site.
Persistent Cookies. Persistent cookies remain on your computer after you have closed your browser or turned off your computer. We use persistent cookies to track aggregate and statistical information about user activity.
Disabling Cookies. Most web browsers automatically accept cookies, but if you prefer, you can edit your browser options to block them in the future. The Help portion of the toolbar on most browsers will tell you how to prevent your computer from accepting new cookies, how to have the browser notify you when you receive a new cookie, or how to disable cookies altogether. Visitors to our Site who disable cookies will be able to browse certain areas of the Site, but some features may not function.
Clear GIFs, pixel tags and other technologies. Clear GIFs are tiny graphics with a unique identifier, similar in function to cookies. In contrast to cookies, which are stored on your computer’s hard drive, clear GIFs are embedded invisibly on web pages. We may use clear GIFs (a.k.a. web beacons, web bugs or pixel tags), in connection with our Site to, among other things, track the activities of Site visitors, help us manage content, and compile statistics about Site usage. We and our third party service providers also use clear GIFs in e-mails to our customers, to help us measure e-mail response rates, identify when our e-mails are viewed, and determine whether our e-mails are forwarded.
How Do You Adjust Browser Cookie Settings?
Cookies can be managed through functionality built into most web browsers (e.g. Microsoft Internet Explorer, Firefox, Chrome). They can be adjusted to notify you of cookie placement requests, ask for permission to accept them, or decline cookies completely. For information on how to adjust your web browser cookie settings, please visit:
How Do We Use Third-Party Ad Networks?
You may opt-out of many third-party ad networks, including those operated by members of the Network Advertising Initiative (“NAI”) and the Digital Advertising Alliance (“DAA”).
Opting out of one or more NAI member or DAA member networks (many of which will be the same) means that those members no longer will deliver targeted content or ads to you. You may continue to receive advertisements, for example, based on the particular website that you are viewing. Also, if your browsers are configured to reject cookies when you change web browsers, your NAI or DAA opt-out may no longer be effective. For more information regarding this practice by NAI members and DAA members, and your choices regarding having this information used by these companies, including how to opt-out of third-party ad networks operated by NAI and DAA members, please visit their respective websites: http://www.networkadvertising.org/choices/ (NAI) and http://www.aboutads.info/choices/ (DAA).
What Cookies Do We Use on Broadcom Sites?
We have categorized our cookie use below. Note that some cookies are set by third parties which Broadcom does not control, so we can't ensure their cookies won't change over time.
Cookies are small data files stored in web browsers to track usage and enable useful services and features on Lithium Communities. This document provides information on the standard cookies set by Lithium Communities and how to reject or delete those cookies should users choose to do so. Understand that restricting cookies can have an adverse impact on the functionality and the online user experience on the Community.
We classify the cookies typically found on Lithium communities into the four broad categories described below. Lithium sets only Type 1 (necessary) and Type 3 (functional) cookies. We do not set any performance tracking (Type 2) or targeting and sharing cookies (Type 4). Note that our customers may set Type 2 and Type 4 cookies on their respective Communities.
These 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
The 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
These 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
Tracking, targeting and sharing
These 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.
Cookies used on Lithium JX communities
Lithium recently acquired the Jive-x community business and rebranded those communities as Lithium JX. Lithium JX communities use the following cookies:
|Cookie Name||Description and Purpose||Possible Values||Type||Expiration Time/Type|
|Used only by the Gamification module. Tracks if the user is authenticated or not. |
Cookies 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.
|true or false||3||one year|
|clickedFolder||This 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||1||at session end|
|highlightedTreeviewLink||This 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.||1||at session end|
|jive-cookie||This 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.||1||at session end|
|jive_default_editor_mode||This 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, advanced||3||30 days|
|jiveLocale||This cookie is used on the front-end for guest/anonymous users who choose a locale setting.||string, locale code||3||30 days|
|jive.login.ts||Stores the time stamp of the user's last login.||epoch time in ms||1||at session end|
|jive.mobile.redirect||This 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, NATIVE||3||one month|
|jiveRegularLoginUserCookie||This cookie is used to auto-redirect the login screen to the built-in authentication page (if the value exists and is set).||true||1||one month|
|jive.saml.passive.tried||This cookie is used to mark when SAML passive authentication has already been attempted.||true||1||3600 seconds|
|jive.security.context||This cookie is the authentication context for the user.||the user's encrypted security contex||1||30 minutes unless refreshed. Same as the standard servlet container session timeout|
|jive.server.info||This 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 localAddr||1||at sesssion end|
|jiveSSOLoginUserCookie||This cookie is used to auto-redirect the SSO screen to the built-in authentication page (if the value exists and is set).||true||1||one month|
|jiveTimeZoneID||This cookie is used on the front-end for guest/anonymous users who choose a timezone setting.||string, timezone ID||3||30 days|
|jive.user.loggedin||This 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 in||1||at session end|
|jive_wysiwygtext_height||This cookie is used on the front-end to persist the height of the editor window across sessions||integer, the height in pixels of the editor after the user chooses to expand the editor window||3||one year|
|JSESSIONID||This 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 Tomcat||1||at end of session|
|linkedin_oauth_||This cookie is used to communicate and authenticate with LinkedIn.||1|
|place_info||This 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 id||1||after place template changes are saved|
|skin.palette.preview||This cookie is used to preview the site with an unpublished template.||ID (long value) of the template||1||30 days|
|This 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.||1||defaults to 14 days|
Customer and third-party cookies on Lithium communities
Lithium customers may set additional cookies on Lithium Community in addition to the standard cookies disclosed above. These cookies are set and controlled by Lithium customers and their affiliates for various purposes such as website usage tracking (very common practice) and targeting for surveys or advertising in some cases. Lithium does not control the dissemination of such cookies. If you need more information on which additional cookies are set on the Community you are visiting, visit the community’s privacy section. You may also wish to review the How to control cookies section to view, remove, or block certain cookies. Note that disabling or removing cookies may have an adverse impact on the proper functioning of the community, and certain features may become disabled or unavailable.
Cookies set by third-party and external sites
- For Privacy related requests email privacy [at] lithium [dot] com. Use a secure communication method such as PGP or SMIME for sharing sensitive information.
- For Security related requests email security [at] lithium [dot] com. Use a secure communication method such as PGP or SMIME for sharing sensitive information.
- Read about our Security Testing and Reporting Policy at https://www.lithium.com/security.
- For sales related and general inquiries, contact your designated Account Manager or visit our website at http://www.lithium.com
- your display preferences, such as contrast colour settings or font size
- if you have already replied to a survey pop-up that asks you if the content was helpful or not (so you won't be asked again)
Also, some videos embedded in our pages use a cookie to anonymously gather statistics on how you got there and what videos you visited.
Enabling these cookies is not strictly necessary for the website to work but it will provide you with a better browsing experience. You can delete or block these cookies, but if you do that some features of this site may not work as intended.
The cookie-related information is not used to identify you personally and the pattern data is fully under our control. These cookies are not used for any purpose other than those described here.
How to control cookies
You can control and/or delete cookies as you wish – for details, see aboutcookies.org. You can delete all cookies that are already on your computer and you can set most browsers to prevent them from being placed. If you do this, however, you may have to manually adjust some preferences every time you visit a site and some services and functionalities may not work.