Data residency is the legal and operational requirement that certain categories of data be stored and processed within a defined geographic boundary. For organizations subject to GDPR, PIPEDA, Quebec Law 25, Australia's Privacy Act, or other regional frameworks, residency is not a preference — it is a compliance obligation. FormKiQ is designed to support it.
How FormKiQ handles residency
FormKiQ deploys into individual AWS regions. Documents, metadata, search indexes, and audit logs all live within the region where you deploy. Because each FormKiQ instance is scoped to a single region by default, you get hard boundary guarantees — data does not replicate across regions unless you explicitly build that architecture.
For multi-jurisdictional organizations, a common pattern is separate FormKiQ instances per region with cross-region authentication standards and no default cross-region data movement. This allows a unified identity plane while maintaining strict data locality.
Supported AWS regions (representative)
| Region | AWS Code | Key regulatory context |
|---|---|---|
| US East (N. Virginia) | us-east-1 | HIPAA, FedRAMP-adjacent workloads |
| US West (N. California) | us-west-1 | CCPA/CPRA in-state hosting option |
| Canada (Montreal) | ca-central-1 | PIPEDA, Quebec Law 25 |
| Canada West (Calgary) | ca-west-1 | PIPEDA, Alberta PIPA |
| EU (Ireland) | eu-west-1 | GDPR |
| EU (Frankfurt) | eu-central-1 | GDPR, German BDSG |
| EU (Paris) | eu-west-3 | GDPR, CNIL context |
| EU (London) | eu-west-2 | UK GDPR post-Brexit |
| Middle East (Bahrain) | me-south-1 | GCC localization context |
| AP (Sydney) | ap-southeast-2 | Australian Privacy Act context |
| AP (Singapore) | ap-southeast-1 | PDPA Singapore |
| AP (Tokyo) | ap-northeast-1 | APPI |
FormKiQ can be deployed in AWS regions where required services are available. Contact FormKiQ to validate availability for your target region.
Who this matters for
Organizations with formal residency obligations: financial services, healthcare, public sector, and SaaS teams serving regulated customers.
When to use it
When procurement, legal, or architecture decisions must align to jurisdiction-specific data-location requirements before vendor approval.