Notes
Consent records that outlive the account that made them
A log the subject of the log can erase is not a log.
Published 2026-08-14 · Last checked 2026-08-14
In short
Naadly lets an owner delete a workspace in one click: accounts, projects, lines, jobs, cloned voices, usage and the audio in storage all go, in the same request. Two things survive on purpose - cloning consent records, because they protect the person who was cloned rather than the person deleting the account, and administrator audit entries, because an erasable audit log is not one.
What deletion actually does
- Storage objects first, then the database rows that reference them - so nothing is orphaned in a bucket.
- Every teammate's seat, every API key, every webhook, every usage counter.
- The session cookie, immediately.
- And it requires typing the word
delete, because a stray click should not end a workspace.
The two exceptions, argued
A consent record is the evidence that a voice was cloned with permission. The person it protects is not the person pressing delete, so letting the account erase it would defeat its only purpose - and it keeps a hash of the reference clip rather than the clip itself. An admin audit entry records what we did to an account; if the account could erase it, it would record nothing.
Anyone can write and ask what is held, and we will say what we can remove and what we cannot.