Skip to main content
EU data residency ensures that your fsckmsft workspace data — including all projects, documents, tasks, and user information — is stored and processed exclusively within the European Union. This option is available to Business plan customers and is particularly relevant for organisations subject to GDPR or operating under national data localisation requirements.
EU data residency is available on the Business plan only. If you’re on a Free or Pro plan and require EU residency, contact sales to discuss upgrading.

​
Infrastructure details

SettingValue
Cloud providerAWS
Primary regioneu-west-1 (Frankfurt, Germany)
Failover regioneu-central-1 (Frankfurt, Germany — secondary AZ)
Data at rest encryptionAES-256
Data in transit encryptionTLS 1.3
All primary data storage, database instances, compute workloads, and backup snapshots for EU-residency workspaces remain within AWS’s EU infrastructure. No Customer Data is transferred outside the EU/EEA for processing, except as permitted under applicable SCCs for ancillary services (see below).

​
How to enable EU data residency

Data residency is a workspace-level setting that must be selected at account creation or via a formal migration request. You cannot change data residency retroactively without a migration, as this involves physically moving your data to a new region.

​
Option 1: Select EU residency at account creation

1

Start workspace creation

Navigate to app.fsckmsft.org/signup and begin the workspace creation flow.
2

Select 'European Union' as your data region

On the workspace setup screen, find the Data Residency selector and choose European Union (Frankfurt).
3

Complete account setup

Finish entering your workspace name and billing information. Your workspace will be provisioned in eu-west-1 from the first request.

​
Option 2: Request a region migration

If your workspace was created with US or APAC residency and you need to migrate to EU, contact support to initiate a region migration.
1

Email support to request a migration

Email support@fsckmsft.org with the subject line “EU Data Residency Migration Request”. Include your workspace name, current plan, and your required completion date.
2

Receive a migration plan

Our team will provide a migration plan including estimated downtime (typically a 2–4 hour maintenance window outside business hours), a data integrity checklist, and a target completion date.
3

Confirm and schedule

Review and confirm the plan. We’ll schedule the migration during a low-traffic period and notify all workspace admins in advance.
4

Verify after migration

After migration, verify your workspace is operating normally. Your workspace settings page will confirm the active data region.

​
GDPR compliance implications

Enabling EU data residency strengthens your GDPR compliance posture in several ways:
  • Data localisation: Personal data of EU/EEA data subjects remains within the EU/EEA at rest, satisfying strict data localisation requirements under some national implementations of GDPR.
  • Reduced cross-border transfer exposure: You avoid reliance on SCCs or adequacy decisions for primary data storage and processing.
  • DPA alignment: Our Data Processing Agreement is designed for EU residency and explicitly covers processing within AWS eu-west-1.

​
Standard Contractual Clauses (SCCs)

Even with EU data residency, some ancillary services (e.g. Intercom for support, Datadog for monitoring) operate from the United States. For these subprocessors, fsckmsft relies on the EU Standard Contractual Clauses (2021/914) as the transfer mechanism. Full SCC documentation is available upon request at legal@fsckmsft.org.

​
Latency considerations

If the majority of your team is located in Europe, EU data residency typically provides the best API response times and page load performance. Expect:
  • EU-based users: 20–60ms API response times from most European cities
  • US-based users accessing EU workspaces: 80–150ms additional latency compared to a US-resident workspace
  • APAC-based users accessing EU workspaces: 150–250ms additional latency
If you have a globally distributed team, consider whether US residency (geographically central for transatlantic teams) or multiple workspaces with different residency settings better suits your needs.
You can benchmark latency to fsckmsft’s regional endpoints by pinging eu-api.fsckmsft.org from your office network before committing to EU residency.