Account Data Residency & Multi-Region Deployments

NoCodeBackend allows you to anchor your account and deploy databases in distinct geographic regions to meet strict data privacy regulations, support European data sovereignty standards like the General Data Protection Regulation (GDPR), and deliver ultra-low latency to your global users.

---

1. Overview: What is Account Data Residency?

Account Data Residency determines the permanent physical location where your account-level data is hosted and stored. This includes:

• Your personal profile and authentication credentials.
• Security keys and API credentials.
• Database access tokens.
• Team member invitations and permissions.
• Custom domain mappings and SSL certificates.
• Saved R2 cloud storage credentials.

Available Geographic Regions

1. EU Central (Frankfurt, Germany):
   • Supports GDPR & European Data Sovereignty: Strictly hosted within the European Union to eliminate unauthorized cross-border transfers under GDPR Chapter V.
   • Ideal for European businesses, enterprise procurement requirements, agencies, and privacy-first SaaS platforms.
2. US West (Phoenix, United States):
   • High-speed, high-availability North American cloud infrastructure.
   • Ideal for applications serving users primarily in the Americas or APAC.

---

2. Residency Locking & Data Sovereignty

To ensure complete compliance with data protection laws and prevent accidental cross-border transfers of sensitive user credentials, Account Data Residency is permanently locked once chosen.

• When you select your residency (via the residency modal on the dashboard), your account is permanently registered to that region.
• You can review your permanent residency at any time via the badge in the dashboard top navigation bar. Hovering over the badge displays a verified confirmation tooltip:

  💡

  "Your personal profile, credentials, and confidential account data are permanently hosted in Frankfurt, Germany. Account residency is locked. You can still deploy individual databases in either region at any time."

---

3. Database Independence: Multi-Region Deployments

Choosing an Account Data Residency does NOT restrict where you can deploy your databases!

NoCodeBackend is designed with complete decoupling between your account identity and your database infrastructure:

• Deploy Anywhere at Any Time: Even if your account residency is locked to Frankfurt (EU), you can create new databases hosted in US West (Phoenix) or EU Central (Frankfurt) at any time with a single click.
• Global Architecture: You can easily run multi-region architectures from a single NoCodeBackend account. For example, you can host your primary European SaaS database in Frankfurt and provision a separate US database in Phoenix for low-latency North American customers.
• Isolated Credentials: Each database generates isolated connection tokens and REST API endpoints hosted in that database's physical deployment region.

---

4. Existing Users & Migration Guidance

If you created your NoCodeBackend account prior to the regional expansion and migrate your residency to Frankfurt (EU):

1. What Moves to Frankfurt:
   • Your account profile, login credentials, workspace metadata, team invites, and confidential authentication tokens are securely migrated to the Frankfurt regional hub.
2. What Stays in US West:
   • Your existing databases remain hosted in US West (Phoenix).
   • Why? To guarantee 100% zero downtime and eliminate connection disruption for your active production applications, APIs, and client traffic. Existing connection strings, endpoints, and MySQL ports continue running uninterrupted.
3. Future Databases:
   • Any new database you create after setting your residency can be deployed in either EU Central (Frankfurt) or US West (Phoenix) depending on your project's needs.

---

5. Security & Infrastructure Compliance

• Encryption in Transit & at Rest: All cross-region communication is protected with TLS 1.3 encryption. Credentials stored in MariaDB are encrypted using AES-256 with isolated per-environment keys.
• GDPR Compliance Support & Zero Cross-Border Transfers: Choosing EU Central ensures your account credentials, auth tokens, team data, and EU-deployed databases are physically stored in Frankfurt, Germany. This provides the European data locality infrastructure required to meet GDPR Article 28 and Chapter V international data transfer obligations.
• Enterprise Isolation: Database instances run in isolated containers with strict firewall barriers and automated backups stored in region.