The requirement that customer data be stored and processed within a specific geographic jurisdiction. EU customers under GDPR often require data to stay within the EU; Canadian healthcare systems often require data to stay within Canada; some defense customers require data to stay within the US. Data residency is not the same as data sovereignty (which adds requirements about whose laws apply) but the two are often confused. For meeting copilots, data residency typically requires running infrastructure in the customer's region (EU-hosted clusters for EU customers), keeping transcripts and recordings in regional object storage, and ensuring that the model inference itself happens within the region — which can be challenging when the LLM provider only has US-region endpoints.