Category: Informational, API
Summary: Conversation service will be reducing its internal data's time-to-live (TTL) from 90 to 60 days in support of new security and compliance requirements. Extensive research has been done to support that this will not be an impactful change to customers, and read-only data should remain available for the conversation long-term through other means. This work will be completed with ticket CS-2092.
Context: This change is being made to meet new security and compliance requirements. Specifically, it is to support the scrubbing of customer data from our systems when customer contracts are terminated.
Impact: Conversations will still be available to read long-term, but they will be unavailable to alter after 60 days. We do not have any evidence that this will produce any noticeable impacts to end customers.
Date of Change: This change will be going into effect no later than Oct 31st, 2020, but the effects of the change will not be present until 60 days later (Dec 2020).
Impacted APIs: Endpoints under /api/v2/conversations/{media}/{conversationId}/* that attempt to change data or conversation states (new communications, transfers, participant attributes, etc) will be unavailable after 60 days from the last change to the conversation.
References: PURE-2783, CS-1671, CS-2092
