Access
Authenticated users, with authorization enforced by the backend rather than the browser.
Security and trust
Clear controls for voice work that needs human review.
CloaFlow separates dashboard access, source systems, agent runtime events, and operational decisions, so customer-service workflows stay understandable and auditable.
Tenant boundary
Calls, requests, settings, notes, and audit records are scoped to one organization.
Source data
Agent and customer systems can stay separate systems of record.
Decision trail
Review decisions, ownership changes, and notes are auditable.
Controls
Current control coverage.
This is the security model the product is built around today. Customer-specific deployments can add stricter retention, access, and review requirements.
- Role-based access
- Users can open only the organizations assigned to them. CloaFlow admins can support customer workspaces with elevated access.
- Tenant isolation
- Organization membership is the boundary for dashboard records and for server-side API access.
- Source separation
- Operational indexes and source references are preferred over copying every sensitive artifact.
- Secret handling
- Database URLs, API keys, webhook secrets, and email credentials live in managed platform secrets.
- Transport security
- Traffic is served over HTTPS/TLS through managed hosting and infrastructure providers.
- Change control
- Production changes are intended to move through version control, checks, and controlled deployment.
Data
Data and source systems.
- Call metadata includes timing, direction, status, organization, agent, phone line, and source references.
- Workflow records include request type, missing fields, owner, review state, approvals, notes, and audit events.
- Source details can be fetched from the connected system when an authorized user opens a case.
- Recordings and transcripts are optional, customer-configured artifacts governed by notice, consent, retention, and access requirements.
Secret handling
API keys, database URLs, webhook secrets, and email credentials are configured through environment variables and platform secret stores.
Encryption
Managed providers handle encrypted transport over HTTPS/TLS. Database and infrastructure encryption come from the selected managed platforms.
Recordings and transcripts
Capture is optional and configured around each customer's consent, access, and retention requirements.
Incident reporting
Found a security issue?
Email hello@cloaflow.com with the affected URLs, reproduction steps, screenshots or logs if available, and a safe way to reach you.