Lithosphere The Lithium Community

Policies and Guidelines

Policies and Guidelines

Filter
Filter by Labels
Select any of the labels below to filter results.
Filters applied...
Sorted by:
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.   Type Classification Description Example 1 Strictly necessary 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 2 Performance 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 3 Functional 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 4 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.  How to control cookies Some cookies are necessary for the proper operation of the Community and disabling or removing them may have an adverse impact on the proper functioning and user experience. However, users may choose to view, block, or remove cookies set by Lithium Community through their web browser settings (or any website cookies for that matter). Consult the help feature for your specific browser to find how. Here are some useful links for your convenience. Microsoft Internet Explorer Privacy Settings and Information Google Chrome Privacy Settings and Information Mozilla Firefox Privacy Settings and Information Apple Safari Privacy Settings and Information Also, you may choose to consult an external and independent third party website such as  AboutCookies.org or www.youronlinechoices.eu/ if you are in the European Union which provides comprehensive information on a variety of browsers and how to control or change their respective privacy settings. Cookies used by Lithium The following standard cookies are used by Lithium Community, Social Media Management, and Lithium Social Intelligence (LSI). Disabling or removing these cookies may have an adverse impact on the proper functioning and user experience on the Community. Community cookies Cookie Name Type Description and Purpose Expiration Time/Type If removed, disabled, or not accepted _ga 2 Distinguishes users using a unique ID. It is used by Google Analytics to calculate visitor, session, and campaign data. By default, the configuration setting that sets this cookie is disabled. 2 years (persistent) Visitor and session data will not be tracked and will not be available to Google Analytics !lithiumSSO:{client_id} 1 Used for passing authentication information to Lithium session SSO will not be functional for the user LiSESSIONID 1 Session management session User cannot log in, and is treated as an anonymous user ­­lia.anon.{setting or config name} 3 Stores community-wide configurations and settings for anonymous users 1 year (persistent) Community behavior will follow defaults and any UI convenience changes made by the user will be ignored. liSdkOptions:{communityId} 3 Dropped when a Studio user navigates to Studio > Advanced > SDK and clicks Submit after checking the View as anonymous checkbox.   The cookie allows developers to sign out of the community but still have it find the URL to use for rendering a skin that is hosted via the Community Plugin SDK.   This cookie is used only on stage sites. 1 month or when the View as anonymous checkbox is unselected The community will serve the URL for the skin set on the stage site instead of the URL to the locally hosted skin (so local SASS development will not work when the user is signed out) lithium.anonymous. usersetting.{setting name} 3 Remembers user preferences 1 year (persistent) The community will not remember the user’s setting preferences lithium.anonymous. usersetting.profile. language 3 Remembers language preferences 1 year (persistent) The community will not remember the user’s language preferences. The language will default to the native language defined for the community. lithiumLogin:{community id} 3 Keeps users logged in when they make a request after their session has expired. It is triggered when a user checks Save login name and password. The cookie is encrypted and includes a unique user secure ID in the database. 30 days (persistent) The "auto login" and "remember me" features will not work LithiumNotifications 3 Temporarily stores Realtime Notification messages (Toast messages) session Realtime notification toasts may not appear (pop-up) after a page transition. LithiumUserInfo 1 Session management session The user will not be able to view secure pages and will be redirected to the login page LithiumVisitor 4 Replaces VISITOR_BEACON. Lithium currently uses both for backward compatibility. This cookie computes billing visits, registered billing visits, visits, registered visits, and unique visitors metrics. The cookie is encrypted and stores when it was first issued, when it was last seen by Lithium, an unique visitor ID (which is unique per visitor’s browser). Configurable (Default = 10 years)  Note: To change the default value, contact Lithium Support. Visits and unique visitors metrics will not be accurate. There will be a new billable visit on each new request. Customers on billing visits model will be affected. P{poll_id}U{user_id}R{reset_count} 3 Tracks when a user has voted in a poll and tracks the answer value. The cookie is used to prevent a user from voting multiple times in a single poll. The cookie is only placed if Use cookies to prevent multiple votes is enabled in Community Admin. 1,000000+ days (persistent) If the user is an anonymous user, the user will be able to vote multiple times when the cookie is cleared. If the user is logged in, votes, and then clears the cookie, they are not allowed to revote. PushyAuthToken 1 Authenticates the user for a session with Realtime Notifications service (Pushy) Manually cleared when the user logs out or when their session expires due to inactivity WebSocket connections to the Realtime Notification service will fail with a 403 Forbidden error and the user will not see realtime notifications. VISITOR_BEACON 4 Computes billing visits, registered billing visits, visits, registered visits, and unique visitors metrics. The cookie is encrypted and stores, when it was first issued, when it was last seen by Lithium, the user ID, and its own unique ID. Configurable  (Default = 10 years) Note:  To change the  default value, contact Lithium Support. Visits and unique visitors metrics will not be accurate. There will be a new billable visit on each new request. Customers on billing visits model will be affected. VISITORID 1 Distinguishes between human and bot traffic 3 years (session) Defeats the bot detection mechanism. (May see increased spam on the community.) ValueSurveyParticipation 3 Stores a timestamp storing the creation time of this cookie, which is used in value survey trigger logic.   Default is 90 days. Configurable in Community Admin The user will get multiple prompts to take a survey ValueSurveyVisitorCount 3 Stores the survey visit count of the user, which is used in logic that determines when a survey is triggered. This cookie is used in conjunction with the ValueSurveyParticipation cookie. When the ValueSurveyParticiation is set, the count for ValueSurveyVisitorCount cookie is reset to 0. Expires when the ValueSurveyParticipation cookie is either set or expires The user will not be prompted to take a survey until the count defined in the Delay before prompting user with survey field in Community Admin > Features > Value Surveys > Settings is met. Social Media Management cookies Social Media Management Cookies Cookie Name Type Description and Purpose Expiration Time/Type If removed, disabled, or not accepted X-TOKEN-ID 1 Protects against cross-site scripting Session This is a security token. It is critical for the application to run PLAY_SESSION 1 This is the main session cookie Session This is the main session cookie. It is critical for the application to run __sdx_page 3 Stores the user’s current application tab 14 days When a user reloads the page, the user is redirected to the default tab instead of to the last tab used in the application PLAY_LANG 3 Retrieves the user’s language 14 days This is used only when LSW cannot detect the browser language and a user has no language set Social Media Management Analytics Cookies Cookie Name Type Description and Purpose Expiration Time/Type If removed, disabled, or not accepted XSessionID 1 This is the main session cookie 24 hours This is the main session cookie. It is critical for the application to run JSESSIONID 3 This is an auto-generated JSP cookie Session The application does not rely on this cookie but uses the cookie occasionally to auto-generate UUIDs LSW Publisher Cookies Cookie Name Type Description and Purpose Expiration Time/Type If removed, disabled, or not accepted TOCOMA-CID 1 The user’s main session cookie Expires when the browser session ends The application will not run LSI cookies Cookie Name Type Description and Purpose Expiration Time/Type If removed, disabled, or not accepted SIP|ws 3 Tracks the workspace to redirect to after a session timeout 1 day   All Lithium Community cookies also apply to LSI   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 Communities may contain embedded images, videos, and links to external and third-party websites. Lithium customers may also include syndicated content on their communities such as banner ads and similar embedded objects from their affiliates and partners. As a result, when you click on such an object you may be presented with cookies from the owner of that respective website where the content is hosted. Lithium does not control the dissemination of such cookies. Contact the relevant third party website for their privacy policy and cookie information. 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 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 anonymous Used only by the Gamification module. Tracks if the user is authenticated or not. true or false 3 one year BIGipServer   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.   2   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 containerSecurityToken Used for RPC and Proxy Calls (Shindig Token) in loading app data in iFrames String, alphanumeric  1  configurable, defaults to 1 hour 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.login.type Stores the type of login that was performed, either true native Lithium-JX login or via SSO String, either "form" or "saml" 1 30 days 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 (one hour) 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 session 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.senttoidp Used to indicate whether a user has logged in with an SSO authority, used in conjunction with the "require explicit first time login" feature string, true 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 session end 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 long lived. 30 days SPRING_SECURITY_REMEMBER_ME_COOKIE 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 X-JCAPI-TOKEN Legacy csrf token, only in use in the mobile apps, set only to provide backwards compatibility String, random with 8-character length 1 1 year   Contact Lithium For Privacy related requests email privacy [at] lithium [dot] com. Use a secure communication method such as PGP or SMIME for sharing sensitive information. Find Lithium’s Privacy Policy at http://www.lithium.com/privacy. 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
View full article
by Retired Community Manager JennC Retired Community Manager 07-20-2016 01:57 PM
Labels (3)
0
14097
This article captures a complete inventory of personal data points used throughout Lithium products, for EU privacy compliance and other cases. These inventories are presented below in two tables: Lithium Communities and Social Media Management Lithium JX Personal data is a broader category than directly identifiable information like names, email addresses, and phone numbers. It also includes: Internal IDs or other anonymized but indirectly identifiable data "Public" data like Twitter posts Metadata or annotations Lithium generates about a person The following table provides the following information: Element: The type of personal data Source: Where the personal data originates from Storage Countries: The geographical location(s) where the personal data is stored Access Locations: The  geographical location(s) where this personal data can be accessed from by a user or system Third-party Usage: List of third-party entities that use this data and where/how it is used Retention/Deletion: Description of how long the personal data is stored before deletion Supported Lithium Features: List of Lithium features the use this personal data Note:   This information is routinely maintained and updated by Lithium Product Management.   Lithium Communities and Social Media Management inventory   Element Source Storage Countries Access Locations Third-party Usage Retention/Deletion Supported Lithium Features Lithium Communities User IDs User display names Message content Kudos Answers Replies Questions Ideas Comments Conversations Review Accepted solutions Views (anonymous / user / robot) Lithium Communities event logs, updated daily USA (all communities) USA backup: also USA Netherlands (EMEA communities only) Netherlands backup: Ireland US-SF US-Austin AWS-US IDC-Bangalore   Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated Klout scores & topics Twitter Twitter user IDs Twitter handles Twitter live stream via GNIP which includes all public mentions and retweets Twitter API via user authentication token (only for registered Klout users who have authorized connection to Twitter), daily USA US-SF US-Austin AWS-US IDC-Bangalore Klout data partners Mashery 90 days ; in case of opt out, no new data will be generated Klout scores & topics Twitter Profiles (can include name, bio, location, birthday, URL) Follower Twitter IDs Following Twitter IDs Tweets (text only) Retweets of the user's tweets by others Mentions of the user's handle by others (replies) Public list memberships assigned by others Aggregate favorite/like counts on a tweet (in dev) Location checkins in a tweet (in dev) Twitter l ive stream via GNIP which includes all public mentions and retweets Twitter API via user authentication token (only for registered Klout users who have authorized connection to Twitter), daily USA US-SF US-Austin AWS-US IDC-Bangalore Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated Klout scores & topics Facebook For registered Klout user: Facebook user IDs Names Profiles (can include name, location, birthday, gender, URL) Likes of the user's postings by others Comments on the user's posts by others Wall posts (text only) Friend IDs and names For registered Klout user's Facebook friends (if the registering user can access): Facebook app user IDs (Facebook generates these on the fly for a given app) Names If the friend is also a registered Klout user, the full profile Facebook API via user authentication token (for registered Klout users who have authorized connection to Facebook), daily Registered and Facebook-connected Klout user's friends' app-dependent ID, name, and profile URL are collected daily USA US-SF US-Austin AWS-US IDC-Bangalore Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated   Klout scores & topics Instagram For registered Klout user: User ID Handle Profile Profile image URL Followers Likes of the user's postings by others Comments on the user's postings by others Posts (images stored as Instagram links only) For registered Klout user's Instagram connections Instagram user IDs Instagram usernames Instagram API via user authentication (for registered Klout users who have authorized connection to Instagram), daily USA US-SF US-Austin AWS-US IDC-Bangalore Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated   Klout scores & topics Google Plus For registered Klout user: User IDs Handles Skills Birthday Gender Organizations Location Publicly visible posts (text only) Comments +1’s (posting endorsements) Reshares ( on user's personal profile only) For registered users' connections: Google Plus user IDs Names usernames Google Plus API via user authentication (for registered Klout users who have authorized connection to Google Plus), daily.   USA US-SF US-Austin AWS-US IDC-Bangalore Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated Klout scores & topics LinkedIn For registered users: User IDs Names Location Number of connections Job titles Specialties Summary Profile image URL Recommendations Education Posts (text only) Comments ( on user's personal profile only) LinkedIn API via user authentication (for registered Klout users who have authorized connection to LinkedIn), daily USA US-SF US-Austin AWS-US IDC-Bangalore Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated   Klout scores & topics Foursquare For registered Klout users: User IDs Names City Gender Bio Tips saved by others Tips liked by others Friends Check-ins (with geocoordinates) Likes For registered Klout users' Foursquare friends Foursquare IDs Foursquare API via user authentication (for registered Klout users who have authorized connection to Foursquare), daily USA US-SF US-Austin AWS-US IDC-Bangalore Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated Klout scores & topics YouTube User IDs Messages Aggregated views Aggregated likes Aggregated dislikes Post comments YouTube API via user authentication (for registered Klout users who have authorized connection to YouTube), daily USA US-SF US-Austin AWS-US IDC-Bangalore Profile link visible on Klout profile page (for registered users who have authorized connection) 90 days ; in case of opt out, no new data will be generated       Klout scores & topics Klout.com User ID Generated by Klout as needed USA US-SF US-Austin AWS-US IDC-Bangalore Klout data partners Mashery 90 days ; in case of opt out, no new data will be generated Klout scores & topics Mixpanel browser cookie Generated by Klout as needed __utma __utmb __utmc __utmt __utmz _cb _cb_ls _chartbeat2 mp_{id}_mixpanel mp_klout__c nksidd mc     Mixpanel  Will not be renewed   Lithium Communities User IDs User display names Message content Kudos Answers Replies Questions Ideas Comments Conversations Review Accepted solutions Views (anonymous / user / robot) Email Login Name SSO Id VisitorId QueryString SessionId BeaconVisitorId IP Address User Agent Request Headers  Lithium Communities event logs, updated daily USA (US Communities) Netherlands and Ireland    US-SF US-Austin AWS-US IDC-Bangalore Bulk Data API shared with authorized Lithium Customers Community metrics shared with authorized Lithium customers via LSI and SMM 30 days, in case of a user deletion request   Social identity mappings (matching Klout user ID with network user IDs for a given person) Generated by Klout as needed USA US-SF US-Austin AWS-US IDC-Bangalore   90 days  (MySQL) - keep only currently connected network tokens 90 days (HDFS) 7 days (AWS) Klout scores & topics Klout.com Names Profiles Emails Addresses Phones Ages IsABrand flag +K (user-to-user topic endorsements) User-chosen topics OAuth user tokens for connected networks Perks activity (up to April 2016) Provided by Klout.com users at registration, most profile fields optional/often blank USA US-SF US-Austin AWS-US IDC-Bangalore Yesmail (profiles, connected networks) Name visible on Klout profile (for logged-in users) 90 days  (MySQL) - keep only current profile fields 90 days  (internal HDFS) - plan to trim to 180 days Yesmail - deprecates before May 25 Klout scores & topics Social Response Network Message IDs (where Twitter users are interacting with a client company) Message text Actionability label (actionable or non-actionable) Social Response logs ported to Klout daily USA US-SF US-Austin IDC-Bangalore   7 days (HDFS) Social Response 1st degree user graphs Generated by Klout daily USA US-SF US-Austin AWS-US IDC-Bangalore   7 days (1st degree) 3 days (2nd degree) 7 days (AWS) Klout scores & topics Klout scores Generated by Klout daily USA US-SF US-Austin AWS-US IDC-Bangalore Klout data partners, Mashery Yesmail (registered Klout users) 90 days (internal HDFS) 7 days (Klout data partners) 4 hours (Mashery) Yesmail -  deprecates before May 25 Klout scores & topics Per-network scores, % of score attributable to network Generated by Klout daily USA US-SF US-Austin AWS-US IDC-Bangalore   30 days Klout scores & topics Klout user topics Generated by Klout daily USA US-SF US-Austin AWS-US IDC-Bangalore Klout data partners Mashery Yesmail (registered Klout users) 14 days (HDFS) 7 days (Data partners via AWS) 4 hours (Mashery) Yesmail deprecates before May 25 Klout scores & topics Per-network user-topic features Generated by Klout daily USA US-SF US-Austin AWS-US IDC-Bangalore   90 days (HDFS) Klout scores & topics Klout user derived locations Generated by Klout daily USA US-SF US-Austin AWS-US IDC-Bangalore   3 days (HFS) Klout scores & topics User-user SOI ("Strength of Influence") scores Klout IDs Relationship type (influencer, influencee) Generated by Klout daily USA US-SF US-Austin AWS-US IDC-Bangalore Klout data partners Mashery 3 days (HDFS) 7 days (Data partners via AWS) 4 hours (Mashery) Klout scores & topics When-to-post: Audience schedule profiles by Twitter handle and network Recommended posting times Generated by Klout weekly USA US-SF US-Austin AWS-US IDC-Bangalore   30 days (HDFS) Social Response User audience sentiment (aggregate stats on the sentiment of posts interacting with the user within the week) Generated by Klout weekly USA US-SF US-Austin AWS-US IDC-Bangalore   90 days (HDFS) Social Impact Ranking, SMM Analytics Content discovery feed (Klout.com and Social Response ) URLs/articles (will contain personal information only if included as part of article text) Twitter handles detected in URLs URLs parsed out of network post data URLs collected via publicly available RSS feeds TW handles parsed out of URLs when present (usually as part of byline) USA US-SF US-Austin AWS-US IDC-Bangalore   90 days (HDFS) Klout.com, Social Response Klout.com recommended experts Generated by Klout weekly USA US-SF US-Austin AWS-US IDC-Bangalore   7 days (HDFS) Klout.com Klout user-entity scores Generated by Klout weekly USA US-SF US-Austin AWS-US IDC-Bangalore   90 days (HDFS) Klout scores & topics Lithium Community scores Top users by score Top users by topic Community health score Generated by Klout weekly USA US-SF US-Austin AWS-US IDC-Bangalore   14 days (HDFS) Lithium Communities Klout.com event logs Generated by Klout daily USA US-SF   90 days Klout.com Twitter Name Screen Name Social Handle Profile Image Location Coordinates Country Code Tweet contents Consumer data is retrieved through Twitter APIs after the company authenticates their Twitter Handle(s) with Response.  All consumer data is subject to Twitter's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contact. Tweets are also deleted in SMM based on Twitter notification. Social Response, Analytics Facebook Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through Facebook APIs after the company authenticates their Facebook Page(s) with Response.  All consumer data is subject to Facebook's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. User comments deleted in Facebook will also be deleted in SMM based on Facebook notification. Social  Response, Analytics Instagram Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through Instagram APIs after the company authenticates their Instagram Page(s) with Response.  All consumer data is subject to Instagram's Terms of Use. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social  Response, Analytics Google+ Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through Google+ APIs after the company authenticates their Google+ Page(s) with Response.  All consumer data is subject to Google's Terms of Use. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response, Analytics Lithium Communities Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through Lithium Community APIs after the company authenticates their Community with Response.  All consumer data is subject to Lithium's Terms of Service.  US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response, Analytics YouTube Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through YouTube APIs after the company authenticates their YouTube Channel(s) with Response.  All consumer data is subject to YouTube's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract.  Social  Response, Analytics Pinterest Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through Pinterest APIs after the company authenticates their Pinterest Page(s) with Response.  All consumer data is subject to Pinterest's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract.  Social  Response, Analytics LinkedIn Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through LinkedIn APIs after the company authenticates their LinkedIn Page(s) with Response.  All consumer data is subject to LinkedIn's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract.  Social  Response, Analytics WeChat Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through WeChat's APIs after the company authenticates their WeChat Account(s) with Response.  All consumer data is subject to WeChat's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Response, Analytics Radian6 Name Screen Name Social Handle Profile Image Location Coordinates Country Code Post contents Consumer data is retrieved through Radian6 APIs after the company authenticates their Radian6 Account(s) with Response.  All consumer data is subject to Radian6's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response, Analytics Smooch Chat contents Within a secure chat, provided by Smooch, consumers will share unstructured PII (i.e. the information will be shared within a chat conversation). This data will be ingested into Response. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response, Secure Messaging, Analytics Twitter Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through Twitter APIs after the company authenticates their Twitter Handle(s) with Response.  All consumer data is subject to Twitter's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Tweets deleted in Twitter will also be deleted in SMM based on Twitter notification . Social Response , Analytics Facebook Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through Facebook APIs after the company authenticates their Facebook Page(s) with Response.  All consumer data is subject to Facebook's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. User comments deleted in Facebook will also be deleted in SMM based on Facebook notification. Social Response , Analytics Lithium Communities Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through Lithium Community APIs after the company authenticates their Community with Response.  All consumer data is subject to Lithium's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics Google+ Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through Google+ APIs after the company authenticates their Google+ Page(s) with Response.  All consumer data is subject to Google's Terms of Use. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics YouTube Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through YouTube APIs after the company authenticates their YouTube Channel(s) with Response.  All consumer data is subject to YouTube's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics Instagram Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through Instagram APIs after the company authenticates their Instagram Page(s) with Response.  All consumer data is subject to Instagram's Terms of Use. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics LinkedIn Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through LinkedIn APIs after the company authenticates their LinkedIn Page(s) with Response.  All consumer data is subject to LinkedIn's Terms of Service.  US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics Pinterest Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through Pinterest APIs after the company authenticates their Pinterest Page(s) with Response.  All consumer data is subject to Pinterest's Terms of Service.  US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics WeChat Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through WeChat's APIs after the company authenticates their WeChat Account(s) with Response.  All consumer data is subject to WeChat's Terms of Service. US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics Radian6 Author Bio Full Name Klout Score profilePicture: caption httpUrl httpsUrl username Post Contents Consumer data is retrieved through Radian6 APIs after the company authenticates their Radian6 Account(s) with Response.  All consumer data is subject to Radian6's Terms of Service.  US & Ireland US-SF US-Austin IDC-Bangalore No Deleted within 30 days of end of customer contract. Social Response , Analytics Community Author login (username) email address (except privacy guard) salted password hash (except SSO) SSO - from SSO identity provider (usually customer's propitiatory identity system via SSO cookie). Local with migration - from PS team or Administrator importing the info Local without migration - from users through initial registration US - San Jose EMEA - Amsterdam From any where using web UI or API Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) Mysql, Elasticsearch, Cassendra - indefinitely. Redis - 24 hours Lithium Communities Community Author userId Created during the first initial interaction to the system, may it be SSO or import or registration US - San Jose EMEA - Amsterdam From any where using web UI or API Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) Mysql, Elasticsearch, Cassendra - indefinitely. Redis - 24 hours Lithium Communities Community Author ICQ (optional) AIM (optional) Skype   (optional) MSN   (optional) Yahoo   (optional) Bio   (optional) Custom personal data fields (customizable per community) Entered by user either through initial registration or sub-sequential interaction with the community. For custom personal data fields, it could also possible be from SSO cookie. US - San Jose EMEA - Amsterdam From any where using web UI or API Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) Mysql, Elasticsearch, Cassendra - indefinitely. Redis - 24 hours Except required custom fields, all are optional not related to any feature supported Community Author Twitter access token Entered by user either through initial registration or sub-sequential interaction with the community US - San Jose EMEA - Amsterdam subprocessor is twitter api Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) Mysql - indefinitely. Twitter integration Community Author Facebook access token Entered by user either through initial registration or sub-sequential interaction with the community US - San Jose EMEA - Amsterdam subprocessor is facebook api Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) Mysql - indefinitely.   Facebook connect and integration Community Author profilePicture Entered by user either through initial registration or sub-sequential interaction with the community US - San Jose EMEA - Amsterdam From any where using web UI or API Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) NFS - indefinitely. Profile pic Community Author ip address browser cookie string user agent http referrer headers From the http requests to the community US - San Jose EMEA - Amsterdam No accessible Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) Mysql - indefinitely. Redis - 24 hours Lithium Communities Community User Metrics Total Messages Posted Total Page Views Total Messages Read Board Topics Started Board Replies Blog Articles Posted Blog Comments Posted Ideas Posted Idea Comments Posted Questions Posted Q&A Replies Posted Answers Posted Q&A Comments Posted Total Board Views Total Logins Total Minutes Online Created by the community US - San Jose EMEA - Amsterdam From any where using web UI or API Yes (Sumologic, Akismet, Aalesforce, Dynamics Cloud Elements, Akamai, Edgecast) Mysql, Elasticsearch indefinitely. Redis - 24 hours Lithium Communities   Lithium JX inventory   Element Source Storage countries Access locations Third-party sharing Retention and deletion Supported JX Features Advanced Gamification (Bunchball) User ID Lithium-JX Core sends during events   Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations   US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Yes (Bunchball) Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Gamification Advanced User Sync First name Last name Email Password Customer-provided CSV file Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Authentication Basic User Sync First name Last name Email Password Customer-provided CSV file Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Authentication Box Integration email User supplied Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days File sync, user can upload files to Box through Lithium-JX Cloud Analytics User Profile Custom Fields Content Sent from Lithium-JX Core N/A US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Export to CSV Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Community Analytics Data Export Service (DES) Personal Insights Impact Metrics Cloud Search userid username, first name last name @mentions Sent from Lithium-JX Core N/A US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days People, places, and content search Core Platform User Full Name Password Email These fields are part of the "User Profile", but these are special in that they are typically enter initally by the corporate administrator or system. Corporate SSO/Identity Provider Imported via Corporate-supplied spreadsheet containing user data Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Userid is shared to Bunchball Core: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Analytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Cloudalytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Search: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Authentication Core Platform User Image Avatar User supplied Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Core: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Analytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Cloudalytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Search: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Profile Analytics People Search Core Platform User Profile Custom Fields User supplied Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Record Retention: (SMTP, Actiance) Core: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Analytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Cloudalytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Search: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Profile Analytics People Search Core Platform User ID Skill User supplied Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Core: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Analytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Cloudalytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Search: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Profile Analytics People Search Core Platform Content User created Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Events may trigger pulls of content by add-ons Perceptive (For Videos)   Storage integrations: Box, Dropbox, Google Docs, Sharepoint Core: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Analytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Cloudalytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Search: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Profile Analytics People Search CMR Analytics Content User Profile Lithium-JX Core sends during events Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Analytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Cloudalytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Analytics Email Module N/A - Emails are sent without storing  N/A N/A US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No If logging is turned on, any information logged gets deleted after 90 days   Ideation Idea (type of Content) @mentions VoterUserId AuthorUserId User created N/A US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Core: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Analytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Cloudalytics: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days Search: Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days   JX for Google username password (auth token) Email Obtained from 3rd-party during setup and synchronization N/A US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Disk Storage Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days User Authentication JX Rewards (Playbox) email username firstname lastname Lithium-JX Core sends during events N/A US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Data can be exported Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days   Streamonce username password (auth token) Email  Obtained from 3rd-party during setup and synchronization N/A US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Exchange google drive/gmail/groups facebook GitHub Evernote Salesforce Jira DropBox Bugzilla Twitter Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days   People Search User profile taken from CoreDB Sent from Lithium-JX Core Depends on installation On Prem: Customer's data center Hosted and Cloud: Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days   Recommender Userid Lithium-JX sends during events Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days N/A Records Retention Content User Profile Lithium-JX sends during events Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) Options of where to send data: to an email, on a hard drive in csv format, actiance Defined by customer   Resonata title manager business unit biography title followers following official address N official city location department code official post code hr contact COOKIES for the 2 web resonata web pages Retrieved from Lithium-JX Core via API calls Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) We have scrapers: Twitter Reddit Also any custom one can be added We can send personal data: via email with reports via JX-community notification export in csv format Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days   Search: Content User Profile Lithium-JX Core sends during events Refer to Data Storage Locations US - Portland Argentina - Junin (Clarotest Consulting Lab - Engineering services) No Deleted at customer's direction Deleted within 30 days of end of customer contract. Backups/logs: 90 days   Lithium JX Data Storage Locations Geographic Location Location Details Facility Vendor Additional Facility Detail Purpose North America Phoenix, AZ IO   Primary site for Cloud and Hosted Customers North America Edison, NJ IO   Backup Location EU Amsterdam, Netherlands Equinox (formerly Telecity)   Primary site for Cloud and Hosted Customers EU London, England Equinox (formerly Telecity)   Backup Location            
View full article
by Lithium Technologies JohnD Lithium Technologies 04-13-2018 11:59 AM
0
800
Data Retention Customer data is retained for the duration of the customer’s contract with Lithium, unless otherwise instructed by the customer. When the contract ends, Lithium Support contacts the customer to offer data return. Then, after the data has been returned or declined by the customer, the data is deleted. Deletion occurs within thirty days with the following exceptions: Data on back up systems or media is maintained for 90 days in order to maintain sound business continuity practices and then deleted Log files are maintained for up to twelve months for security reasons and then deleted Klout data for which Lithium acts as a controller is retained for longer periods of time based on Lithium’s legitimate interested in maintaining the integrity of Klout analysis that is dependent on historical data. During and after the life of the contract, Lithium can use aggregated and anonymized data for metrics and reporting purpose. This data does not include any personal information nor any information about the customer or the end user. Data Backup and Restoration Information on backup tapes is encrypted using AES 256-bit information and tapes are over written every ninety (90) days. Access to the backup tapes is restricted to authorized individuals. Offsite tapes are kept in a secure facility. Backups are made daily and full backups weekly. We conduct backup restoration testing every six (6) months, in January and July. Data Destruction When the contract ends, if the customer wishes to have a copy of the data, we provide the information to the customer in an XML format via our secure SFTP servers. The information on the SFTP servers remain intact for 30 days after which time it is deleted, unless otherwise instructed by the customer. The active data bases are also dropped from the production servers as well after the XML extraction is transferred to the customer. After the media used for storage is retired, it is scrubbed or destroyed using NIST SP 800-88 guidelines.
View full article
by Community Manager Community Manager Community Manager 04-11-2018 01:49 PM
Labels (1)
0
500
Lithium's steps to ensure GDPR Compliance
View full article
by Lithium Alumni (Retired) Lithium Alumni (Retired) Lithium Alumni (Retired) 04-27-2017 10:05 AM
11
8299
The following companies are subprocessors to Lithium, Inc.: AWS (locations in the USA and Ireland) Sumo Logic (AWS locations in the USA) Akismet (location in the USA) Persistent (location in India) Netmania (locations in Bulgaria and UK) Infogain Corporation (formerly Blue Star Infotech America, Inc.) (locations in the US and India) Hinterlands Consultancy Pty. Limited (locations in Australia) Akamai Technologies, Inc. (locations are global; for listing see Akamai site at https://www.akamai.com/us/en/locations.jsp) Infoesearch Information Technology Enabled Services, a Private Limited Company (location in India) ServiceRocket, Inc. (locations in the USA) Clarotest Consulting Lab (location in Argentina) Smooch Technologies, Inc. (AWS locations in the USA) Netbase Solutions, Inc. (locations in the USA) iTalent Corporation (locations in the USA, India and UK) Social Edge Consulting, LLC (locations in the USA, Canada, UK, Portugal and Spain   Lithium also utilizes the following subprocessors to provide certain optional services to those Lithium customers to elect to purchase those optional services: Ooyala, Inc. (locations in USA, Australia, Mexico, Singapore, UK, Spain, France, Germany, Sweden) (video storage and playback option) Box, Inc. (locations in USA) (file preview option) Cloud Elements, Inc. (locations in the US and Ireland) (API integration with customer’s CRM application)   Effective October 3, 2017, Lithium acquired the Jive-x external community platform from Jive Software, an Aurea company. As a result Lithium entered into a transition services agreement with Jive that will allow Jive, functioning as a subprocessor, to continue to provide Jive-x services for 12 to 15 months.    Lithium also utilizes subcontractors that do not have any access to our customer’s data, such as, for example, Equinix and Wave Business which maintain data center facilities hosting Lithium’s main US-based data centers.   If you have any questions, please contact your Lithium Customer Success Representative. For more information about our subprocessors, you may request a copy of the Lithium Data Location and Subprocessor Guide by emailing legal@lithium.com
View full article
by Lithium Technologies LithiumPrivacy Lithium Technologies 10-21-2015 03:58 PM
Labels (1)
0
3101
Top Contributors