Data Security FAQs

SearchUnify offers a multitenant edition and two single editions

There is no out-of-the-box migration from the Data Center Edition or the SUP Edition to the Cloud Edition.

SearchUnify stores encrypted access/refresh tokens for content sources (Lithium, Salesforce, Jive etc.). These credentials are stored to synchronize the content in the SearchUnify index.

All the authentication access tokens/refresh tokens stored in the middleware are encrypted using AES-256 encryption algorithm.

It depends upon what content needs to be made searchable via SearchUnify. For example, in a Lithium community, SearchUnify supports searching ideas, discussions, blogs etc. So, these content pieces will be stored in the search index.

SearchUnify uses the standard platform REST APIs on SSL for all the content sources. For websites, Apache-based crawlers are used to crawl the websites and index the content.

SearchUnify automatically updates its crawlers whenever there is a release upgrade of any of the SaaS-based content source.

Only those content items which a user has access to, show up in search results. For example, in the case of a Jive community, a user can see only that content in search results which belongs to the groups that he/she has access to.

Yes, access to the SearchUnify admin panel is fully encrypted.

  • The data at rest is encrypted using AES-256, ensuring that any stored data remains secure.

  • The data in transit is encrypted using TLS 1.2 and 1.3, safeguarding it from unauthorized access during transmission.

SearchUnify retains statistical data from the production environment for a period of one year.

If your team needs to remove or delete this data before the retention period expires, please contact the SearchUnify support team to initiate the process. The support team will ensure that the data is securely deleted in accordance with your request.