Your data. Your rules.

Toronto co-location

All primary production servers are hosted in professional co-location facilities in Toronto, Canada. We do not rely on shared public cloud hyperscalers for primary data storage, giving you and your clients predictable physical data residency.

Canadian jurisdiction

Data stored on MyVoiceHub infrastructure is subject to Canadian law and is not subject to cross-border data transfer agreements unless explicitly configured by the partner.

Tenant isolation

Every client tenant operates in its own isolated data partition. Call records, fax logs, SMS history, and AI agent data are strictly scoped to the originating tenant and are not accessible across account boundaries.

Encryption in transit and at rest

All data transmitted between clients and the platform is encrypted via TLS. Stored data, including call records, fax content, and message logs, is encrypted at rest.

Your data belongs to you

Client and tenant data is owned by the client. MyVoiceHub does not claim any rights to communications content, call recordings, fax documents, or SMS messages stored on the platform.

No research or model training

Client data is never used for internal research, product development, AI model training, or any analytical purpose beyond operating the platform on your behalf. What flows through your tenants stays with your tenants.

No data brokering

We do not sell, license, or share client data with third parties for commercial purposes. Data shared with sub-processors is strictly limited to what is required to deliver the contracted service.

Data deletion on request

Partners and tenants can request full deletion of their data upon contract termination. Deletion requests are processed within a defined retention window and confirmed in writing.

Bring your own API keys

For all AI-related products, clients may supply their own API keys for underlying model providers. This means AI inference runs under the client's own account and billing relationship, with no data transiting MyVoiceHub's AI credential scope.

Credential isolation

API keys supplied by a tenant are stored in encrypted form and are never exposed across tenants or accessible to other partners. Each set of credentials is scoped exclusively to the tenant that provided them.

No PBX credential requirement for AI Agents

Voice AI Agents deploy as registered PBX extensions and do not require trunk-level or administrator credentials. Your clients retain full control of their phone system at all times.

Audit logging

API key usage, agent activity, and administrative actions are logged per tenant. Logs are available to the partner for their own compliance review and can be exported on request.

Self-hosting for enterprise clients

Enterprise partners with specific data sovereignty or security policy requirements may elect to self-host the MyVoiceHub platform stack within their own infrastructure. This option allows full control over where data lives, how it is backed up, and which network policies govern access.

Air-gapped deployment

Self-hosted deployments can be configured for air-gapped or private network environments, suitable for clients in regulated industries such as healthcare, legal, or government where external connectivity must be restricted.

Policy conformance

Self-hosting partners are responsible for configuring the deployment to meet their own internal security policies. MyVoiceHub provides technical documentation and onboarding support for self-hosted environments as part of the enterprise agreement.

Dedicated infrastructure option

For partners who do not require full self-hosting but need dedicated infrastructure rather than a shared multi-tenant environment, dedicated server options are available on request.