Voice AI Privacy Policy
Review draft · not effective. Professional review and factual verification pending.
Contents
- Introduction and scope
- Provider identity and contact
- Definitions and roles
- Website visitors and business contacts
- Caller data and business responsibilities
- Categories of information
- Purposes and limits
- Notices and lawful processing
- Audio and transcription
- Hosting and technical custody
- Service providers and disclosures
- International processing
- Access, confidentiality and security
- Retention, backups and deletion
- Access and correction requests
- Questions and complaints
- Children and sensitive information
- Changes and effective date
1. Introduction and scope
This draft describes Voice AI business voice services and two distinct processing contexts: Morganext’s own business and website relationships, and caller information processed for a business customer. It is not an approved operational notice. The business must provide its own notice reflecting the deployed service.
2. Provider identity and contact
Morganext is the service brand. The legal entity providing Voice AI, its registration number, address and privacy representative must be identified in the signed service agreement and inserted in the final notice. Corporate pages refer to Morganext LLC (Georgia); that does not establish the contracting entity for this service. General inquiries: info@morganext.com. This is an existing company contact, not a verified dedicated privacy or incident channel.
3. Definitions and roles
“Business customer” means the organization configuring the service for its callers. “Personal data” means information relating to an identified or reasonably identifiable individual. “Processing” includes collection, recording, storage, access, use, transfer and deletion. The business generally determines the purposes of processing caller data; Morganext’s technical custody does not transfer that control. Statutory roles, including database controller and holder under Israeli law, depend on the actual arrangements.
4. Website visitors and business contacts
For its own inquiries, account relationships, administration and legal obligations, Morganext determines the purposes of processing contact details, correspondence and relevant business records. Website processing is addressed separately in the corporate Privacy Policy. This static Voice AI area adds no analytics events, cookies or browser storage; hosting access logs and email-provider processing are not established by the page source. Existing corporate pages load external Google Fonts.
5. Caller data and business responsibilities
The business chooses the service purposes, business content, workflow rules and lawful instructions. It must assess necessity, provide required notices, establish any required consent or other legal permission, maintain accurate content and provide a rights-contact channel. Morganext processes caller information to deliver the instructed service, subject to applicable law and contract. These allocations do not remove either party’s independent statutory duties.
6. Categories of information
Depending on configuration, processing may include telephone numbers, names and contact details, call audio, transcripts, language, call times and duration, routing and technical identifiers, order or reservation details, delivery addresses, support requests and related metadata. Account users’ identifiers, permissions and activity records may also be processed. Only necessary categories should be enabled; recording, transcript storage and analytics are not assumed to be active for every customer.
7. Purposes and limits
Configured purposes may include understanding requests, answering questions, fulfilling orders, arranging reservations, routing calls and supporting authorized operational review. Security, troubleshooting and service administration must be defined and proportionate. This draft does not authorize independent advertising, sale of caller data, voice identification, or model training on caller content. Provider training and secondary-use terms must be checked before selection; no “never used for training” promise is made.
8. Notices and lawful processing
The applicable permission or processing ground must be assessed for each purpose and jurisdiction. Israeli notice requirements include whether provision is legally required or voluntary, consequences of refusal, purposes, recipients and their purposes, controller identity and contact, and access/correction rights as applicable. Continued participation in a call must not be treated as universal consent. Recording, employee monitoring and sector-specific requirements need separate review.
9. Audio and transcription
Speech may need to be processed to operate a voice conversation even if no recording is retained. Audio recording, transcript retention and associated quality review depend on customer configuration, provider behavior and legal requirements. The business must explain which applies before the relevant processing. An AI disclosure alone is not a recording consent or a complete privacy notice.
10. Hosting and technical custody
Morganext may host or operate application infrastructure and administer infrastructure on which databases reside. Information may therefore be stored or accessed in systems operated by Morganext or contracted providers. Customer control of purposes does not mean that data stays on customer-owned infrastructure. Actual systems, access boundaries and locations must be documented for each deployment.
11. Service providers and disclosures
AI inference, speech recognition/synthesis, telephony, hosting, notifications and monitoring providers may receive necessary information. Actual provider identities, purposes, data categories and contract references require verification in the Subprocessors draft and deployment annex. Disclosures required by law must be assessed, limited where lawful, and documented; customer notice should be provided where permitted.
12. International processing
Processing, storage or remote support may occur outside Israel. Before a transfer, the parties must identify destinations, onward recipients and a permissible transfer basis under applicable Israeli transfer regulations, including required recipient undertakings. Foreign provider terms or a European transfer clause alone do not establish Israeli compliance. Locations and mechanisms remain deployment-specific and unverified here.
13. Access, confidentiality and security
Access should be limited to authorized personnel and providers for the assigned purpose, under confidentiality obligations and reviewed permissions. Tenant isolation, role-based access, secure communications, encryption, monitoring and backup protections must be verified in the deployment’s security annex. No certification, encryption coverage, or absolute protection is represented by this draft. See Security & Data Retention.
14. Retention, backups and deletion
The business and service provider must agree retention by data category and purpose, including audio, transcripts, orders, logs and backups. No universal period is verified. Configuration is available only where supported. Deletion may be subject to legal retention, disputes or restricted backup cycles, which must be explained with final removal dates and restore controls. Contract termination does not prove immediate deletion from every copy or provider.
15. Access and correction requests
Individuals may have rights to inspect personal data and request correction or deletion of information that is inaccurate, incomplete, unclear or out of date, subject to applicable law and exceptions. This can include retained audio and transcripts. There is no blanket promise of erasure on demand. Callers should contact the business they called; Morganext should assist that business under the applicable arrangement and route requests it receives appropriately. Identity checks must be proportionate.
16. Questions and complaints
For Morganext’s own processing, or help identifying the responsible business, write to info@morganext.com with a brief description. Do not send full recordings, identity documents or sensitive details in an initial email. A secure follow-up channel and responsible contact must be confirmed. Individuals may also approach the competent privacy authority or seek remedies available under law.
17. Children and sensitive information
The service is offered to businesses; that does not establish that callers are adults. Customers must assess children’s data, sensitive content and sector obligations. Avoid collecting payment credentials, identity documents, health details or voice biometrics unless expressly scoped, lawfully authorized and supported by verified safeguards. Unexpected sensitive disclosures require a minimization and escalation procedure.
18. Changes and effective date
Draft prepared 12 November 2026; effective date not set. Material processing changes require reassessment and appropriate notice before they apply. Final publication requires confirmed entity details, data flows, providers, retention and legal approval. This notice must not be treated as finalized legal advice or proof of compliance.