Understand retention and deletion
Wirevox does not currently expose one global retention setting or one self-service action that deletes every record associated with an account or caller.
Current retention behavior
| Data | Current behavior |
|---|---|
| Calls and transcripts | Retained with agent/workspace records; no configurable retention period or individual call deletion in the interface. |
| Voice browser tests | Stored as call and lead/contact records and billed like operational sessions. |
| Chat conversations | Beta interface provides individual conversation deletion; session deletion cascades to its messages, tool events, and credit reservations. |
| Vox threads and messages | Persist in chat history; there is currently no thread-delete control. |
| Vox attachments | Private temporary object and record default to seven-day expiry; sweeper runs every six hours. |
| Knowledge | Extracted chunks and embeddings persist until their chunk, source, base, agent, or workspace relationship is deleted. |
| Custom voice | Provider-side clone and local metadata persist until explicitly deleted; original upload is not retained by Wirevox after creation. |
| Shared test link | Remains usable until revoked, expired, or exhausted; link records and test-call records are not an automatic retention policy. |
| Integration credentials | Persist while connected and are deleted from Vault through the secure disconnect flow. |
A token or session expiry limits future access; it does not necessarily delete the underlying historical row.
Resource deletion
Agent
Deleting an agent unassigns its phone-number record, deletes its tools, calls, and leads, then deletes the agent. Cascading relationships remove versions, attachments, deployments, sessions, and other agent-owned records. Shared knowledge bases, reusable functions, integrations, and the phone-number inventory remain.
Knowledge
Deleting a chunk removes that unit. Deleting a source removes its chunks and purges the source from scoped knowledge functions. Deleting the knowledge base removes its indexed content. Agents that depended on it must be reviewed and republished.
Workspace
Deleting a workspace removes the workspace record and workspace-owned dependent rows through cascading relationships. It is blocked for the user's only creator-owned workspace, and parent agency relationships can restrict deletion.
Workspace deletion does not by itself prove that subscriptions, phone numbers, OAuth grants, backups, provider-side cloned voices, or externally created records were cancelled or erased. Resolve those lifecycles first.
Account-level and legal requests
The current interface does not provide full account deletion or a caller-subject request workflow. Use the contact method in the current Privacy Policy for access or deletion requests. Identify the workspace, caller/contact, relevant time range, and records without sending unnecessary sensitive data.
Safe deletion sequence
- Identify the exact scope and legal preservation requirements.
- Pause delivery and wait for active operations to finish.
- Export or preserve only the records you are authorized to retain.
- Disconnect providers and delete provider-side resources where required.
- Delete the narrowest appropriate Wirevox resource.
- Verify dependent agents, functions, knowledge, numbers, and external systems.
- Record who approved the deletion and what was verified.
Deletion is not a backup workflow. JSON agent export does not include credentials, knowledge files, conversation history, or all related records.