Identify the object#
A recording, transcript, conversation draft, vocabulary entry and received task message can live in different places. A control that clears one should not be assumed to clear every copy or downstream attachment.
If deletion matters to your use, verify the exact current controls and their behavior on a non-sensitive test item. Check what disappears from the app and what remains in the original task environment.
Avoid policy invention#
No universal retention period or retroactive remote-erasure promise is established here. Future policy documentation should state local storage, service retention, backup behavior and account-close handling separately.
Until those facts are confirmed, minimize unnecessary sensitive data and use the workflow only within the handling rules you can establish. Do not delete a useful unsent draft merely to fix a microphone or update problem. Troubleshooting and deliberate retention management should remain separate actions.