Data residency is the choice, usually written into the contract, that customer data lives in a specific region. EU data in the EU. US data in the US. UAE data in the GCC. Many regulated industries (healthcare, financial services, government) require it; many large enterprises require it regardless of regulation.
Cloud providers offer regional isolation, but a vendor still has to architect their system so that customer data does not cross regions. Telemetry, backups, and model-training feedback loops are common failure points where data quietly crosses borders.
A serious vendor states the regions they support, documents which customer-facing services operate in each region, and proves the isolation with auditor-verified diagrams. A vendor who claims 'we support data residency' without naming the regions is making a marketing claim.
Vorel supports US-East, US-West, EU-Ireland, EU-Frankfurt, UK-London, UAE-Central, India-Mumbai by default, with named cloud regions and contractually-bound boundaries.