EU Data Residency

Your data stays in Europe

Dedicated EU infrastructure for organizations that require strict GDPR compliance and data residency. Same API, same quality, same pricing.

Two endpoints, one API

Both endpoints are fully Google Translate v2 compatible, run in the EU, and share the same pricing. Choose the one that fits your compliance requirements.

Global Endpoint

api.langbly.com
Netherlands (europe-west4)

Optimized for lowest latency worldwide. All infrastructure currently runs in the EU, but this is not a contractual guarantee.

  • GDPR-compliant
  • Lowest latency globally
  • Google Translate v2 compatible
  • Best for most use cases
Strict Data Residency

EU-Only Endpoint

eu.langbly.com
Finland (europe-north1)

Guaranteed EU data residency. All translation processing, storage, and caching stays within the European Union.

  • GDPR-compliant
  • All processing in the EU
  • Google Translate v2 compatible
  • Best for regulated industries

Everything stays in the EU

When you use the EU endpoint, every component of the translation pipeline runs within the European Union. No data leaves EU borders at any stage of the process.

Our infrastructure runs on certified platforms that meet ISO 27001 and SOC 2 standards, with all data encrypted in transit using TLS.

API servers
Finland (europe-north1)
Translation processing
EU infrastructure
Database
EU region
Cache
EU region
Encryption in transit
TLS 1.2+
Infrastructure certification
ISO 27001, SOC 2

Built for GDPR compliance

Both endpoints are GDPR-compliant by design. The EU endpoint adds a contractual guarantee that all processing stays within the EU.

No content storage

We don't persist translation content in our database. Results may be cached briefly to speed up repeated requests, then discarded.

Encrypted in transit

All API traffic is encrypted with TLS. Your translation data is never transmitted in plain text between any component.

DPA available

We offer a Data Processing Agreement for enterprise customers. Contact us to set up a DPA for your organization.

Cross-border transfers

US companies translating EU customer data should consider the EU endpoint to simplify cross-border data transfer compliance.

Switch endpoints in one line

Both endpoints share the same Google Translate v2 compatible API. Switching to the EU endpoint is as simple as changing the base URL.

cURL
# Global endpoint
curl "https://api.langbly.com/v2?key=YOUR_KEY&q=Hello&target=de&source=en"
# EU-only endpoint (strict data residency)
curl "https://eu.langbly.com/v2?key=YOUR_KEY&q=Hello&target=de&source=en"
Python
from langbly import LangblyClient
# Use the EU endpoint
client = LangblyClient(
api_key="YOUR_KEY",
base_url="https://eu.langbly.com"
)
result = client.translate(
q="Hello world",
target="de"
)
Node.js
import { LangblyClient } from "langbly";
// Use the EU endpoint
const client = new LangblyClient({
apiKey: "YOUR_KEY",
baseUrl: "https://eu.langbly.com"
})
const result = await client.translate({)
q: "Hello world",
target: "de"
})
Regulated industries
Healthcare, finance, legal, government
US companies with EU users
Simplify cross-border compliance
Enterprise procurement
Meet internal data residency policies
Public sector
National data sovereignty requirements

Who should use the EU endpoint?

The global endpoint is GDPR-compliant and works great for most use cases. The EU endpoint is designed for organizations that need a contractual guarantee that all data processing stays within the EU.

If your security team, legal department, or procurement process requires strict data residency, the EU endpoint is the right choice.

Get started with EU data residency

Same API key works on both endpoints. Switch to the EU endpoint whenever you need strict data residency.