Built around business boundaries
Customer records are associated with a workspace. Database row-level security and server membership checks enforce access boundaries. Server requests authorize the active workspace before querying customer data. Agency access is controlled through assigned membership roles.
Protecting connections and files
HTTPS protects data in transit. Integration credentials are encrypted using AES-256-GCM. Private attachments use scoped access and expiring download links. Provider callbacks verify signatures and use idempotency controls to reduce duplicate processing. Hosted data uses provider-managed encryption at rest.
Your team stays in control
Choose which providers to connect, review access roles and disconnect integrations you no longer need. AI suggestions need human review; tools are subject to configured scopes and approval policies. Maintain accurate user access and follow your organization’s consent and retention requirements.
Report a security concern
Email [email protected] with the subject “Security report”. Include affected URLs, reproduction steps and the impact you observed without exposing customer data or secrets. Do not access other customers’ records or disrupt production. We will coordinate investigation through that channel. This page describes technical controls; it is not a claim of SOC 2, ISO 27001, HIPAA certification or an uptime SLA.