Data Residency

Blue's infrastructure runs entirely on EU servers. Your data stays within the European Union.

All of Blue’s production infrastructure is hosted within the European Union. Customer data — records, attachments, comments, automations, backups, and analytics — is stored and processed entirely on EU servers.

What this covers

  • Application servers — every request to Blue (web, mobile, API) is served from EU regions.
  • Databases — primary and replica MySQL instances are EU-hosted, with point-in-time backups stored alongside them.
  • File attachments — files uploaded to records, comments, forms, or documents live in EU object storage (primary in Backblaze EU; replicated to AWS S3 EU for redundancy).
  • Backups and disaster recovery — all backup copies remain within the EU.
  • Analytics and operational telemetry — Blue’s internal logging and analytics pipelines run on the same EU infrastructure.

Why it matters

  • GDPR alignment — keeping personal data within the EU simplifies compliance with EU data residency expectations and reduces the need for transfer mechanisms like Standard Contractual Clauses.
  • Latency — for EU-based teams, requests stay regional. Teams elsewhere still benefit from Blue’s edge caching and CDN.
  • No cross-border transfers — your data isn’t replicated or processed outside the EU as part of normal operation.

Sub-processors

Blue uses a small number of sub-processors. Each has been selected with EU data residency in mind — for the most current sub-processor list and the regions they operate in, see Blue’s privacy policy.

Questions

If you have specific compliance questions — data processing agreements, regional commitments, or audit needs — reach out to support and we’ll route you to the right contact.