<aside>
IT vendor Q&A documentation, including network diagrams.
</aside>
Provide a detailed network and data flow diagram, including all sub-processors, regions, and ports. Any third party egress paths?
Cluely’s network and data flow is structured as follows (see also our Architecture and Data Processing Policy for further internal documentation):
Describe encryption in transit, protocols, cipher suites, and key rotation cadence. Any TLS termination points outside your VPC?
- Encryption in Transit:
- All client-to-server and server-to-server traffic uses TLS 1.2+ (TLS 1.3 preferred).
- Cipher suites: AWS ALB defaults (TLS_AES_256_GCM_SHA384, ECDHE-RSA-AES256-GCM-SHA384, etc.; see AWS reference), Cloudflare defaults (AEAD-AES128-GCM-SHA256, TLS_AES_128_GCM_SHA256 AEAD-AES256-GCM-SHA384, TLS_AES_256_GCM_SHA384 AEAD-CHACHA20-POLY1305-SHA256, TLS_CHACHA20_POLY1305_SHA256; see Cloudflare reference).
- Data sent to LLMs (OpenAI, Google) always over HTTPS/TLS 1.2+.
- Key rotation: Managed certificates renewed at least every 90 days (auto-rotation via AWS ACM or Let’s Encrypt).
- TLS Termination:
- Only at AWS ALB in the primary Cluely VPC. No termination at a global POP/CDN edge. All intra-service comms remain encrypted.
Describe encryption at rest, algorithms, KMS used, key ownership options, rotation policy, and backups encryption.
- Encryption at Rest:
- All customer data (RDS/Postgres, S3 buckets, Neon, and backups) encrypted at rest using AES-256.
- Key management: AWS KMS (or Azure Key Vault for EU projects), with default keys owned by Cluely.
- Key rotation: AWS KMS/Key Vault keys rotated at least annually; customer-managed keys available for Enterprise plan on request.
- Backups: All database and file backups encrypted using the same algorithm and KMS keys; backup retention window = 30 days.
- No plaintext production data stored on unencrypted disks.
For RAG, what data sources are indexed, how is tenant isolation enforced, and how is embedding store segregated to prevent cross-tenant bleed?
- Sources: Only customer-uploaded documents (PDFs, docx, txt, etc.) and team content are indexed into per-tenant stores.