---
title: "History and deletion: what still needs confirmation"
description: "The project includes local-history and retention design work, but the reviewed sources do not establish a complete public deletion guarantee."
slug: "local-history-deletion"
category: "privacy-data"
language: en
editorial_status: published
capability_status: review
reviewed_at: 2026-10-13
keywords: ["CueSpec local history","delete voice data","retention settings"]
---

# History and deletion: what still needs confirmation

The project includes local-history and retention design work, but the reviewed sources do not establish a complete public deletion guarantee. Removing a local item and deleting already-sent content are different actions.

## 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.

## Related reading

- [Where recorded audio goes](/audio-data-flow/)
- [What can be local and what needs a connection](/offline-scope/)
- [Data-processing facts in the current workflow](/privacy-facts-summary/)
- [CueSpec product facts at a glance](/product-facts/)