How Cllr protects the personal data your workflows handle, and how every workflow is shaped around your requirements, then refined as they change.
Protection built into the platform
These controls are built into the platform and run in production today, across every workflow.
Built in
Every workflow runs inside these controls, in production today.Payments DB
Customer DB
Usage DB
Rotated, and scoped per environment
- TLS only
- Role-based access
- Audit trail
30 days
Default retention, then deleted on a rolling cycle you can change.Masked, not stored
Switch on PII masking and sensitive data is never written down.Deployed in your region
Cllr is deployed in whichever cloud region your organisation needs, anywhere in the world.HTTPS
On every endpoint, with personal data encrypted at rest as well.Two-factor for every seat
Available on every seat, behind roles that separate managers from admins.How data moves through Cllr
Retention applies across our stores, and backups expire on their own defined schedule. Audit logs keep their own, separately configured retention.
01
Collected
From you, on your instructions02
In transit
Over HTTPS, encrypted03
Processed
Masked data is not persisted04
Stored
Encrypted, in your region05
Retained
30-day rolling default06
Deleted
On the cycle or on request
Where your data is processed
Each deployment runs in the cloud region you choose, and every core processing service runs there with it, including the language models that handle conversation content.
Object storage
- Recordings and files
Managed database
- Contacts, campaigns and transcripts
Language-model processing
- Message and conversation content
Speech-to-text
- Call audio
Speech synthesis
- The agent's voice
The region is set per deployment. The register naming each provider in yours is available to your privacy or vendor-risk team.
Controls in production
Who can reach the data, how the platform is exposed, what is recorded, and how deletion reaches every copy.
Access
- Role-based access with separate manager and admin levels
- A managed identity and authentication layer
- Two-factor authentication, available for every seat
Network and APIs
- HTTPS endpoints for every API and application
- Containerised services in a private cloud network, not exposed to the public internet
- Rate limiting on our APIs
- One-time-use API credentials where applicable
Accountability
- Audit logs of user and operational activity
- Audit-log retention configurable to your requirements
- Telemetry and observability across the platform
Deletion
- Your data deleted on request from our primary systems
- Backups protected, and expired on a defined schedule
- Deletion windows for each store set out in your DPA
Shaped around your requirements
No two organisations hold data the same way. Each workflow starts from secure defaults, is set to your policy, and keeps being tuned as your needs grow.
Region
By default
Any cloud region, worldwideTailored to you
Placed wherever your policies and regulators expectPII masking
By default
Available on every workflowTailored to you
Switched on for the data you never want storedData retention
By default
A rolling 30-day cycleTailored to you
Set to your own retention policyAudit logs
By default
Every action recordedTailored to you
Kept for as long as your auditors needAccess
By default
Manager and admin rolesTailored to you
Two-factor and roles set seat by seat
Questions about security and data
Where data lives, who is responsible for it, and how long it is kept.
Still have a question?
Talk to the team and we will answer it directly.
Start with the workflow that costs you most
Bring one process with a clear owner and a measurable baseline. We map it, test it against representative cases, and hold it to the KPI you set.