Data Retention
Last updated
Was this helpful?
Last updated
Was this helpful?
For Slack channels, raw message data is stored for 60 days by default.
You can change the retention period (7 to 365 days) in Additional Settings under Settings.
Statistics derived from messages are retained indefinitely while only metadata (e.g., time of arrival, author, linked tickets) is kept.
After the retention period, raw message data is deleted.
Note: ClearFeed does not store attachments.
You can also disable the Data Retention entirely for your account.
If you plan to retain raw data on ClearFeed for more than 365 days, email support@clearfeed.ai.
Can the data be restored if deleted because of the present retention settings? Answer: Data already deleted from our systems because of the present retention setting cannot be restored right now.
If I update the thread of the old ticket/request, will the integration still work on the thread Answer: Yes, the integration will work as we don't delete the Metadata.
Will the old tickets be present in Slack to refer them later? Answer: Yes, we don't delete tickets/messages from Slack.
Is the data retention disabled by default? Answer: By default, Data Retention is disabled for the Internal Helpdesk product edition. For other product editions, it is set to 60 days. You can also extend it from 60 to 365 days.
Can I disable data retention settings completely? Answer: Yes, you can disable the retention settings completely for the account.
Will the older threads sync with Zendesk or will it get deleted as well? Answer: Even after the retention period the older threads continue to sync with Zendesk.
Can I retain data for more than 365 days? Answer: Yes and If you plan to retain data for more than 365 days, you can reach out to us at support@clearfeed.ai.
Will all the data of my old threads be deleted after the retention timeline? Answer: We just delete the title and message texts of the request. However, all operations that work on the request will continue working (for eg - syncing messages between the ticket and Slack).