Voice AI Security & Data Retention
Review draft · not effective. Professional review and factual verification pending.
Contents
1. What is verified and what is not
This is a public review draft, not a security certification. The website implementation is static and adds no call collection, lead database, analytics events or browser persistence. Voice AI runtime controls, hosting locations, providers and operating procedures were not verified in this website review. The requirements below are deployment review items and proposed contractual safeguards, not claims of completed controls.
2. Customer isolation and permissions
Before launch, document and test logical isolation of customer records, catalogs, call histories and administrative actions. Define role-based access where implemented, least-privilege permissions, account lifecycle, privileged support access and periodic authorization review. Availability of these controls must be evidenced in the DPA security annex.
3. Encryption and secure communications
Transport protection, storage encryption and key handling must be checked across telephony, application, database, backup and third-party paths. A website HTTPS URL alone does not establish encryption of calls or stored data. This notice asserts neither end-to-end encryption nor a verified encryption standard. Publish only coverage supported by current deployment evidence.
4. Logging and operational monitoring
Agree the events needed for security and troubleshooting, access restrictions and retention. Avoid unnecessary phone numbers, transcript text, credentials and sensitive payloads in logs or analytics. Validate redaction and alert handling before enabling monitoring. No claim about production log contents or an active monitoring service is made here.
5. Backups and recovery
Confirm whether backups exist, which data they contain, their locations, access controls, protection, schedule, expiry and restore tests. Specify recovery expectations contractually. Backups must have a defined lifecycle and procedures to prevent restored copies from reintroducing deleted data into ordinary use. No backup frequency, recovery target or continuous availability is verified by this draft.
6. Retention and customer configuration
Agree separate retention rules for audio, transcripts, caller details, orders, account records, logs and backups, based on necessity and legal duties. Customer-configurable retention applies only where supported and tested. Document defaults, maximum periods, deletion triggers, provider copies and exceptions in DPA Annex D. Do not assume that disabling recording also disables every transcript or provider log.
7. Deletion and contract termination
The customer should submit authorized requests through the agreed channel. Verify identity and authority proportionately, determine lawful retention requirements, then track deletion across active systems and providers. At contract end, agree export, access revocation, deletion confirmation and backup expiry. Explain any retained copies, restricted use and final deletion dates; do not promise immediate removal from all copies.
8. Incident response and supplier review
Confirm incident contacts, reporting triggers, evidence preservation, containment and recovery procedures before launch. Contractual reporting must support applicable statutory obligations; it cannot replace them. Assess subprocessors’ relevant controls and terms before access, and periodically review them. General questions may be sent to info@morganext.com; a monitored emergency channel must be separately agreed.
9. Review and publication
The deployment owner must approve evidence for every actual control before finalizing this notice. Detailed security configurations, internal addresses and vulnerabilities belong in restricted reviews. Draft prepared 12 November 2026; no effective date, certification or comprehensive compliance claim.