Security Briefing

Updated Februrary 17, 2026

Security for QliqCHAT is maintained through a hybrid cloud model that leverages Amazon Web Services (AWS) for high-availability signaling while ensuring all Protected Health Information (PHI) remains under the customer's ultimate control.

AWS Cloud Architecture (The Conduit):‍

QliqSOFT utilizes AWS to host its orchestration and temporary data layers. In this environment:

MySQL (AWS RDS):

Serves as the primary message store for active conversations. To facilitate multi-device synchronization, messages and media are stored here for a rolling 7-day period before being purged from the cloud.

Amazon DocumentDB:

Handles high-volume system logging and audit trails. It records technical telemetry and delivery status (e.g., read receipts) while remaining logically separated from the PHI-containing message databases.

Kubernetes (k8s) on EC2:

The platform runs as containerized microservices on Amazon Linux 2023, allowing for scalable, isolated processing of messaging signals and Quincy chatbot logic.

Core Security Pillars:

The system continues to employ the Cloud Pass-Thru™ architecture, enhanced by current AWS security standards:

Double Encryption:

Every message is encrypted at the device level using 2048-bit RSA public/private keys. It is then "double-encrypted" during transit via TLS 1.2+ as it passes through the AWS environment.

Key Isolation:

Private decryption keys are generated and stored exclusively on user devices; they are never sent to or stored in the AWS cloud. Consequently, QliqSOFT cannot decrypt or access message content even while it sits in the temporary MySQL buffer.

No S3 for Messages:

Binary message data and attachments are handled within the structured database layer (MySQL) to ensure a single point of data lifecycle management and programmatic purging after seven days.

Customer-Controlled Archival:

While the AWS cloud serves as a transitory conduit, permanent data ownership resides with the organization:

QliqSTOR:

A dedicated archival server remains behind the organization's firewall (running on Windows).

Local MongoDB:

QliqSTOR pulls a copy of every encrypted message, decrypts it locally using the organization's master key, and stores it in a local MongoDB database for long-term auditing and EMR integration.

‍