- Atlas
- /
- Support Center
- /
- Policies and Guidelines
- /
- Personal Data Inventory for Khoros Subscription Se...
Options
- Article History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
Personal Data Inventory for Khoros Subscription Services
Personal Data Inventory for Khoros Subscription Services
This article captures a complete inventory of personal data points used throughout Khoros products, for EU privacy compliance and other cases. These inventories are presented below in three tables:
- Khoros Communities and Khoros Care
- Khoros Marketing
- 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 Khoros features the use this personal data
Note: This information is routinely maintained and updated by Khoros Product Management. For a full listing of Khoros’s Data Locations and Subprocessors, please visit here.
Khoros Communities and Khoros Care
| Element | Source | Storage Countries | Access Locations | Third-party Usage | Retention/Deletion | Supported Lithium Features |
|---|---|---|---|---|---|---|
|
Khoros Communities
|
Khoros Communities event logs, updated daily |
|
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 |
|
|
USA |
US-SF US-Austin AWS-US IDC-Bangalore |
|
90 days; in case of opt out, no new data will be generated |
Klout scores & topics |
|
|
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 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 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
|
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 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
|
Foursquare API via user authentication (for registered Klout users who have authorized connection to Foursquare), daily |
|
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
|
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
|
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
|
Mixpanel |
Will not be renewed | |||
|
Khoros Communities
|
Khoros Communities event logs, updated daily |
|
US-SF
US-Austin AWS-US IDC-Bangalore |
|
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 |
|
Klout scores & topics | |
|
Klout.com
|
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 90 days Yesmail - deprecates before May 25 |
Klout scores & topics |
|
Response
|
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 |
|
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) |
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) |
|
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
|
Generated by Klout daily | USA |
US-SF US-Austin AWS-US IDC-Bangalore |
Klout data partners Mashery |
|
Klout scores & topics |
|
When-to-post:
|
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 Response)
|
|
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 | |
|
Khoros Community scores
|
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 | |
|
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 |
|
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 |
|
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+
|
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 |
|
Khoros Communities
|
Consumer data is retrieved through Lithium Community APIs after the company authenticates their Community with Response. All consumer data is subject to Khoros'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
|
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 |
|
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 |
|
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 |
|
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
|
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
|
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 |
|
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 |
|
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 |
|
Khoros Communities
|
Consumer data is retrieved through Khoros Community APIs after the company authenticates their Community with Response. All consumer data is subject to Khoros'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+
|
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
|
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 |
|
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 |
|
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 |
|
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 |
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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 |
| Element/Area | Source | Storage Countries | Access Locations | Third-party Usage | Retention/Deletion | Supported Spredfast Features |
| Spredfast Platform | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Initiatives to Users with visibility/access. | |
| Spredfast Platform | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Roles (named privilege sets) to Users with that role. | |
| Spredfast Platform | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Approval Groups to Users in each group. | |
| Spredfast Platform | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Labels to their creating User. | |
| Spredfast Platform | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Credentials (authenticated social media handles) to Users with visibility/access. | |
| Spredfast Platform | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Sendgrid (SaaS email vendor) | Aurora - indefinitely until 30 days post-contract | Identifies email addresses that should be contacted with Spredchat @-mentions. |
| Spredfast Platform | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
ZenDesk - If a user searches for a Help topic in the customer help center and/or submits a trouble ticket to Support, their User Profile ID is transferred to ZenDesk and stored with the Help topic search record or the trouble ticket record. | Aurora - indefinitely until 30 days post-contract | Core platform User profile details. |
| Spredfast Platform | Company Administrator-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Conversations Companies to the Users therein. | |
| Spredfast Platform | Generated nightly by the Spredfast system. | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
AWS filesystem - 1 day (deleted and re-generated nightly) | Generated nightly by the Spredfast system for select FinServ customers, and then delivered to these customers via SFTP. | |
| Spredfast Platform | Captured by Pendo as users navigate the product suite. | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Pendo (SaaS service that captures in-product feature usage) | Indefinitely at Pendo until 30 days post-contract) | Events are generated as User navigate/use the system (tying a user id to the event/action) and sent to Pendo for aggregation, analysis, and visualization. |
| Spredfast Ads | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties social network ad accounts to the users with visibility/access. | |
| Spredfast Ads | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties individual social network ads to the users with visibility/access. | |
| Spredfast Care | Generated by the Spredfast system as user actions occur. | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract Redshift - 30 days |
Ties social care agent users to their activity metrics. | |
| Spredfast Care | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Care Rules to their creating User. | |
| Spredfast Care | Sourced from supported social networks via API | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
SFDC - When leveraging the Salesforce CRM integration, whodex profile IDs are sent to the customer's Salesforce instance and paired up with a contact in that system. | Aurora - indefinitely until 30 days post-contract | Social network author account details show up next to posts in context. |
| Spredfast Care | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties notes made by social care agent users to the whodex profiles. | |
| Spredfast Analytics | Generated by the Spredfast system as user actions occur. | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Kibana - 30 days | Ties analytics exports to the user that triggered the export. | |
| Spredfast Analytics | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Analytics dashboards to the Users with visibility/access. | |
| Spredfast Publishing | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties marketing plans/campaigns to the Users with visibility/access. | |
| Spredfast Publishing | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Messages (draft social network posts) to the Users with visibility/access. | |
| Spredfast Publishing | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties Media Assets (photos, videos, etc) to the Users with visibility/access. | |
| Spredfast Moderation | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Indicates the User that made a Comment on an in-flight Messages (draft social network post). | |
| Spredfast Moderation | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Indicates the User who authored the reply to a social network post via an authenticated social handle (Credential). | |
| Spredfast Moderation | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Indicates the User who authored a retweet to a Tweet via an authenticated Twitter handle (Credential). | |
| Spredfast Experiences | User-created | USA | US - Austin AWS - US |
Aurora - indefinitely until 30 days post-contract | Indicates the User who created the Experiences Stream. | |
| Spredfast Experiences | Sourced from supported social networks via API | USA | US - Austin AWS - US |
Aurora - indefinitely until 30 days post-contract Cassandra - 7 days Memcached - 1 day |
Represents a social network post in an Experiences Stream (list/queue) of posts. | |
| Spredfast Experiences | Company Administrator-created | USA | US - Austin AWS - US |
Aurora - indefinitely until 30 days post-contract | Represents the thin shell of a User object in the Experiences product. | |
| Spredfast Experiences | User-created | USA | US - Austin AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties a Visualization to the Users with visibility/access. | |
| Spredfast Experiences | User-created | USA | US - Austin AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties a Space to the Users with visibility/access. | |
| Spredfast Experiences | User-created | USA | US - Austin AWS - US |
Aurora - indefinitely until 30 days post-contract | Ties a Spotlight Report to the Users with visibility/access. | |
| Spredfast Intelligence | Sourced from supported social networks via API | USA | US - Austin AWS - US |
Cassandra- indefinitely until 30 days post-contract | Represents searchable social network posts. | |
| Spredfast Inbox | Sourced from supported social networks via API | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Cassandra - indefinitely until 30days post-contract | Represents a social network post in an Inbox Stream (list/queue) of posts. | |
| Spredfast Inbox | User-created | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Aurora - indefinitely until 30 days post-contract | Identifies a list of social media users considered to be "influencers". | |
| Spredfast Inbox | Generated by the Spredfast system as user actions occur. | USA | US - Austin Argentina - Buenos Aires (Virtualmind contract engineering) Germany - Hamburg (Softserve contract engineering) Ukraine - Lviv (Softserve contract engineering) AWS - US |
Cassandra- 30 days post contract | Ties social care agent users to their activity metrics (live runtime data). |
| Element | Source | Storage countries | Access locations | Third-party sharing | Retention and deletion | Supported JX Features |
|---|---|---|---|---|---|---|
|
Advanced Gamification (Bunchball)
|
JX Core sends during events
|
Depends on installation
|
|
Yes (Bunchball) |
|
Gamification |
|
Advanced User Sync
|
Customer-provided CSV file |
Depends on installation
|
|
No |
|
User Authentication |
|
Basic User Sync
|
Customer-provided CSV file |
Depends on installation
|
|
No |
|
User Authentication |
|
Box Integration |
User supplied |
Depends on installation
|
|
No |
|
File sync, user can upload files to Box through Lithium-JX |
|
Cloud Analytics
|
Sent from JX Core | N/A |
|
Export to CSV |
|
|
|
Cloud Search
|
Sent from JX Core | N/A |
|
No |
|
People, places, and content search |
|
Core Platform
These fields are part of the "User Profile", but these are special in that they are typically enter initially by the corporate administrator or system. |
|
Depends on installation
|
|
Userid is shared to Bunchball |
|
User Authentication |
|
Core Platform
|
User supplied |
Depends on installation
|
|
No |
|
|
|
Core Platform
|
User supplied |
Depends on installation
|
|
Record Retention: (SMTP, Actiance) |
|
|
|
Core Platform
|
User supplied |
Depends on installation
|
|
No |
|
|
|
Core Platform
|
User created |
Depends on installation
|
|
Events may trigger pulls of content by add-ons Perceptive (For Videos) Storage integrations: Box, Dropbox, Google Docs, Sharepoint |
|
|
|
CMR Analytics
|
JX Core sends during events |
Depends on installation
|
|
No |
|
Analytics |
|
Email Module
|
N/A |
N/A |
|
No |
|
|
|
Ideation
|
User created | N/A |
|
No |
|
|
|
JX for Google
|
Obtained from 3rd-party during setup and synchronization | N/A |
|
No |
Disk Storage
|
User Authentication |
|
JX Rewards (Playbox)
|
JX Core sends during events | N/A |
|
Data can be exported |
|
|
|
Streamonce
|
Obtained from 3rd-party during setup and synchronization | N/A |
|
|
|
|
|
People Search
|
Sent from JX Core |
Depends on installation
|
|
No |
|
|
|
Recommender
|
JX sends during events |
|
No |
|
N/A | |
|
Records Retention
|
JX sends during events | Refer to Data Storage Locations |
|
Options of where to send data: to an email, on a hard drive in csv format, actiance | Defined by customer | |
|
Resonata
|
Retrieved from JX Core via API calls | Refer to Data Storage Locations |
|
We have scrapers:
We can send personal data:
|
|
|
|
Search:
|
JX Core sends during events | Refer to Data Storage Locations |
|
No |
|
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 |
