Skip to content

Security

Every line here is one your compliance team can check.

Each deployment runs inside its own data boundary, with an escalation path defined before go-live and a record of what the agent said and when. On-prem and regulated-residency paths are scoped per deployment. No third-party attestation has been issued for ChatSheba, and nothing on this page claims one.

How Sheba handles your data

  • PDPL-aware by default

    Every Sheba deployment is built with personal-data-protection requirements in mind from the start, so regulated buyers can deploy without re-architecting for compliance.

  • 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 supports on-prem and regulated-residency paths, scoped per deployment during the engagement rather than switched on from a standing configuration.

  • 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.

  • A record of what was said

    Conversations and agent behaviour are recorded against the customer record, so a regulated buyer can review what was said, by whom, and when, across the deployment’s lifetime.

Security inside ChatSheba

See how these boundaries apply to a ChatSheba deployment — the CRM-level audit trail, the WhatsApp policy handling, and the per-deployment configuration.

ChatSheba security and data boundaries

Talk through compliance with a specialist.

Bring your data-residency and regulatory requirements. We'll walk you through how a Sheba deployment meets them.

Discuss your use case