EU Data Residency

Last updated: September 14, 2026

Project Paced operates a dedicated European instance at eu.projectpaced.com for organisations that are required to keep project data within the European Union. The EU instance is a separate cloud project with its own database, storage, application backend and identity namespace. No project data is replicated to the Global instance.

Why a separate instance

Data location on our infrastructure is fixed when a cloud project is created and cannot be changed afterwards. Operating a genuinely separate European project is therefore the only way to guarantee residency rather than approximate it. This is a structural separation, not a configuration flag.

Where EU data is stored and processed

A note on terminology, because it matters for due diligence questionnaires. eur3 is a multi-region location, not a single region. It would be inaccurate to describe your database as hosted in Belgium alone, since it is replicated across three EU member states. Our file storage and application backend are single-region and are correctly described as Belgium. AI processing runs on the EU multi-region endpoint, which keeps processing within the EU geography but is not a single-region deployment.

We publish this level of detail so that your security and procurement teams can complete their assessments without a follow-up call.

AI processing

Timeline generation on the EU instance is served by the EU multi-region Vertex AI endpoint. Prompts and generated timelines are processed within EU member state regions. Project descriptions you submit for timeline generation are not used to train foundation models.

Identity and access

Each instance maintains its own user directory. An account on the Global instance does not exist on the EU instance, and the same email address creates a separate account on each. Users, projects and API keys do not cross between instances.

API keys issued on the EU instance carry a distinct prefix so that integrations, including our Model Context Protocol server, route requests to the European backend automatically. When connecting an AI assistant, you are asked to select your instance, Global or EU, before signing in. See the MCP server documentation for connection steps.

Contractual position

• Our Data Processing Agreement is available to all customers and sets out the processor obligations we accept under the UK GDPR and EU GDPR.
• Our sub-processor list names every third party with potential access to customer data, along with their role and location.
• Our security overview covers infrastructure security, application hardening, authentication and monitoring across both instances.

Availability and commercial terms

The EU instance is available under enterprise licensing. Enterprise agreements are invoiced directly rather than through self-service checkout, and include a named renewal date and seat allocation.

To discuss an EU deployment, request the Data Processing Agreement, or complete a security questionnaire, contact support@projectpaced.com.

Frequently asked questions

Can data be moved from the Global instance to the EU instance? The instances are independent, so a migration is an export from one and an import into the other. We can assist enterprise customers with this process.

Is the EU instance available on the monthly plan? No. The EU instance is provisioned under enterprise licensing only.

Does the EU instance support the MCP server and public API? Yes. Both are deployed to the European backend and are reached with EU-issued API keys or by selecting the EU instance during sign-in.

Which instance should we choose? If your organisation has a contractual or regulatory requirement to keep personal data in the EU, choose the EU instance. Otherwise the Global instance is appropriate and is the default.