Security

The Malakai platform is a voice-enabled AI system that processes incoming and outgoing calls, converts speech to text, retrieves relevant context, generates intelligent responses, and synthesizes responses back to audio format. All data flowing through these services originates from the Malakai Backend and is routed through secure channels with encryption and hashing mechanisms at rest and in transit.

The Malakai system processes voice interactions through a sophisticated pipeline involving call ingestion, speech recognition, contextual retrieval, AI-powered response generation, and voice synthesis, with every stage implementing encryption and hashing protocols to ensure data confidentiality and integrity.

The primary data flow in the Malakai system proceeds as follows:

1. Inbound/Outbound Call — Twilio receives the call initiated from the Malakai Backend, establishing voice connection with the caller.
2. Speech-to-Text Conversion — The audio stream is transmitted from Twilio to Deepgram for STT processing.
3. Context Retrieval — Transcribed text is sent to VoyageAI (RAG) to retrieve relevant context from the knowledge base.
4. LLM Response Generation — The combined user query and retrieved context is sent to Claude, OpenAI, or Gemini for intelligent response generation.
5. Text-to-Speech Synthesis — The generated response is sent to ElevenLabs for TTS conversion.
6. Call Response Delivery — The synthesized audio is transmitted back through Twilio to the caller.

All data flowing through the Malakai platform originates from the Malakai Backend, which acts as the centralized data source and control point. This data is then routed through the following channels and services:

1. Inbound call from caller → Twilio receives and forwards to Malakai Backend
2. Malakai Backend retrieves workspace configuration from DynamoDB
3. Audio stream forwarded to Deepgram (STT) with encryption
4. Deepgram returns transcribed text to Malakai Backend
5. Malakai Backend sends query to VoyageAI for context retrieval
6. Combined query and context sent to Claude/OpenAI/Gemini
7. Generated response received and forwarded to ElevenLabs (TTS)
8. Synthesized audio returned to Malakai Backend
9. Audio forwarded to Twilio for delivery to caller

Throughout this entire flow, call records are stored in DynamoDB (encrypted), recordings are stored in S3 (encrypted and/or hashed), and all data is transmitted using TLS encryption. The Malakai Backend maintains encrypted audit logs of all operations.

The Malakai platform adheres to the following standards and regulations:

• GDPR (General Data Protection Regulation): Data handling complies with EU privacy regulations; user consent obtained for processing
• CCPA (California Consumer Privacy Act): California residents have rights to data access, deletion, and opt-out
• HIPAA (Health Insurance Portability and Accountability Act): If handling healthcare data, encryption and audit logging enforced
• SOC 2 Type II: Cloud infrastructure providers (AWS, Anthropic, OpenAI) maintain compliance
• ISO/IEC 27001: Information security management system certification pursued
• PCI DSS (Payment Card Industry Data Security Standard): If processing payment data, compliance enforced

Key generation & storage:

• Master encryption keys generated using cryptographically secure random generators
• Keys stored in AWS Secrets Manager or HashiCorp Vault with access control
• Hardware Security Modules (HSMs) used for high-security environments
• Key rotation policy enforced every 90 days

Key access & rotation:

• Only authorized services granted access via IAM policies
• Key rotation does not require data re-encryption; new keys used for new data
• Old keys retained for decryption of historical data
• Key usage logged and audited for compliance

In the event of a security incident or suspected data breach, the following protocol is activated:

1. Detection: CloudWatch, CloudTrail, and intrusion detection systems monitor for anomalies
2. Isolation: Affected systems are immediately isolated to prevent further compromise
3. Investigation: Forensic analysis performed; audit logs reviewed for scope determination
4. Notification: Users and relevant authorities notified per regulatory requirements (GDPR, CCPA, etc.)
5. Remediation: Security fixes deployed; systems restored from clean backups
6. Post-Incident: Root cause analysis; preventive measures implemented

Important disclosure: The Malakai platform integrates with multiple third-party services to provide voice AI functionality. This section explicitly states what data is visible to each third-party service, what they can and cannot access, and what usage limitations apply.

The Malakai platform implements a comprehensive data security architecture that ensures all data originating from the Malakai Backend is protected throughout its lifecycle. Every integration point uses end-to-end encryption, sensitive data is hashed using industry-standard algorithms, and all systems maintain detailed audit logs for compliance and accountability.

Third-party services have strictly limited visibility into the platform’s data and operations. Each external service operates in isolation, seeing only the specific data necessary for their function. User credentials, system configuration, audit logs, and encrypted data remain completely hidden from third parties.

By leveraging AWS’s managed security services (S3, DynamoDB), implementing TLS 1.2+ for all network transmission, maintaining strict access controls via IAM policies, and enforcing data compartmentalization, the Malakai platform provides a secure, scalable, and compliant solution for voice AI interactions.

All data handling practices comply with global privacy regulations including GDPR, CCPA, and HIPAA, ensuring users’ data rights and privacy are protected at the highest standards.

For questions or security concerns, please contact the Malakai Security Team.