Comment on page
Some of our customers may need to review their cloud data retention policy to adhere to company policies or certification standards. To accommodate that need, our platform offers custom data retention settings in every bot.
This article will explain the ins and outs of the data retention settings, and what happens with your data once this feature is enabled.
In Settings > Bot Settings, you can now find the 'Data retention' settings:
Toggle 'Customise retention' to make use of the Data retention feature. Once enabled, you can specify what the specific retention period (in days) should be for each section in the platform:
Conversations are the conversations users have had with the bot. These conversations can be found in the History > Conversations menu.
Per default, sessions expire after 30 days. That means that session information and variables are kept for 30 days. This can be changed with the customised data retention so that the session expires after a configurable amount of days after the last session activity.
It is also possible to delete the session at any point in the conversation, for example after a couple of hours and you want the user to re-identify themselves in the bot. This can be done using this API endpoint.
Please note that changing the session settings will account for new conversations. Let's say you change your session retention today to 15 days. This will count for the new conversations, but the session created before today will still have the 30 day retention period.
If an API integration is used, and this throws an error, this error will end up in History > Error logs. With the customised data retention settings you can choose when these logs are deleted.
Note that changing the data retention settings take about a day to be visible in the platform.
The draft and live version of a bot can have different data retention settings. This means that it is possible to retain testing data in your draft bot longer than actual user data in your live bot.
Simply change to your live environment (by going to Publish > Open live mode) and change the settings while in the live mode of the bot.
For some use cases, you might want to treat specific variables as sensitive. To achieve this, you can use the 'Sensitive variables' feature. This functionality allows you to ensure variables are not saved in the conversation history.
It is also important to note that sessions are archived automatically after 30 days. The other components; conversations, error history and training expressions, are archived after a year (365 days) if custom data retention is not enabled.