Security Architecture
Enterprise trust is engineered into every layer of whatiha. How we safeguard multi-tenant conversation logs, patient consultation bookings, and WhatsApp credentials.
PostgreSQL Row-Level Security (RLS)
Every database query executed by our NestJS API runs under strict multi-tenant session contexts. PostgreSQL policies enforce that tenant A can never read, modify, or query records belonging to tenant B, even in the event of an application logic bug.
Zero AI Model Training
Your patient and customer WhatsApp interactions are routed strictly through commercial enterprise zero-retention API agreements. Your business conversations and uploaded knowledge documents are never retained or used to train open AI foundation models.
Encryption in Transit & At Rest
All web communication, webhook triggers, and administrative dashboards utilize TLS 1.3 with automated HSTS. Sensitive secrets, including WAHA WhatsApp session keys, Google Calendar OAuth tokens, and Stripe API keys, are encrypted at rest with AES-256.
Isolated Worker Queues & Fault Tolerance
Asynchronous workloads (inbound audio transcription, Kokoro voice note synthesis, follow-up pacing) are managed via Redis-backed BullMQ clusters. Jobs feature deterministic exponential backoff, dead-letter storage, and idempotent execution.
01. WhatsApp Session & Gateway Isolation
Each organization’s WhatsApp connection is assigned a persistent, sandboxed session inside our containerized gateway architecture. Webhook deliveries are validated via HMAC signature headers to eliminate spoofing attacks. If a mobile connection temporarily disconnects, our health monitors trigger non-destructive automated reconnect loops without dropping queued patient inquiries.
02. Role-Based Access Control (RBAC) & Audit Trails
Team members access the dashboard using scoped authorization tokens (Owner, Admin, Operator, Read-Only). All administrative configuration changes, prompt updates, calendar overrides, and phone disconnect requests are logged with immutable timestamps and IP address signatures.
03. Telephony & Voice Security
Inbound and outbound voice calls dispatched by our 25-Second Voice Strike engine use secure SIP/WebRTC trunking. Synthesized voice memos generated by our local Kokoro voice studio are stored in temporary encrypted memory buffers and purged immediately following transmission to the recipient.
04. Vulnerability Disclosure & Bug Bounty
We welcome responsible disclosure from security researchers. If you identify a potential security vulnerability, please report it immediately to our security response team at security@whatiha.ai. We review all submissions within 24 hours.
Require a Security Questionnaire or SOC 2 Report?
Our enterprise engineering team assists corporate IT and compliance departments.