Trust Center / Local Data Residency

Local Data Residency

Tabbly can provide local data residency for customers who request that covered account data, call artifacts, and related processing stay within a chosen geographic region such as India or the United States.

Available on request. The commitments and options described on Trust Center pages apply to customers who specifically request them and enter into the corresponding contractual arrangements with Tabbly. Standard product use remains governed by our Terms & Conditions and Privacy Policy unless a signed agreement states otherwise. To request any of these controls, contact [email protected] or your Tabbly account team.

What “local data residency” means at Tabbly

When a customer requests local residency and Tabbly confirms the configuration in writing, we aim to:

Store customer account content and retained call-related data (where retention is enabled) in infrastructure located in the agreed region.
Route primary processing for those workloads through regional services where commercially and technically available.
Document any unavoidable cross-border transfers (for example limited global control-plane functions, DNS, or support tooling) in the customer’s agreement or DPA.

Regions commonly requested

India — frequently requested alongside DPDP programs and India-first voice deployments.
United States — available for customers who require US-based storage and processing for covered datasets.

Additional regions may be discussed for enterprise deals subject to infrastructure availability and lead time.

Boundaries and customer systems

Residency commitments apply to Tabbly-controlled systems covered by the customer’s order. They do not automatically cover third-party destinations the customer connects (CRMs, webhooks, analytics, or personal storage). Customers remain responsible for residency choices in those systems.

How this interacts with Terms

Default platform operation is described in our Terms & Conditions and Privacy Policy. Local residency is an optional, request-based configuration and becomes binding only when included in the customer’s signed order, DPA, or enterprise addendum.

Request residency

Email [email protected] with your preferred region, data types to cover, and go-live timeline. We will confirm feasibility and any plan requirements.

Last updated: October 2026 · Part of the Tabbly Trust Center