Trust is earned on the details, so here are ours.
EAZETX handles real conversations with real customers. That means being clear about what is stored, how it is protected, and where the line sits between what the engine handles and what a person must.
Call data and recordings
Call recordings, transcripts and the details captured during a call are stored to run the service and honour your retention settings - nothing more.
- Retention periods you configure, not open-ended storage
- Access scoped to the people who need it
- Transcripts tied to the call that produced them
- Data you can request the removal of
Encryption
Customer data is encrypted in transit and at rest, so recordings and transcripts are protected on the wire and in storage.
- Encryption in transit for calls and data
- Encryption at rest for stored recordings and transcripts
- Protected handoff of context during escalation
- No customer data sent to third parties without cause
Escalation-rule guarantees
Escalation triggers are explicit and configurable. Sensitive requests are never silently auto-handled when your rules say a person should take them.
- Clearly defined, visible escalation triggers
- No silent auto-handling of sensitive calls
- Per-call-type rules you control
- Predictable boundary between agent and human
Stated honestly, current status only.
We will not dress up our security posture with badges we have not earned. This page reflects where things stand today, and we will update it as our practices mature.
If your organisation has a specific security or data-handling requirement, reach out through the contact page and we will tell you plainly what we can and cannot commit to.
- No overclaiming of certifications we do not hold
- Data handling described in plain terms
- Retention and access on your terms
- Direct answers to security questions on request