Conversation - Conversation Deletion

[jasonmorais]

Background

Per the ShareThrift SRD and BRD, all conversations (message threads) tied to reservation requests or listings must be deleted 6 months after the related listing or reservation request has reached a completed, expired, or cancelled state. This is required to enforce the operational database retention strategy and ensure messaging records do not persist beyond the defined retention window.

Task Description

• Implement logic to automatically delete conversations (message threads) from the operational database (Azure Cosmos DB, MongoDB API) after the 6-month archival window has passed following listing expiration or reservation closure.
• Ensure deletion is triggered by a scheduled process or event-driven handler to prevent retention policy violations.
• Log all deletion events for observability and auditing (integrate with OpenTelemetry and Azure Monitor).
• Confirm that orphaned notifications or message-related artifacts are also cleaned as required.
• Update system documentation to clearly define messaging lifecycle and retention rules.

Acceptance Criteria

• Conversations are deleted 6 months after their associated listing or reservation request is archived.
• Deletion is observable in logs and metrics.
• No residual data remains in the database for deleted conversations/messages.
• Documentation is updated to reflect the deletion and retention process.

References

• BRD/SRD: Data Retention Strategy for messages and conversations
• ADR: OpenTelemetry, Observability
• Azure Cosmos DB (MongoDB API) deletion requirements
• documents/share-thrift-srd-bronze.md
• documents/share-thrift-brd.md