Security, privacy, and data retention
Wirevox processes account, caller, conversation, knowledge, integration, and billing data to operate AI agents. Security depends on both platform controls and how each customer configures access, prompts, providers, functions, consent, and retention.
This documentation describes behavior verified in the current product and source. It is not a certification, data-processing agreement, legal opinion, or guarantee about a third-party provider.
Do not claim that Wirevox is SOC 2, ISO 27001, HIPAA, PCI DSS, or another regulated-data solution unless a current signed agreement or formal certification explicitly establishes it. The current product does not expose a BAA workflow.
In this topic
- Understand authentication and workspace isolation
- Understand data flows and stored records
- Configure caller disclosure and data minimization
- Protect knowledge, files, and web imports
- Protect integrations, functions, and secrets
- Understand retention and deletion
- Review current security boundaries
- Operate securely and respond to incidents
Shared responsibility
Wirevox supplies authentication, workspace authorization, versioned configuration, approval-backed Vox actions, scoped storage, and integration controls. Workspace owners remain responsible for:
- inviting only authorized people and reviewing roles;
- collecting only necessary caller data;
- configuring legally appropriate AI, transcription, and recording disclosures;
- selecting providers and integration permissions suitable for the data;
- validating prompt and tool safety;
- defining an external retention and deletion policy where the product has no setting; and
- meeting contractual, sector, and jurisdictional obligations.
Use the published Privacy Policy for the service's legal privacy statement. If this documentation conflicts with a signed agreement or current policy, follow the governing document and contact Wirevox.