Deletion

What deletion removes, and what it cannot.

Deleting is always available. This page will state exactly what goes, what stays, and when the last backup copy expires. It will never claim erasure while a backup still holds a copy.

Structure only. Policy wording pending approval.

This page shows what the deletion statement will cover and the requirements it must meet. It is not the policy itself. The current privacy notice, terms and data processing agreement on the app remain the documents that apply.

What is true today

Unconfirmed preview: Rows deleted automatically after 48 hours.
Account deletion: Removes your workspace database and account records. Some operational records without your list, such as usage and cleanup records, remain as the privacy notice describes.
Backups: Not reached by deletion. Rolling copies expire within 30 days under the current configuration.
Receipt: Not yet issued. The response confirms deletion and lists warnings only.

The receipt you will get

One line per storage class. Synthetic example.

Deletion receiptSynthetic

Reference DEL-7K2Q-SYNTH

Uploaded rows: Deleted 12:41
Counts and reasons: Deleted 12:41
Audit events: Kept 90 days, no identifiers
Backups: Expire by 12 Oct. Not erased earlier.

Requirements before this becomes policy

In place48-hour expiry of unconfirmed rows enforced in code.
In placeBackup retention of no more than 30 days disclosed.
PendingDeletion receipt issued per storage class with a reference id.
PendingDeletion during processing tested: deletion wins, nothing half-written.
PendingRemaining operational records listed precisely in the wording.
PendingWording reviewed by the named privacy reviewer.

Until then: privacy notice, section on retention.