This page also lists what we do not have.
ChatSheba runs inside a per-deployment data boundary, with defined escalation controls and a deployment path scoped for regulated environments. No third-party attestation or certification has been issued for it. What follows is the posture, the controls, and the limits.
- 35+AI personas in production
- 14+industries deployed
- Secondsto a routine reply
- AllArabic dialects
- After hoursroutine questions answered
PDPL-aware planning
ChatSheba is designed with personal-data-protection requirements in mind from the start, so regulated buyers can scope deployment architecture, data handling, and escalation controls early in the project.
Per-deployment data boundaries
Each deployment runs inside its own data boundary. Your customers' data stays scoped to your deployment — it is not pooled across clients.
On-prem and regulated-residency paths
For banks, healthcare, and other regulated sectors, Sheba can scope on-prem or regulated-residency deployment paths where data location and control are key requirements.
Human escalation as a control
Defined escalation triggers route sensitive conversations to a person, with guardrails that keep the agent from improvising on policy, legal, or medical questions.
Every conversation logged against the customer record
Conversations and agent behavior are recorded in the CRM, so a regulated buyer can review what was said, by whom, and when.
What ChatSheba is not certified for
No third-party certification or attestation has been issued for ChatSheba — not ISO 27001, not SOC 2, and not a PDPL certification scheme. The posture on this page is Sheba's own, documented and scoped per deployment rather than audited by an outside party. On-prem and regulated-residency paths are scoped during the engagement, not available as a standing configuration. Where a requirement falls outside what a deployment can carry, that is said during scoping rather than after it.
Try it live
The banking assistant runs the same boundaries this page describes — open it and test them.
Talk through your regulatory requirements with a specialist.
Bring your data-residency and regulatory requirements. We'll walk you through how a ChatSheba deployment can be scoped against them.
Discuss your use case