Data Residency — Intravo

Regional commitment. EU-origin customer content and personal data must remain within approved EU processing and storage paths. The default is no EU-to-US transfer. A documented exception must be approved before any proposed transfer and must meet customer commitments, applicable law, and the safeguards below. Some US-origin data may be processed in approved EU environments when contracts and law permit it.

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 identifies the customer's configuration. Customer contracts may impose stricter requirements. Optional integrations must satisfy the same regional requirements before they receive EU-origin data.

Regional design

An authoritative customer, tenant, event, meeting, or workload assignment determines the processing region; region selection must not depend solely on DNS geolocation or a transient client IP address.
EU requirements cover application and AI processing, storage, replicas, backups, recovery, logs, identifiable telemetry, support, and subprocessors. EU-origin data must not fail over to a US region; recovery must remain within an approved EU path.
Administrative and support access require least privilege, MFA, approved managed devices, and audit logging. Access from the United States is treated as an international-transfer risk even when the data remains stored in an EU data center.
Changes that may affect residency are reviewed through change and vendor-management processes.

International transfers

A proposed exception must be approved before processing and document business necessity, data and recipients, locations and retention, customer authorization, an applicable legal transfer mechanism, a transfer-impact assessment, effective supplementary safeguards, and an accountable owner, expiration, review date, and exit plan. If the required protection or contractual residency commitment cannot be met, the transfer does not proceed.

A DPA, Standard Contractual Clauses, adequacy mechanism, certification, or encryption does not override a stricter Intravo or customer residency commitment. Legal obligations remain applicable and are addressed through the appropriate legal and privacy review.

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; each service and component requires contractual and technical confirmation. A provider's general assurance report or agreement does not establish that a specific feature meets this standard.

AI, retention, and testing

EU-origin prompts, transcripts, files, embeddings, and model outputs may use an AI service only with written confirmation that processing, storage, logging, support, and subprocessors remain in the approved EU path. Otherwise the feature must be blocked for EU data or use an approved EU-hosted alternative.

Retention and deletion requirements cover active data, backups, replicas, caches, derived outputs, exports, and observability records. Regional routing, outage behavior, restoration, and deletion must be tested before production, at least annually, and after material changes.

Public standard

Download the Data Residency and International Transfer Standard, version 1.0 (PDF), effective September 24, 2026, for the approved requirements.

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.