Data Residency — Intravo

Regional commitment. EU-origin customer data is routed to approved EU processing paths and is not routed to the United States unless the customer has approved a lawful transfer or processing is required by law. Some US-origin data may be processed in approved EU environments.

Service-specific scope

Residency is determined by the contracted product, enabled features, storage location, integrations, support model, and subprocessor coverage. The applicable order or service agreement is authoritative for a customer's configuration. A general reference to an “EU service” does not automatically mean every optional integration is available in-region.

Regional design

Customer and feature configuration identifies the intended processing region.
Storage, compute, observability, backup, and optional provider paths are reviewed before a service is represented as region-bound.
Administrative access is restricted by role and business need; necessary remote access does not itself change the storage region, but may be an international transfer under applicable law.
Changes that may affect residency are reviewed through change and vendor-management processes.

International transfers

Where processing creates a restricted international transfer, Intravo uses an applicable legal mechanism such as an adequacy decision, the European Commission Standard Contractual Clauses, the UK Addendum, or another recognized safeguard. Transfer assessments and supplementary measures are applied when required.

Provider transparency

The Subprocessors page identifies relevant providers and high-level regional posture. Provider networks may be global even when storage or compute is region-configured; contractual terms and technical configuration determine the applicable commitment.

Confirming your configuration

For a product-specific data-flow or residency confirmation, contact privacy@intravo.com and identify the product, features, intended users, and required region.