Voice AI Subprocessors
Review draft · not effective. Professional review and factual verification pending.
Contents
1. Status of the provider register
No Voice AI subprocessor identity or processing location has been verified for this publication. This is not a statement that the service has no subprocessors. Do not infer any supplier relationship from examples, industry norms, the corporate website’s font provider or other products. Obtain a deployment-specific approved register before transferring caller information.
2. AI and speech providers
Depending on configuration, AI inference providers may process prompts, relevant business context and conversation text; speech recognition providers may process audio and produce text; speech synthesis providers may process response text and generate speech. Confirm exact data fields, transient processing, retained logs, training/secondary-use terms and deletion behavior for each service. These categories are possible uses, not a confirmed vendor list.
3. Telephony, hosting and communications
Telephony providers may handle numbers, call signaling, audio and call metadata. Hosting/cloud providers may store application records, databases, files and backups. SMS or notification providers may receive destination details and necessary message content. Operational monitoring providers, if used, may process diagnostic events. Determine whether each entity is a subprocessor or acts independently for a defined purpose; not every provider has the same legal role.
4. Required information for each confirmed provider
The approved register must identify the legal provider name, service category, processing purpose, personal-data categories, countries of storage/processing/support, relevant transfer mechanism, onward providers, contractual/DPA references and version dates. Record customer authorization, assessment date, retention and training settings. No guessed names, regions or assurances should appear in that register.
5. Authorization, changes and international processing
The signed DPA must specify authorization, notice of additions or replacements, objections and resolution before new processing begins. Review international transfers and recipient undertakings under applicable Israeli rules, including remote support and onward transfers. A provider’s general website or marketing statement is insufficient evidence of the terms of a specific account.
6. Request deployment details
Business customers can request the proposed register through info@morganext.com and complete DPA Annex C before approval. Callers should ask the business they contacted which providers and notice apply. Draft date: 12 November 2026. This notice remains incomplete for operational reliance until the actual provider inventory is verified.