Coveo processes two distinct forms of customer data: index data and analytics data. This article describes those two forms of data, and outlines how customers can meet data privacy and compliance requirements.
Any item that you send to Coveo Cloud for unified indexing is part of index data. Coveo Cloud uses this data to provide relevant search results and recommendations to your end-users.
Index data is a binary deconstruction of your indexed content, compressed using proprietary algorithms, and encrypted at rest using AES-256. Index data can contain an HTML representation of the original content and can contain personal data.
Analytics Data is the information reflecting the access or use of the Cloud Services by the end users of a Coveo-powered solution. It includes end-user profile, visit, session, impression, click-through and click stream data, as well as the statistical analysis made available to you through your account with Coveo. See Understanding Usage Analytics Events.
Performance data is information related to use of the products in an aggregated and anonymized form based upon analytics data. Performance data does not reveal the identity or traits of any particular individual person. Coveo uses performance data for its internal business purposes to measure and enhance the functionality and operation of the Coveo Cloud.
Coveo has appointed a Chief Information Security Officer and a Data Protection Officer to oversee compliance with regulations, such as HIPAA, GDPR, CCPA, and PIPEDA. Coveo is committed to providing services that facilitate compliance with relevant privacy legislation. In this regard, Coveo offers control mechanisms relative to both index data and analytics data.
Customers have total control as to what information is indexed. Therefore, Customers can decide what information is or is not processed by Coveo to meet their compliance requirements. See Adding and Managing Sources.
Index data cannot be anonymized or de-identified as it will constantly reflect data contained in original source systems in order to provide the search results.
Customers have complete control to disable, obfuscate, or encrypt any usage analytics. In other words, it is possible to anonymize and de-identify analytics data. See Can I Disable Coveo Usage Analytics in a Search Interface?
Coveo does not keep IP addresses and instead uses a generated unidentifiable unique identifier based on a non-reversible operation (hash) on the IP address.
Coveo provides GDPR-compliant consent/withdrawal mechanism to restrict the information collected as analytics data. Therefore, Customers who rely on consent as a mechanism for collection can provide an opt-out mechanism to users. Furthermore, Coveo makes services such as API endpoints available to help customers respond to user GDPR requests.
See the Compliance section for further information on GDPR and HIPAA.