Legal
AI and Service Providers
Provider roles, AI-processing considerations and how to obtain the authorized provider schedule for a business deployment.
Version date: September 6, 2026
1. Provider roles and deployment scope
Vizavi uses service providers for hosting, storage, AI processing, payments and communications. The providers enabled for a particular feature or deployment can differ. A brand listed as a supported integration below is not a representation that every customer’s data is sent to that provider.
For a business deployment, request the applicable provider schedule from privacy@vizavi.ai or legal@vizavi.ai before supplying data subject to vendor or residency restrictions. The schedule must identify the contracting entity, purpose, data categories, processing locations and applicable processing terms. This general directory does not replace that schedule or authorize unspecified subprocessors under a DPA.
A processor acting for Vizavi, an independently controlled payment service, and a destination you connect have different roles. Source platforms retain their own copies under their agreements with you.
2. Supported AI processing
| Provider / capability | Information involved | Conditions to check for the enabled deployment |
|---|---|---|
| OpenAI API - language-model responses and embeddings | Prompts, selected text and context, requested outputs and related request metadata. | Contracting entity, endpoint and region, data-sharing opt-in, operational retention, stored responses, prompt caching and any approved retention controls. |
| AssemblyAI - transcription | Audio or an audio retrieval reference, language/speaker settings, transcript and job metadata. | Applicable agreement, model-improvement opt-out, deletion/retention settings, processing region and any voice/diarization addendum. |
| Soniox - transcription | Audio or a file/retrieval reference, language/speaker settings, transcript and job metadata. | Applicable agreement, permitted uses, region, retention and provider-side deletion for completed and failed jobs. |
3. Training is different from storage
A no-training arrangement does not automatically remove operational logs, abuse monitoring, prompt caches or stored responses. Conversely, deleting a file from Vizavi does not itself prove deletion of copies at a provider. The applicable contract and enabled controls determine these matters.
AssemblyAI’s standard terms include model-improvement and training rights unless an applicable arrangement limits them. A no-training promise must therefore be confirmed for the actual account and processing, not inferred from the use of an API. Contact us before sending data with a contractual prohibition on such use.
Any provider used for Google Workspace data must satisfy the applicable Google Limited Use restrictions. This directory does not authorize model training, advertising use or another secondary use prohibited by the source terms, a DPA or applicable law.
4. Other provider categories
| Role | Purpose and data |
|---|---|
| Hosting, databases, storage and recovery | Operate the application and store authorized content, account records and recovery copies. Infrastructure product names do not identify the legal hosting entity or actual processing location. |
| Payment providers, including Stripe where selected | Process subscriptions and refunds, payment credentials, payer details and transaction references. The chosen payment method and checkout identify the applicable provider. |
| Email delivery, support and operational services | Deliver requested account/service messages, manage support and operate technical monitoring with the data necessary for that purpose. |
| User-connected systems | Retrieve permitted content from, or transmit an approved action to, calendar, CRM, messaging, document, task and meeting platforms within configured scopes. These services also operate under their own agreements with the customer. |
5. Provider changes and objections
For processing covered by a DPA, new or replacement subprocessors are subject to the authorization, notice and objection process in that agreement. A general update to this page does not silently expand an existing deployment’s authorization or remove a required transfer safeguard.
Contact legal@vizavi.ai to obtain the current schedule, discuss a specific provider objection or agree residency and processing restrictions. If a required restriction cannot be supported, the affected processing must not be enabled under that restriction.
Vizavi AI Inc.
Delaware corporation
131 Continental Dr., Suite 305, Newark, Delaware 19713, United States