Skip to main content

Security and data handling

Transport​

Use HTTPS when calling the API.

API keys​

  • Treat API keys like passwords
  • Never embed them in public client-side code
  • Prefer sending them via X-API-Key header (not query params)

Data handling​

  • Requests are not stored in a database by default
  • Translation results may be cached in Redis for a limited time (see Caching)
  • Server logs may contain error details

EU data residency​

The dedicated EU data residency endpoint (eu.langbly.com) routes translation processing through Google Cloud regions in EU member states. europe-west4 in the Netherlands is the configured default, not the only EU region. The temporary Redis cache is in Frankfurt and eligible translated responses expire after one hour.

See EU Data Residency for full details.

Compliance​

If you have specific compliance or retention requirements, contact support@langbly.com.

Frequently asked questions​

What data does Langbly store permanently?​

Only account-specific data you actively use for features such as glossaries, custom instructions, or translation memory is stored permanently. We keep that data because those features require it to be available for future requests. The raw source text and translation results from individual API requests are never saved to a permanent database.

How does the EU data residency endpoint differ from the global one?​

The API itself is identical: same request format, same response format. The only difference is where processing happens. The eu.langbly.com endpoint routes all requests to Google Cloud regions inside EU member states (default europe-west4 in the Netherlands). Temporary Redis caching for that endpoint runs in Frankfurt and expires after one hour. The global endpoint uses non-EU regions by default.

Are my API requests logged?​

Server logs may contain error details (e.g., stack traces, timestamps) for operational debugging. However, the actual source text and translation results from your requests are not stored in any permanent database. The temporary Redis cache (see Caching) is not a permanent log. It expires after 1 hour, or after 24 hours if you use an idempotency key.

How long is cached data retained?​

By default, cached translation results in Redis expire after 1 hour. If you send an Idempotency-Key header, the cache is extended to 24 hours. In both cases the data is automatically removed and is never written to a permanent store.

Who can I contact about compliance or data processing questions?​

Email support@langbly.com for compliance-related inquiries.