Skip to main content
An account’s region_code is application metadata. Selecting a country or account region does not by itself deploy an isolated regional stack, migrate stored records, or restrict every processor to that region. The current recovery deployment uses Google Cloud. Do not rely on earlier documentation naming AWS regions in Virginia, Dublin, or Cape Town as evidence of available Truthlocks deployments.

​
Before choosing a residency requirement

Obtain confirmation of the actual locations and processors used for your workspace’s database, object storage, backups, logging, email, billing, and AI features. A database location alone does not establish where all related data is processed. Changing a profile’s region preference is not a data migration. If a location restriction is required by your organization, arrange and verify the deployment and processing terms before submitting restricted data. Public proof material, documentation, and content you deliberately publish have a different visibility boundary from private workspace records. Review what you publish and which downstream services receive it. See security architecture, tenant isolation, and consumer profile updates.