Security
Plain‑language security and access controls designed for customer support teams.
Role‑based access for admins and support users.
Conversations and tickets are separated by tenant.
Retention is configurable by plan or policy.
Conversation history is logged for support follow‑up.
Only necessary contact fields are stored for follow‑up.
Security settings are adjustable by account needs.
Security settings you can control
During onboarding we align settings to your data policy and support workflow.
- Roles and access for admins vs support agents.
- Tenant isolation so each account’s chats and tickets stay separated.
- Transcript retention windows based on policy or plan.
- Contact fields captured so you only collect what you need.
- Email routing for alerts and follow‑ups.
Handling PII or PHI
If you collect personally identifiable or medical information, security requirements are higher. We’ll review your retention, access, and notification needs before go‑live.
If HIPAA applies, a Business Associate Agreement (BAA) and policy review are required. Ask us about your specific compliance requirements.
Data lifecycle overview
- 1Collection
Capture only essential contact details needed for follow‑up.
- 2Storage
Chats and tickets are stored per tenant with access controls.
- 3Retention
Retention windows are configured to match your policy.
- 4Review
Admins can audit conversation history for support follow‑up.