Voice AI Data Processing Agreement
Review draft · not effective. Professional review and factual verification pending.
Contents
- Template status and execution
- Parties, roles and applicable law
- Scope, duration and permitted operations
- Documented instructions and lawful demands
- Confidentiality and personnel
- Safeguards and risk assessment
- Security incidents and cooperation
- Subprocessor authorization
- International transfers and remote access
- Assistance and rights requests
- Periodic reporting, oversight and audits
- Retention, return, deletion and backups
- Responsibility, change and survival
- Annex A — Processing Description
- Annex B — Technical and Organizational Security Measures
- Annex C — Subprocessors and Processing Locations
- Annex D — Retention and Deletion Schedule
- Annex E — Incident Reporting and Escalation Contacts
1. Template status and execution
Unsigned B2B review template. This document becomes contractual only if completed, approved and executed or expressly incorporated into a signed agreement by authorized representatives. Complete customer/provider legal names, registration numbers, addresses, signatories, underlying agreement reference and effective date. No agreement is created by visiting or downloading this page.
2. Parties, roles and applicable law
The customer determines the purposes of caller processing. The confirmed Morganext contracting entity (“Provider”) processes within documented instructions and may operate infrastructure and databases. Identify the database controller and holder under the Privacy Protection Law, 5741-1981, as amended including Amendment 13. This template also addresses the Privacy Protection (Data Security) Regulations, 5777-2017, including Regulation 15, and applicable transfer rules. Each party retains its own statutory obligations. Separate independent processing must be documented, not silently absorbed into this DPA.
3. Scope, duration and permitted operations
Annex A must identify services, systems accessible to Provider, data subjects, data fields, purposes, operations and duration. Permit only the collection, speech processing, transcription, storage, retrieval, routing, transmission, export and deletion expressly selected there. Processing continues only for the service term and agreed lawful return/deletion period. New purposes, sensitive data, biometric processing and model training are excluded unless separately assessed and expressly authorized in writing.
4. Documented instructions and lawful demands
Provider shall process only on documented lawful instructions, including approved configuration changes and transfer instructions. It shall promptly notify the customer if an instruction appears unlawful, suspend the affected operation pending resolution where lawful, and keep an instruction record. If law requires different processing, notify the customer before processing unless prohibited, document the legal requirement and limit disclosure to what is required.
5. Confidentiality and personnel
Provider shall authorize access only to personnel requiring it for assigned duties, bind them to confidentiality continuing after access ends, provide appropriate privacy/security instruction and maintain authorization records. Grant, review and revoke access through documented procedures. Customer administrators must likewise manage their own users. Any exceptional support access requires a defined purpose, authorization and appropriate record.
6. Safeguards and risk assessment
Before processing, the parties shall complete the outsourcing risk assessment, determine the applicable database security level and approve Annex B. Provider shall implement and maintain the expressly agreed measures and applicable legal requirements, evidence their operation and notify material changes. Annex B must distinguish verified controls from planned work; a planned control is not a contractual representation of current implementation. The customer shall not authorize access where the risks cannot be adequately addressed. The customer shall incorporate the required outsourcing scope in its database security procedure, with explicit references to this agreement and the Provider’s security procedure.
7. Security incidents and cooperation
Provider shall notify the customer without undue delay on becoming aware of a suspected or confirmed incident affecting customer data, with initial information available then and phased updates. Annex E must set an operational notification deadline compatible with immediate statutory reporting where applicable. Include event timing, affected systems and categories, likely consequences, containment and contact details; preserve evidence and cooperate on remediation. Neither party may delay a legally required report pending the other’s consent or a complete investigation. Regulatory and individual notices follow law and agreed coordination, without limiting independent duties.
8. Subprocessor authorization
Provider shall not engage an additional processor without the customer’s prior written authorization under the selected specific or general authorization mechanism. Annex C must set advance change notice, a reasonable objection period and a resolution or termination process before a disputed new processing flow begins. Provider shall assess the proposed provider and bind it in writing to relevant processing, confidentiality, safeguards, incident, oversight and deletion duties, including Regulation 15 matters where applicable. Provider remains contractually responsible for delegated obligations as agreed and required by law.
9. International transfers and remote access
No foreign storage, processing, remote access or onward transfer may begin outside the documented authorization. Record countries, recipients and a lawful transfer route under the Israeli transfer regulations in Annex C, including required written undertakings and onward-transfer restrictions. Reassess changes before implementation. Do not infer lawful transfers solely from a provider’s brand, cloud region label or GDPR documentation.
10. Assistance and rights requests
Provider shall promptly forward requests concerning customer data and assist lawful access/correction processes, including locating retained audio and transcripts, proportionate identity verification, secure delivery and correction propagation. It shall not independently decide the customer’s response unless legally required or instructed. The parties shall agree response targets allowing statutory deadlines to be met, reasonable assistance terms and cooperation with competent authorities.
11. Periodic reporting, oversight and audits
Provider shall report to the customer at least annually on performance of the agreed processing and security obligations, and report security events as required. The customer shall exercise risk-based oversight of the outsourcing arrangement. Permit proportionate evidence requests, questionnaires and qualified independent audits subject to confidentiality and protection of other customers. Routine notice, frequency, cost allocation and remediation tracking must be agreed; these arrangements must not obstruct urgent incident review, statutory oversight or regulator access. Record findings, owners and remediation deadlines.
12. Retention, return, deletion and backups
Provider shall retain only the categories and periods approved in Annex D. On termination or lawful instruction, return or delete data as selected, revoke access and instruct subprocessors accordingly. Document completion and any exception. Isolate legally retained copies from ordinary use and delete when the basis expires. Define backup expiry, protection, restore restrictions and reapplication of deletions after recovery; no unverified immediate purge commitment applies. Do not retain data merely because the service ended without a deletion request.
13. Responsibility, change and survival
The customer is responsible for lawful purposes, content, instructions and its notices; Provider is responsible for its processing, personnel and delegated duties under this DPA and law. Neither allocation removes mandatory obligations. Liability, dispute resolution and language precedence require counsel-approved provisions in the signed agreement. Confidentiality, return/deletion, incident cooperation and accrued rights survive as necessary. Material changes require written agreement; unresolved material risk must be escalated and affected processing suspended where appropriate.
14. Annex A — Processing Description
Complete before execution: customer and Provider identities; service/order reference; purpose per workflow; authorized systems and access scope; start/end dates; caller, customer-contact and staff categories; data fields; recording/transcription settings; frequency/volume; selected operations; business instructions and escalation rules. Mark sensitive data and minors explicitly as included or excluded with rationale. Owner and approval date: to be agreed.
15. Annex B — Technical and Organizational Security Measures
For each control record requirement, implemented status, evidence reference, owner, review date and remaining work: logical tenant isolation; identity/access lifecycle and roles; privileged access; authentication; confidentiality/training; secure communications and encryption coverage; key management; logging/redaction; monitoring; vulnerability and change management; backups/restoration; incident response; physical/provider controls; continuity. All deployment controls are unverified in this template. Keep detailed evidence in a restricted annex, not this public page.
16. Annex C — Subprocessors and Processing Locations
Create one approved entry per provider: legal name; service; purpose; data categories; storage, inference and support countries; onward recipients; transfer basis and undertaking; DPA/service-document references and version; retention/training settings; security assessment; customer authorization date. Also complete change-notice and objection periods. No provider or region is confirmed by this template.
17. Annex D — Retention and Deletion Schedule
Create separate rows for audio, transcripts, caller details, orders, account records, operational/security logs and backups. For each: purpose; retention trigger and maximum period; system/provider; export window and format; deletion method and deadline; backup expiry and restoration procedure; legal hold basis and review; evidence and responsible owner. Periods and technical support must be confirmed before signature; blank fields authorize no indefinite retention.
18. Annex E — Incident Reporting and Escalation Contacts
Complete customer and Provider primary/backup contacts; monitored reporting channels and hours; out-of-hours escalation; initial notification deadline; update cadence; evidence-transfer method; regulator-reporting owner; individual-notice owner; decision log and closure criteria. Test the contact path before launch. The public company email is not represented as a 24/7 incident channel. Execute with authorized signatures, names, roles and dates after all annexes and bilingual interpretation have been approved.