Data residency is not a single static region for every customer. Production workloads run on infrastructure regions selected for your deployment, while optional integrations (identity providers, AI features, payment processors, or trust services) may introduce processing in additional jurisdictions when you enable them.
Primary processing
Core VaseSign application and storage are hosted with logically isolated tenancy on contracted cloud infrastructure. The authoritative region list for your organisation — including failover behaviour — is supplied in the enterprise data processing schedule or deployment workbook shared after commercial alignment.
Customer content vs operational metadata
Signed documents and envelope payloads typically reside in customer-scoped storage tied to your tenant. Operational telemetry, audit logs, and support artefacts may replicate to tooling regions required for reliability or incident response — categories are enumerated under diligence.
Cross-border considerations
When subprocessors process personal information outside South Africa, your organisation remains responsible for lawful transfer mechanisms under POPIA Chapter 9 and related guidance. VaseSign assists by documenting recipient categories in the Subprocessors register and supplying contractual clauses during onboarding.
If a procurement questionnaire asks for a definitive region without context, answer "deployment-specific — schedule attached under NDA" rather than inferring from this overview alone.