Last updated: Jun 19 2018
The data that is collected in Episerver Find is by default the same data as being stored in the CMS/Commerce database. Data collected by Episerver Find should not include any PII data.
Collecting statistics about searched and clicked data can be done through Episerver Find. An API for excluding data that matches patterns will be developed, to prevent PII data from being stored in statistics.
Episerver Find checks the Do Not Track (DNT) header on the request to check if statistics should be track for a user. The DNT functionality will be overridable soon, to make it possible for partners to build their own "Do not track" implementation.
By default, the same data that is being stored in CMS/Commerce database. Data stored by Episerver Find should not include any PII data. You can use the convention API to prevent specific properties containing PII data from being stored in Episerver Find. Data is stored in Elastic Search, on virtual machines in the cloud.
Searched and clicked data can be stored in Episerver Find. The data is stored in Elastic Search, on virtual machines. An API for excluding data that matches patterns will be developed, to prevent PII data from being stored in statistics.
Data that has been received from the querying API should be handled in the same way as when using data from the database. You should consider excluding PII data from being shown on the site.
The statistics that have been stored can be fetched by the API. You should consider filtering PII data before showing it on the website.
You should be able to fetch most types of data using the querying API. A request to the Managed Services team for fetching data about a user can be made in cases where you cannot fetch the data yourself.
You should be able to delete most types of data using the querying API. A request to the Managed Services team for deleting data can be made in cases where you cannot delete the data yourself.